Page 1 of 1
[SOLVED] Long time connecting after changing a router

Posted:
Feb 16th, '13, 07:02
by zugunder
Hi,
I recently had to replace my WiFi router, now I have a Buffalo one. And a problem with connections came with it. It takes tens of seconds to load a simple website, most of the time the browser reporting "connecting" or "waiting for
http://www... However, downloading big files is OK, speed is really high, but again, it takes some time to start downloading.
What could I check to find the reason for that? Anything with DNS servers?
Thank you.
P.S. Mageia 1 64bit with KDE.
Re: Long time connecting after changing a router.

Posted:
Feb 16th, '13, 13:33
by doktor5000
Did you reconfigure your wireless interface on the Mageia side after exchanging the router?
Please show your
/etc/sysconfig/network-scripts/ifcfg-wlan0 and your
/etc/resolv.conf and the time it takes for name lookups by e.g.
- Code: Select all
time nslookup www.google.com
Re: Long time connecting after changing a router.

Posted:
Feb 16th, '13, 23:24
by zugunder
Hi Doctor,
No, I have not change anything in settings after I replaced the router.
/etc/sysconfig/network-scripts/ifcfg-wlan0:- Code: Select all
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=no
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=yes
DNS1=192.168.11.1
RESOLV_MODS=yes
WIRELESS_MODE=Managed
WIRELESS_ESSID=Name
WIRELESS_ENC_KEY=s:xxxxxxxxxxxx
WIRELESS_WPA_DRIVER=wext
WIRELESS_WPA_REASSOCIATE=no
IPV6INIT=no
IPV6TO4INIT=no
ACCOUNTING=yes
NM_CONTROLLED=yes
DHCP_CLIENT=dhclient
NEEDHOSTNAME=no
PEERDNS=no
PEERYP=yes
PEERNTPD=no
/etc/resolv.conf:- Code: Select all
nameserver [b]192.168.11.1[/b]
(This is the router's IP I use to access it for manual configuration, I am not sure it should be also DNS...)
- Code: Select all
$ time nslookup www.google.com
Server: 192.168.11.1
Address: 192.168.11.1#53
Non-authoritative answer:
Name: www.google.com
Address: 74.125.137.99
Name: www.google.com
Address: 74.125.137.106
Name: www.google.com
Address: 74.125.137.105
Name: www.google.com
Address: 74.125.137.104
Name: www.google.com
Address: 74.125.137.103
Name: www.google.com
Address: 74.125.137.147
real 0m0.045s
user 0m0.000s
sys 0m0.006s
Re: Long time connecting after changing a router.

Posted:
Feb 17th, '13, 00:06
by doktor5000
So basic name resolution is ok, and for me the router is also a forwarder to DNS server.
What browser are you using?
Re: Long time connecting after changing a router.

Posted:
Feb 17th, '13, 00:10
by zugunder
Hi Doctor,
Thank you for the prompt reply!
It doesn't seem to depend on a browser - all networking applications behave the same way - Akregator, weather applet, etc.
I actually tried different browsers too - at least FF, Konqueror and Opera have the same lagging behavior.
I think it might be some specific Buffalo-Linux issue as Windows networking is not affected at all.
Re: Long time connecting after changing a router.

Posted:
Feb 17th, '13, 00:19
by doktor5000
Well, you could try to reconfigure the connection using drakconnect, providing e.g. google DNS server instead of using your router, so put
8.8.8.8, 8.8.4.4 instead of 192.168.11.1 there for DNS servers.
Then you could try to clear your browser cache, and maybe also try to disable IPv6, system-wide and maybe in the browser explicitly.
For IPv6, in draknetcenter -> advanced options -> disable IPv6 (and maybe reboot or restart networking).
For the browser, in firefox that would be about:config -> network.dns.disableIPv6 set to false
Re: Long time connecting after changing a router.

Posted:
Mar 6th, '13, 05:01
by zugunder
Hi,
Sorry for the late reply, but changing the default (Buffalo router) DNS to the Google's made the trick immediately. I did not touch IPv6 settings as everything works pretty fast now. The only thing which is still broken is watching online TV - the players still buffer not continuously but with significant gaps, so the playback is regularly interrupted.
I am only curious what exactly the problem was - in the router, my ISP's DNS service or anywhere else?
Thank you!
P.S. I checked it in Windows - there are exactly the same problems with buffering video streams, so the problem seems to be on ISP's side (or some general hardware malfunctions). The problem is solved.