Typing the command:

% route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface     *        U     2      0        0 wlan0
link-local      *          U     1000   0        0 wlan0
(... hang for a while ...)
default         UG    0      0        0 wlan0

Here, before the last line default rule be printed, route just hang for while.

Isn't the route table cached somewhere?

I used to grep the result from route to get the default rule, to get the default gateway. Now, route seems hang for a while in some machines.

  • 2
    BTW, it would be more efficient to parse the /proc/net/route file for that information. – Keith Jun 2 '11 at 3:31
  • The IPs are encoded in hex numbers in /proc/net/route. – Xiè Jìléi Jun 2 '11 at 5:06
  • 2
    Yes. so you can convert them. If you can't, the output of ip route is also easier to parse. – Keith Jun 2 '11 at 6:53

It's trying to do a reverse DNS lookup on the gateway address, and waiting for timeout. Try running with the -n option to suppress that.

| improve this answer | |

You may have some DNS related problems. Try the following to check it out:

$ cat /etc/resolv.conf
nameserver <IP_1>
nameserver <IP_2>
search <DOMAIN>

host www.google.com <IP_1>

host www.google.com <IP_2>

If everything is working fine, you shouldn't get any delays while executing 'route' command


| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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