Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
You can always drop another linux box on the ethernet segment and run tcpdump to see what the last packet was between src and dest before the long timeout. This may help to provide a clue. HTH, ---------------------- Chuck Young Internet Systems Engineer E-Services Consulting Genuity Solutions ----------------------------- > -----Original Message----- > From: owner-discuss at Blu.Org [mailto:owner-discuss at Blu.Org]On Behalf Of > John Chambers > Sent: Friday, September 21, 2001 12:10 PM > To: discuss at Blu.Org > Subject: Re: ssh delays > > > Greg wrote: > | > | Note that dns should be caching the entries, so subsequent lookups > | should be fast even if the dns is having problems. is ssh still slow, > | repeatably? > > Yup; that's also one of the things I've tested a lot. I can > use nslookup, ping, etc to verify that the other end > responds quickly, then when I try ssh, it hangs for a > minute or two. You'd think that the earlier requests would > fill up any caches, but the delay still happens. > > - > Subcription/unsubscription/info requests: send e-mail with > "subscribe", "unsubscribe", or "info" on the first line of the > message body to discuss-request at blu.org (Subject line is ignored). - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |