Announcement

**TedNig** · May 05, 2007, 06:59 AM

Re: Fiesty network issue

There are some trix/traps to getting the NIC's to work properly in Linux from what I've read on google. Here is a how-to that may help you a tad.

Page

GL!

**coolclassic** · May 05, 2007, 07:13 AM

Re: Fiesty network issue

I not concerned with wireless at the moment I just want to get a working ethernet connection. The problem is That I can connect and I can google or read a wikki but I can't log on to a normal web site i.e. this web site. I don't think installing bcm43xx drivers will make any diffrence to a wired connection. The issue appears to be fiesty and why is it causing problems in connection on some web sites. I am using the same adsl ethernet modem to connect to the internet this computer works the other doesn't same operating system.

**jankushka** · May 05, 2007, 07:31 AM

Re: Fiesty network issue

pls, post the result of the following:

Code:

cat /etc/network/interfaces

Code:

cat /etc/hosts

Code:

cat /etc/resolv.conf

Code:

ifconfig -a

Code:

netstat -rn

**coolclassic** · May 05, 2007, 08:20 AM

Re: Fiesty network issue

peter@ubuntu:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface eth1 inet dhcp

peter@ubuntu:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

peter@ubuntu:~$ cat /etc/resolv.conf
nameserver 192.168.1.1

peter@ubuntu:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:19:7E:47:C4

7
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11

eth1 Link encap:Ethernet HWaddr 00:19:B9:5E

8:F5
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::219:b9ff:fe5e:d8f5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14357 (14.0 KiB) TX bytes:8933 (8.7 KiB)
Interrupt:21

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1824 (1.7 KiB) TX bytes:1824 (1.7 KiB)

peter@ubuntu:~$ netstat -rn
Kernel IP routeing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

**jankushka** · May 05, 2007, 10:17 AM

Re: Fiesty network issue

normally, on laptops, eth0 is the wired connection, while eth1 is the wireless one.
eth0 is not in /etc/network/interaces and it's not configured.
eth1 seems to be configured all right.
eth1 is not brought up automatically, so i'll assume you use knetworkmanager to get it going.
this thing you can only reach google and wiki is weird.
if you can reach google, you should be able to reach anything else...
could you pls try:

Code:

ping -c 5 [url]www.google.com[/url]

and

Code:

ping -c ftp.ch.debian.org

Code:

tracepath [url]www.google.com[/url]

and

Code:

tracepath ftp.ch.debian.org

**Detonate** · May 05, 2007, 10:25 AM

Re: Fiesty network issue

You might try disabling the ipv6 entries in your hosts files, just comment them out, and if using firefox set the disable ipv6 entry in about:config to "True".

**coolclassic** · May 05, 2007, 11:05 AM

Re: Fiesty network issue

peter@ubuntu:~$ ping -c 5 www.google.com
PING www.l.google.com (66.102.9.104) 56(84) bytes of data.
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=1 ttl=240 time=117 ms
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=2 ttl=240 time=105 ms
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=3 ttl=240 time=99.8 ms
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=4 ttl=240 time=152 ms
64 bytes from lm-in-f104.google.com (66.102.9.104): icmp_seq=5 ttl=240 time=125 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 99.877/120.477/152.891/18.560 ms

peter@ubuntu:~$ ping -c ftp.ch.debian.org
ping: bad number of packets to transmit.

peter@ubuntu:~$ tracepath www.google.com
1: ubuntu.local (192.168.11.3) 0.246ms pmtu 1500
1: buffalo.setup (192.168.11.1) 1.267ms
2: no reply
3: lo99.mk-1-ips.as9105.net (212.74.111.124) 135.272ms
4: ge0-3.mk0.as9105.net (80.40.119.141) 152.948ms
5: pos3-0.lon10.as9105.net (212.74.108.10) 196.344ms
6: pos2-p0.lon11.as9105.net (212.74.111.230) 158.373ms
7: ge-7-1-0.lon11.ip.tiscali.net (213.200.77.49) asymm 6 155.133ms
8: 213.200.78.34 (213.200.78.34) asymm 6 171.240ms
9: 195.219.195.17 (195.219.195.17) asymm 7 234.659ms
10: 195.219.195.6 (195.219.195.6) asymm 8 225.153ms
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500

