On Mon, Aug 01, 2005 at 04:33:11PM -0400, Jim McQuillan wrote: > jeff, > > Ok, the next thing to do is use tcpdump to watch the traffic that is > trying to go out through that interface. > > if the external interfaced is eth1, then try this: > > tcpdump -i eth1 > > Then sit back and watch, to see what traffic is trying to use the > interace. > > That is, assuming you've pulled the plug. > > Jim.
Jim, I've tried that on several occasions and not seen any traffic go on eth1 once the plug was pulled. Even attempting to ping google.com didn't show any traffic. That aside, I've been trying other things, and I may have gotten it working, though I'm not sure why, which isn't ideal. The following two changes were precipitous in making my terminals work again: switching from the nfs-kernel-server package to the nfs-user-server package and changing the host line in /etc/nsswitch.conf to read host files dns rather than the other way around. We'll see if it stays working, but I have my fingers crossed. And I'll be attempting to replicate this success on the other two machines. Thanks, Jeff ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
