At 09:35 AM 3/4/2004, Joost De Cock wrote:

This should be:

route add default gw 192.168.0.1

Ah, thank you. So perhaps rebooting simply did what I failed to do manually?


You may want to check the arp table:

woody:~# arp
Address HWtype HWaddress Flags Mask Iface
delliver.face2interface ether 00:08:74:C0:5E:69 C eth0
woody:~#


Then I pinged the other boxes on my lan and arp showed them all except for woody, which is this box.

I am still concerned about why this happened to begin with. It's looking like the fix was to reinstall my nic driver, but why did things go bad? This as said happened two weeks ago as well, also for unknown reasons so am assuming it's the same thing.

Well next time if there is a next time I'll know just what to try for recovery. Here's a funky idea, if this were to happen on a steady basis I could put a cron job in to check for the symptoms and if the network's lost then reinstall my nic. :0}

Maybe tulip isn't all that good a match for my netgear fs310tx nic? So after some time it misbehaves and stops working?

Marty Landman Face 2 Interface Inc. 845-679-9387
FormATable DB: http://face2interface.com/Products/FormATable.shtml
Make a Website: http://face2interface.com/Home/Demo.shtml
Free Formmailer: http://face2interface.com/Products/Formal.shtml



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to