Hi all, i have a strange problem with my internet conection. I’m using a router between the modem and 2 computers (opensuse 11.3 and macosx) and I am connecting to the router with cable.
When I call for any url (with any browser) the connection needs a lot of time (about 40 seconds), but when I am browsing in this site, the connections work fine (when I go to google.es I have to wait about 40 seconds, but when I am in the results of the search, the connection works fine). Something similar to this post.
If i do a test speed, the result is as fast as the connection should be.
I did a lot of tries using ifup beside knetworkmanager, switched from dhcp to local ip, stoped IPv6…
I thought the problem can be because the DNS i am using, but if I boot in the same computer with windows xp (I have a dual boot) the internet connection works fine.
Could anyone help me?
Thanks.
Did you manually set the DNS info in the network settings, rather than leaving it to DHCP?
sounds like you’re not using the same DNS or not in the same order.
ping abcnews.com (for example) and see how long it takes to respond.
Also type on Linux and OSX :
traceroute abcnews.com
and on Windows (I guess) :
tracert abcnews.com
Make sure that in your /etc/hosts the local ipv6 entries if any are at the end of the file and not before the ipv4 ones.
Check with ‘route’ that ‘default’ points to the ip of your router.
You can manually add DNS in /etc/resolv.conf for testing. It won’t survive a reboot (if you’re using dhcp).
For example, add the following line :
nameserver 208.67.222.222
This is openDNS. You should be able to use it. See if it makes a difference.
As a test:
I changed the first DNS entry on my system to the server mentioned by please_try_again and found a very noticeable difference in response. I was wondering about that for some time, finally tried it. Like it!
Bart
Don’t tell me that your Firefox runs faster now ! 
Hi all, I was today making changes in my internet setup and now the delay when I call for google.es at the first time is about 15 - 20 seconds, but… I have made so many changes that I don’t know what “was” the problem. The configuration now is:
- ifup as configuraton method.
- IPv6 enabled.
- DHCP enabled, but using just version 6. If I use versino 4 I can’t reach the router and if I chose version 6 and 4, the connection is slow.
- I added the DNS of my ISP to /etc/resolv.conf. If I add openDNS, the speed don’t changes.
- The IPv6 entries are at the end of /etc/hosts
But this is very slow (about 60 seconds to load abcnews.com for example) compared with windows (8-9 seconds to load completly the same site) with firefox.
I did also what said please_try_again and I obtain this:
Ping to abcnews.com:
Linux
PING abcnews.com (199.181.132.250) 56(84) bytes of data.
64 bytes from 199.181.132.250: icmp_seq=1 ttl=236 time=214 ms
64 bytes from 199.181.132.250: icmp_seq=2 ttl=236 time=213 ms
64 bytes from 199.181.132.250: icmp_seq=3 ttl=236 time=213 ms
64 bytes from 199.181.132.250: icmp_seq=4 ttl=236 time=217 ms
64 bytes from 199.181.132.250: icmp_seq=5 ttl=236 time=213 ms
--- abcnews.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 213.317/214.649/217.973/1.800 ms
Windows
Haciendo ping a abcnews.com [199.181.132.250] con 32 bytes de datos:
Respuesta desde 199.181.132.250: bytes=32 tiempo=296ms TTL=236
Respuesta desde 199.181.132.250: bytes=32 tiempo=214ms TTL=236
Respuesta desde 199.181.132.250: bytes=32 tiempo=216ms TTL=236
Respuesta desde 199.181.132.250: bytes=32 tiempo=290ms TTL=236
Estadísticas de ping para 199.181.132.250:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 214ms, Máximo = 296ms, Media = 254ms
Traceroute to abcnews.com:
Linux
traceroute to abcnews.com (199.181.132.250), 30 hops max, 40 byte packets using UDP
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Windows
Traza a la dirección abcnews.com [199.181.132.250]
sobre un máximo de 30 saltos:
1 * * * Tiempo de espera agotado para esta solicitud. (this is similar to "timed out request"...)
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8 * * * Tiempo de espera agotado para esta solicitud.
9 * * * Tiempo de espera agotado para esta solicitud.
10 * * * Tiempo de espera agotado para esta solicitud.
11 * * * Tiempo de espera agotado para esta solicitud.
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 * * * Tiempo de espera agotado para esta solicitud.
21 * * * Tiempo de espera agotado para esta solicitud.
22 214 ms 213 ms 214 ms 199.181.132.250
Traza completa.
Any idea about what can be the problem?
Thanks a lot.
If you have a router between your modem and your lan, then your router is acting as DHCP server and configured properly. Right?
Does the default route (gateway) on your Linux box point to your router IP ?
Please type: route
Do you have several wired & wireless network interfaces ?
ifconfig -a
Sorry, I forgot to said this in the last post. The default route is pointing to my router IP.:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 br0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 br0
I have several wired and wireless network interfaces, but I don’t know why are to devices with the same mac adress (br0 and eth0).
br0 Link encap:Ethernet HWaddr 00:1E:8C:D2:E1:3F
inet addr:192.168.1.10 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
RX packets:236082 errors:0 dropped:0 overruns:0 frame:0
TX packets:242848 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:80271552 (76.5 Mb) TX bytes:66314550 (63.2 Mb)
eth0 Link encap:Ethernet HWaddr 00:1E:8C:D2:E1:3F
inet6 addr: fe80::21e:8cff:fed2:e13f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:236163 errors:0 dropped:0 overruns:0 frame:0
TX packets:242890 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:83754095 (79.8 Mb) TX bytes:67567160 (64.4 Mb)
Interrupt:23 Base address:0xc000
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:98 errors:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6356 (6.2 Kb) TX bytes:6356 (6.2 Kb)
vboxnet0 Link encap:Ethernet HWaddr 0A:00:27:00:00:00
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)
wlan0 Link encap:Ethernet HWaddr 00:1D:1A:02:18:97
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)
Why do you have a bridge ? (br0)
That could be the problem.
Not sure (I cannot test) … but you can try the following commands in that order :
ifconfig eth0 down
brctl delbr br0
route del default
ifconfig eth0 inet 192.168.1.10 netmask 0xffffff00
ifconfig eth0 up
route add default gw 192.168.1.1 dev eth0
It won’t survive a reboot, but you will see if it makes a difference. I’m not sure that you can delete the bridge however, since I don’t know why you need one. Are you doing some virtual networking ? VirtualBox doesn’t need to create a bridge anymore.
Well… I don’t know why is there a bridge, I don’t remember to create it (in fact I don’t know what exactly is a bridge). I think it was always there, is it possible?
I will try the commands you sugest…
Hello, I tried what you said pease_try_again but two things happened:
- I had to add ‘ifconfig br0 down’ after the first command.
- When I did route del default, it retourned this message: ‘SIOCDELRT: No existe el proceso’ (“The proccess does not exist”).
Now when I type ifconfig -a, the bridge is no there, but there is not any result when I try to go to any site.
eth0 Link encap:Ethernet HWaddr 00:1E:8C:D2:E1:3F
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21e:8cff:fed2:e13f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:716382 errors:1 dropped:0 overruns:0 frame:1
TX packets:809170 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:263104588 (250.9 Mb) TX bytes:218940421 (208.7 Mb)
Interrupt:23 Base address:0xe000
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:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5092 (4.9 Kb) TX bytes:5092 (4.9 Kb)
vboxnet0 Link encap:Ethernet HWaddr 0A:00:27:00:00:00
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)
wlan0 Link encap:Ethernet HWaddr 00:1D:1A:02:18:97
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)
or you can try to send a dhcp request (will not work if eth0 is not configured dor dhcp. But I guess it is):
dhclient eth0
It should set up the DNS for you.
Hi, I’ve tried reach the three addresses with and without the bridge, after set up the DNS with dhclient eth0 (it is configured for DHCP).
I’ll paste just once because in both cases (with and without the bridge) the results are very similar.
visko@viskovitz:~> ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.08 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.551 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.559 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.566 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.592 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.569 ms
--- 192.168.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5001ms
rtt min/avg/max/mdev = 0.551/0.819/2.082/0.565 ms
visko@viskovitz:~> ping 199.181.132.250
PING 199.181.132.250 (199.181.132.250) 56(84) bytes of data.
64 bytes from 199.181.132.250: icmp_seq=1 ttl=236 time=220 ms
64 bytes from 199.181.132.250: icmp_seq=2 ttl=236 time=229 ms
64 bytes from 199.181.132.250: icmp_seq=3 ttl=236 time=225 ms
64 bytes from 199.181.132.250: icmp_seq=4 ttl=236 time=228 ms
64 bytes from 199.181.132.250: icmp_seq=5 ttl=236 time=223 ms
--- 199.181.132.250 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 220.028/225.484/229.643/3.572 ms
visko@viskovitz:~> ping abcnews.com
PING abcnews.com (199.181.132.250) 56(84) bytes of data.
64 bytes from 199.181.132.250: icmp_seq=1 ttl=236 time=228 ms
64 bytes from 199.181.132.250: icmp_seq=2 ttl=236 time=225 ms
64 bytes from 199.181.132.250: icmp_seq=3 ttl=236 time=222 ms
64 bytes from 199.181.132.250: icmp_seq=4 ttl=236 time=223 ms
--- abcnews.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4004ms
rtt min/avg/max/mdev = 222.263/225.057/228.890/2.573 ms
I read your first post again. So you just have a delay when you try to connect to a site, but otherwise the connection speed is OK. Is that right ?
The problem occures under Linux but not under Windows (guess you have a dual boot).
You don’t have problem with your Mac which is connected to the router the same way (and get its IP and DNS through DHCP, right ?)
Right.
The problem occures under Linux but not under Windows (guess you have a dual boot).
Yes, I have a dual boot and this occures just with Linux.
You don’t have problem with your Mac which is connected to the router the same way (and get its IP and DNS through DHCP, right ?)
Yes and not, the Mac get its IP and DNS through DHCP and I don’t have any problem with it, but uses a wireless connection.
Well … The only thing I can think of would be to set up the DNS manually under Linux by writing a nameserver entry in /etc/resolv.conf and under Windows by editing the TCPIP properties of the connection, just to make sure that you’re using the same DNS(s) (in the same order) in both cases.
Then I would try different browsers (with default configuration and no plugins or extensions if possible) under Linux, like Firefox, Chromium, Opera, Konqueror. Also clear those browsers cache first.
OK, I’ll try with the browsers to see what happen.
Thank you very much for your help.