Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was trying to capture localhost traffic with Ethereal, which doesn't work without re-routing localhost traffic to your router gateway. I didn't get the route command quite right, and messed up my routing table. I typed route -f to clear the routing table and rebooted, but when I finished rebooting, the routing table wasn't restored to its original state. I didn't use the -p parameter, so none of my changes should have persisted after a reboot.

What can I do to restore the routing table to its default routes?

share|improve this question
Ethereal? Don't you mean Wireshark? – Michael Hampton Aug 31 '12 at 22:34
Ethereal and Wireshark are both protocol analyzers. – James L. Aug 31 '12 at 23:49
Ethereal was renamed Wireshark many years ago. If you're still using Ethereal, you have a real antique on your hands. And the provided link provides several possible ways of monitoring local traffic without messing with your routing table. – Michael Hampton Sep 1 '12 at 0:58
Perfect! Didn't know that. I'll take a look. Thanks Michael. – James L. Sep 1 '12 at 1:54
up vote 2 down vote accepted

Turns out that because I had setup the IPv4 settings for the NIC to use static values, Windows didn't completely rebuild the routing table when I rebooted. I changed the NIC to get its address from the DHCP server, which rebuilt the routing table, then I set it back to static values again and rebooted. The routing table is fine now.

share|improve this answer
As a side note: This is the gentleman who created Ethereal... which went on to become Wireshark - – joeqwerty Sep 1 '12 at 6:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.