Re: ssh & select() problem on 5.3

2004-11-30 Thread Claudiu Dragalia-Paraipan
Just for the record, the problem is solved. It was indeed a misconfiguration at the next hop, at the provider. Thank you. With respect, -- Claudiu Dragalina-Paraipan [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature

Re: ssh & select() problem on 5.3

2004-11-29 Thread Claudiu Dragalia-Paraipan
Peter Jeremy wrote: On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: Since the problem occurs only when I connect to the firewall or to a server behind it, I started to suspect a hardware failure. Could a network card cause such problems ? A couple of people have mentioned pa

Re: ssh & select() problem on 5.3

2004-11-29 Thread Claudiu Dragalia-Paraipan
Andre Oppermann wrote: Peter Jeremy wrote: On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: Since the problem occurs only when I connect to the firewall or to a server behind it, I started to suspect a hardware failure. Could a network card cause such problems ? A couple of p

Re: ssh & select() problem on 5.3

2004-11-29 Thread Andre Oppermann
Peter Jeremy wrote: On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: Since the problem occurs only when I connect to the firewall or to a server behind it, I started to suspect a hardware failure. Could a network card cause such problems ? A couple of people have mentioned pat

Re: ssh & select() problem on 5.3

2004-11-29 Thread Peter Jeremy
On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: >Since the problem occurs only when I connect to the firewall or to a >server behind it, I started to suspect a hardware failure. Could a >network card cause such problems ? A couple of people have mentioned path-MTU problems.

Re: ssh & select() problem on 5.3

2004-11-29 Thread Barney Wolff
On Sun, Nov 28, 2004 at 06:43:47PM +0200, Claudiu Dragalia-Paraipan wrote: > > Since the problem occurs only when I connect to the firewall or to a > server behind it, I started to suspect a hardware failure. Could a > network card cause such problems ? > The firewall is running on FreeBSD 5.2.1

Re: ssh & select() problem on 5.3

2004-11-28 Thread David Malone
On Sun, Nov 28, 2004 at 08:30:03PM +0200, Alin-Adrian Anton wrote: > A tcpdump shows that what actually happens is that packets won't reach > me in spite of the fact that his firewall(router)'s tcpdump shows that > he keeps sending them to me. Packets never reach me, but I am still able > to send t

Re: ssh & select() problem on 5.3

2004-11-28 Thread Alin-Adrian Anton
Hi, Barney Wolff wrote: Perhaps an MTU problem, with the ICMP "fragmentation needed but DF set" being blocked by the firewall? It would only show up when the server has enough to send to fill a packet. I'm the friend he was talking about. The very same thing happens when the firewall is disabled.

Re: ssh & select() problem on 5.3

2004-11-28 Thread Claudiu Dragalia-Paraipan
Hi, Robert Watson wrote: Sounds like a bug, but the interesting question is really whether it's a kernel bug or an SSH bug. I'm not up on SSH internals, but there are a few other knobs you might try and things to look at that might help address whether it's a kernel bug or not: (1) Try debug.mpsaf

ssh & select() problem on 5.3

2004-11-27 Thread Claudiu Dragalia-Paraipan
Hello, since I have upgraded to FreeBSD 5.3 I have the following problem with SSH client: I log on several FreeBSD 5.2.1 machines, and when I start a command that gives a 'large' result (like dmesg, cat a file), ssh client locks. I ran ssh in gdb, and found out that it locks in select() in libc.