This is a discussion on Sluggish network after upgrade from Woody stable to testing. within the Linux Networking forums, part of the Linux Forums category; Howdy. A couple of days back I upgraded my system from Debian Woody stable to testing using apt-get dist-...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Howdy.
A couple of days back I upgraded my system from Debian Woody stable to testing using apt-get dist-upgrade. After the upgrade my network is very sluggish. It takes 30 sec just to ssh to the machine next door. My initioal googling didn't make me any wiser. Has anyone met this problem and can point me in _ANY_ direction? Best wishes from Jens Ivar |
|
|||
|
Jens Ivar Jordre wrote:
> A couple of days back I upgraded my system from Debian Woody stable to > testing using apt-get dist-upgrade. After the upgrade my network is very > sluggish. It takes 30 sec just to ssh to the machine next door. My > initioal googling didn't make me any wiser. Has anyone met this problem > and can point me in _ANY_ direction? 30s sounds like a DNS time out. Maybe you have a bogus DNS server in /etc/resolv.conf? Maybe there's a reverse look up failing? Play with tcpdump to find out what is going on - preferably on both ends of the connection... Mike -- Mike Jagdis Web: http://www.eris-associates.co.uk Eris Associates Limited Tel: +44 7780 608 368 Reading, England Fax: +44 118 926 6974 |
|
|||
|
Jens Ivar Jordre wrote on 04.11.2003 21:55:
> Howdy. > > A couple of days back I upgraded my system from Debian Woody stable to > testing using apt-get dist-upgrade. After the upgrade my network is very > sluggish. It takes 30 sec just to ssh to the machine next door. My > initioal googling didn't make me any wiser. Has anyone met this problem > and can point me in _ANY_ direction? Problems with slow SSH starting are often rooted in the inabilty of reverserse IP lookup. Check your nsswitch.conf and maybe try "CheckHostIP=no" in ssh_config. Just a guess. Good luck. -- Walter -- A: Weil es die Lesbarkeit des Textes verschlechtert. F: Warum ist TOFU so schlimm? A: TOFU F: Was ist eins der groesste Aergernisse im Usenet? |
|
|||
|
Jens Ivar Jordre wrote on 04.11.2003 21:55:
> A couple of days back I upgraded my system from Debian Woody stable to > testing using apt-get dist-upgrade. After the upgrade my network is very > sluggish. It takes 30 sec just to ssh to the machine next door. My > initioal googling didn't make me any wiser. Has anyone met this problem > and can point me in _ANY_ direction? Problems with slow SSH starting are often rooted in the inability of doing reverse IP lookups. Check your nsswitch.conf and maybe try "CheckHostIP=no" in ssh_config. Just a guess. Good luck. -- Walter |
|
|||
|
Mike Jagdis wrote:
> 30s sounds like a DNS time out. Maybe you have a bogus DNS server > in /etc/resolv.conf? Maybe there's a reverse look up failing? Play > with tcpdump to find out what is going on - preferably on both ends > of the connection... You were right on this one. My primary DNS server was failing. Thanks. Jens Ivar |
|
|||
|
On Tue, 04 Nov 2003 21:55:56 +0100, Jens Ivar Jordre
<jensivar.jordre@fi.uib.no> wrote: > > A couple of days back I upgraded my system from Debian Woody stable to > testing using apt-get dist-upgrade. After the upgrade my network is > very sluggish. It takes 30 sec just to ssh to the machine next door. I would first check to see if you have a "domain" line in your /etc/resolv.conf. If you don't and you use unqualified names to connect, it will first try to look up the name with no domain. Only when that fails or times out will it append the domain name. At least that's the documented behavior. There seems to be a bug in Sid as installed on my laptop, that causes it to always do this, even though I have a domain line in /etc/resolv.conf. To test, use the fully-qualified name to connect and see if that makes a difference. -- -| Bob Hauck -| To Whom You Are Speaking -| http://www.haucks.org/ |