Date: Mon, 29 Sep 2003 08:06:35 +1000 From: "Joe Shevland" <joe.shevland@e-wise.com> To: <freebsd-stable@freebsd.org> Subject: Re: "No route to host after certain time" is fxp only? Message-ID: <003e01c3860c$c8b74790$0100000a@internal.ewise.com> References: <3F719A58.5000700@snu.ac.kr><6.0.0.22.0.20030924103406.0307c250@209.112.4.2><6.0.0.22.0.20030924111529.05a965d0@209.112.4.2><6.0.0.22.0.20030924114051.06fb5e58@209.112.4.2><6.0.0.22.0.20030924121543.08c1c060@209.112.4.2><3F71C4E9.8030801@snu.ac.kr> <3F71C6E9.5070903@burghcom.com><6.0.0.22.0.20030924164105.08ccb600@209.112.4.2> <20030928142750.E5415@mail.physik.uni-mainz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Is there any chance this might've caused an issue with natd and a gateway machine using an Intel EtherExpress/100? I CVSup'ed on Friday 26th (morning AEST) to RELENG_4 remotely ... and subsequently locked myself out :) NATD was chewing up a lot of CPU (~20% on a 1GHz single CPU) and the machine was almost unreachable using the fxp interface - I could eventually get an SSH login prompt but that would timeout. From the LAN side (an rl driver card, Dolphin?) people could still access the machine. The internal users still had internet access, albeit very, very slow. Sorry I don't have better information, I've still got the logs but couldn't find anything obvious being streamed to the console and natd didn't seem to have much to say (I'd have looked at syslog but I was only getting ~3 minute windows on the machine before it started complaining again). Killing and restarting NATD would fix the problem temporarily, however it would start happening again after a short period, maybe triggered by another SSH connection to the outside interface though thats just guessing/coincidence at this stage. CVS'uping to a previous date=2003.09.19 tag fixed the issue; I've got a list of the files that were affected between the good date and (my) bad date if they're of use. Regards, Joe ----- Original Message ----- From: "Administrator IPA" <administrator@mail.physik.uni-mainz.de> To: "Mike Tancsa" <mike@sentex.net> Cc: <freebsd-stable@freebsd.org>; <bms@freebsd.org> Sent: Sunday, September 28, 2003 10:31 PM Subject: Re: "No route to host after certain time" is fxp only? > > Dear Mike. > > I saw the problem only on two machines: a SMP system with a Intel > Ether Express/100 (fxp) running RELENG_5_1 and a older UP machine > running RELENG_4_8, also equipted with a Intel EtherExpress/100. > All other machines, either UP or SMP machines runninf RELENG_5_1 > have em0 NICs (Intel EtherExpress/1000). They never showed up the reported > problems until now. maybe it's a driver related problem? > > Hope this helps, sorry if it is boring ;-) > > Oliver >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003e01c3860c$c8b74790$0100000a>