peter@ubuntu:~$ tracepath ftp.ch.debian.org
1: ubuntu.local (192.168.11.3) 0.239ms pmtu 1500
1: buffalo.setup (192.168.11.1) 1.069ms
2: no reply
3: lo99.mk-1-ips.as9105.net (212.74.111.124) 192.341ms
4: ge0-3.mk0.as9105.net (80.40.119.141) 174.191ms
5: pos3-0.lon10.as9105.net (212.74.108.10) 166.403ms
6: pos2-p0.lon11.as9105.net (212.74.111.230) 173.339ms
7: ge-7-1-0.lon11.ip.tiscali.net (213.200.77.49) asymm 6 155.242ms
8: so-3-1-0.lon22.ip.tiscali.net (213.200.80.30) asymm 7 161.256ms
9: 213.200.78.238 (213.200.78.238) asymm 7 170.226ms
10: ldn-bb1-link.telia.net (80.91.250.225) asymm 9 181.294ms
11: ffm-bb1-link.telia.net (80.91.249.9) asymm 9 189.247ms
12: zch-b1-link.telia.net (213.248.65.42) asymm 9 204.253ms
13: dante-01287-zch-b1.c.telia.net (213.248.79.190) asymm 10 196.308ms
14: swiEZ2-10GE-1-3.switch.ch (130.59.36.249) asymm 11 170.326ms
15: rou-rz-gw-giga-to-switch.ethz.ch (192.33.92.1) asymm 12 185.937ms
16: rou-fw-rz-rz-gw.ethz.ch (192.33.92.169) asymm 13 155.276ms
17: rou-fw-cla-rz-fw.ethz.ch (192.33.92.186) asymm 14 152.307ms
18: no reply
19: rou-hpx-1-phys-hpx-server-2.ethz.ch (129.132.80.1) asymm 16 169.514ms
20: phys-server-gw.ethz.ch (129.132.80.2) asymm 17 174.547ms
21: kaerpf.ethz.ch (129.132.86.196) asymm 18 167.222ms reached
Resume: pmtu 1500 hops 21 back 18
peter@ubuntu:~$

**coolclassic** · May 05, 2007, 11:28 AM

Re: Fiesty network issue

Disabling ipv6 didn't help but here is more info that may be helpful

I did another ping and tracepath using this web address:
ping -c 5 http://kubuntuforums.net
ping: unknown host http://kubuntuforums.net

tracepath http://kubuntuforums.net
gethostbyname2: Unknown host

**Detonate** · May 05, 2007, 12:06 PM

Re: Fiesty network issue

Try the ping without the http;//

Code:

ping kubuntuforums.net

If that doesn't work, but this does, you have a DNS issue.

Code:

ping 64.34.177.146

**coolclassic** · May 05, 2007, 04:09 PM

Re: Fiesty network issue

That works so its not DNS

**jankushka** · May 05, 2007, 04:54 PM

Re: Fiesty network issue

peter@ubuntu:~$ tracepath ftp.ch.debian.org
1: ubuntu.local (192.168.11.3) 0.239ms pmtu 1500
1: buffalo.setup (192.168.11.1) 1.069ms
2: no reply
3: lo99.mk-1-ips.as9105.net (212.74.111.124) 192.341ms
4: ge0-3.mk0.as9105.net (80.40.119.141) 174.191ms
5: pos3-0.lon10.as9105.net (212.74.108.10) 166.403ms
6: pos2-p0.lon11.as9105.net (212.74.111.230) 173.339ms
7: ge-7-1-0.lon11.ip.tiscali.net (213.200.77.49) asymm 6 155.242ms
8: so-3-1-0.lon22.ip.tiscali.net (213.200.80.30) asymm 7 161.256ms
9: 213.200.78.238 (213.200.78.238) asymm 7 170.226ms
10: ldn-bb1-link.telia.net (80.91.250.225) asymm 9 181.294ms
11: ffm-bb1-link.telia.net (80.91.249.9) asymm 9 189.247ms
12: zch-b1-link.telia.net (213.248.65.42) asymm 9 204.253ms
13: dante-01287-zch-b1.c.telia.net (213.248.79.190) asymm 10 196.308ms
14: swiEZ2-10GE-1-3.switch.ch (130.59.36.249) asymm 11 170.326ms
15: rou-rz-gw-giga-to-switch.ethz.ch (192.33.92.1) asymm 12 185.937ms
16: rou-fw-rz-rz-gw.ethz.ch (192.33.92.169) asymm 13 155.276ms
17: rou-fw-cla-rz-fw.ethz.ch (192.33.92.186) asymm 14 152.307ms
18: no reply
19: rou-hpx-1-phys-hpx-server-2.ethz.ch (129.132.80.1) asymm 16 169.514ms
20: phys-server-gw.ethz.ch (129.132.80.2) asymm 17 174.547ms
21: kaerpf.ethz.ch (129.132.86.196) asymm 18 167.222ms reached

as expected.
i'd dare say your network (via eth1) works all right and your problem is somewhere else.

**coolclassic** · May 06, 2007, 01:58 PM

Re: Fiesty network issue

"i'd dare say your network (via eth1) works all right and your problem is somewhere else."

So where do I go from here? This appears to be a big issue with fiesty why does it work on one computer and not the other? Both with the same router and modem.

**coolclassic** · May 08, 2007, 06:13 AM

Re: Fiesty network issue

problem solved, apparently it's to do with window scaling (what ever that is).

Here was the solution: edit /etc/sysctl.conf
and insert the following line

net.ipv4.tcp_window_scaling=0

to reset

sudo sysctl -p

**Detonate** · May 08, 2007, 07:00 AM

Re: Fiesty network issue

That's a new one to me.

Announcement

Fiesty network issue

Fiesty network issue

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment