Hi, Bruce, I believe the problem is solved. A device was using same ip, the router was accepting (?) both. I thought I had defined to a different ip, before, when I had to do for all devices of the network, after I upgraded to a new router, many months ago. Always, ISTR having observed the problem since them, but was not clear in my mind if that was true.
Thank you very much for giving me many points to think and learn. I had given up solving this problem, but your encouragement made me think about it again. Anyway, I try will reply, below, to some of your questions. --- Em ter, 9/4/13, Bruce Dubbs escreveu: > De: Bruce Dubbs > Assunto: Re: [blfs-support] openssh-6.2p1 messages > Para: "BLFS Support List" > Data: Terça-feira, 9 de Abril de 2013, 1:58 > Fernando de Oliveira wrote: > > --- Em seg, 8/4/13, Bruce Dubbs escreveu: > > >> /usr/sbin/sshd -p29 -D -d -d > > > > Done. > > >> On the client: > >> > >> ssh -v -v -p29 server > > > > I did some work during some time in the machines, no > disconnection. > > Left them alone, came back, client disconnected. > > From the sever log, you can see that the connection > completed ate the line: > > debug1: Setting controlling tty using TIOCSCTTY. > > There were frequent delays and keep alive requests. I > don't know what > the ~/.ssh/config or /etc/ssh/ssh_config files had, if > anything. Both > those are on the client. > > You need to have in one of the *client* config files: > > ServerAliveInterval 45 > > The number may vary, but 45 seems to work for me. I > also add > > ServerAliveCountMax 10 They are there, since you suggested, the other day. ... > The questions I would have include > What is the route between the server and > client? Are there > a lot of devices or is it as short as a virtual device in a > local system? > Just a router. Have two different generation LFS machines with almost identical configurations which are guests of the same host. Why only one was having problems seem to be understood now (see above). > Is the route busy with other traffic? I do not think it is. > > > Client lost connection with message: > > > > $ Write failed: Broken pipe > > > > Server stopped manually, after that. > > That's normal with a -D option at disconnect. Well, these are scripted now, so I do not forget if eventually it is needed in the future. > > > >> ping generally uses ICMP, not tcp or udp. > > > I knew it could be done, was perhaps going to do it, > but I want to > > ping, as it is the way I "see" the other machines > without going > > there, or just to test they are running, etc. > > Generally not bad. It could be a target for a Denial > of Service attack, > but otherwise it won't do much. If someone sends an > ICMP packet (ECHO > REQUEST), it just responds with an ECHO_REPLY packet. > > -- Bruce When you are back, please, is there a way of having ping working and not being vulnerable to a DoS attack? Thanks again, Take care, []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
