| View previous topic :: View next topic |
| Author |
Message |
the_sphynx
Apprentice
Joined: 19 May 2004
Posts: 156
Location: Thornton, CO
|
 Posted: Thu Apr 07, 2005 10:43 pm Post subject: route output is SLOW!! [SOLVED] |
 |
|
Here is my route output. I don't think it should take 41 sec. to display my kernel routes. It slows down at my first route and at my default route at the end. My router is 72.16.133.205 and eth0 is my external interface. Any advice would be greatly appreciated.
| Code: |
firewall root # time route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
72.16.133.204 * 255.255.255.252 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
loopback localhost 255.0.0.0 UG 0 0 0 lo
default 72.16.133.205 0.0.0.0 UG 0 0 0 eth0
real 0m41.039s
user 0m0.001s
sys 0m0.003s
|
_________________
Folding@Home User 285941
Last edited by the_sphynx on Fri Apr 08, 2005 7:14 pm; edited 1 time in total |
|
| Back to top |
|
 |
wmgoree
Apprentice
Joined: 08 Aug 2003
Posts: 246
Location: Alexandria, VA
|
| Posted: Thu Apr 07, 2005 10:51 pm Post subject: use route -n, or get PTR records |
|
|
It's taking so long because it's trying to look up the hostnames for the IP addresses in the routing table, and coming up with nothing. You have two options:
1. Ask route to stop looking up the hostnames
2. Get some PTR records for those IP addresses (possibly not feasible depending on your setup)
Solution #1 is fairly easy; just add the -n flag to route, thus:
Solution #2 could involve a whole host of steps.
If the -n flag doesn't solve the issue, that may mean a problem with the network media.
_________________
vi? *snicker* it doesn't even include a mail reader... |
|
| Back to top |
|
|
TerminalAddict
Tux's lil' helper
Joined: 13 Feb 2003
Posts: 119
|
| Posted: Thu Apr 07, 2005 10:52 pm Post subject: |
|
|
| Code: |
apoc root # time route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.4.0 * 255.255.255.0 U 0 0 0 eth1
172.16.149.0 * 255.255.255.0 U 0 0 0 vmnet1
172.16.109.0 * 255.255.255.0 U 0 0 0 vmnet8
loopback apoc.loudas.com 255.0.0.0 UG 0 0 0 lo
default 192.168.4.254 0.0.0.0 UG 0 0 0 eth1
real 0m0.330s
user 0m0.000s
sys 0m0.002s
apoc root # time ip route show
192.168.4.0/24 dev eth1 proto kernel scope link src 192.168.4.147
172.16.149.0/24 dev vmnet1 proto kernel scope link src 172.16.149.1
172.16.109.0/24 dev vmnet8 proto kernel scope link src 172.16.109.1
127.0.0.0/8 via 127.0.0.1 dev lo scope link
default via 192.168.4.254 dev eth1
real 0m0.058s
user 0m0.000s
sys 0m0.001s
apoc root #
|
|
|
| Back to top |
|
|
wmgoree
Apprentice
Joined: 08 Aug 2003
Posts: 246
Location: Alexandria, VA
|
| Posted: Fri Apr 08, 2005 3:06 pm Post subject: /proc/net/route |
|
|
| Code: | | cat /proc/net/route |
Will also be much faster but you have to learn to read the addresses in that format.
_________________
vi? *snicker* it doesn't even include a mail reader... |
|
| Back to top |
|
|
the_sphynx
Apprentice
Joined: 19 May 2004
Posts: 156
Location: Thornton, CO
|
| Posted: Fri Apr 08, 2005 7:12 pm Post subject: |
|
|
I appreciate the responses. I don't have any domains pointing to any of my IP(s). So that could explain the slowness of a simple route command. Here is the output of route -n:
| Code: |
firewall root # time route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
72.16.133.204 0.0.0.0 255.255.255.252 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 72.16.133.205 0.0.0.0 UG 0 0 0 eth0
real 0m0.003s
user 0m0.000s
sys 0m0.003s
|
So I would chalk it up to DNS resolution.
_________________
Folding@Home User 285941 |
|
| Back to top |
|
|
|
Networking & Security
