Pierre Fortin wrote:
> Felix Miata wrote:
> > > So your route command should work faster... no?
> > Only if I use -n. Plenty slow otherwise.
> Give us a new "route" and "route -n" output and indicate precisely where the
> former's the delay occurs. What is st21s? It's unknown from here and from your
st21s is 192.168.0.54, the Linux machine I'm trying to configure.
> message headers, you are on a dialup. The link is up when you are issuing the
> route command, right?
Not for the previous posts. These following are, and without using -n, the delay
was before the first line was output.
-n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
209.208.25.25 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.0.54 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo
192.168.0.0 192.168.0.254 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.0.254 0.0.0.0 UG 1 0 0 eth0
without -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
209.208.25.25 * 255.255.255.255 UH 0 0 0 ppp0
st21s.atlantic. * 255.255.255.255 UH 0 0 0 eth0
localhost * 255.255.255.255 UH 0 0 0 lo
192.168.0.0 192.168.0.254 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
default 192.168.0.254 0.0.0.0 UG 1 0 0 eth0
without -n or a connection the pause was after display of second entry:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
st21s.atlantic. * 255.255.255.255 UH 0 0 0 eth0
localhost * 255.255.255.255 UH 0 0 0 lo
192.168.0.0 192.168.0.254 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
default 192.168.0.254 0.0.0.0 UG 1 0 0 eth0
I don't understand why there are any .254 entries. Where do they come from?
Nothing on my local net has IP 192.168.0.254.
I changed /etc/rc.d/rc.local from:
route add -net 192.168.0.0 netmask 255.255.0.0 gw 192.168.0.254
to
route add -net 192.168.0.0 netmask 255.255.0.0 gw 192.168.0.54
and got with route -n and isp connection:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
209.208.25.20 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.0.54 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo
192.168.0.0 192.168.0.54 255.255.255.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.0.254 0.0.0.0 UG 1 0 0 eth0
Without the -n I still get the long delay.
> > /etc/sysconfig/network-scripts/
> > grep * metric:
> > ifup: route add default gw ${GATEWAY} metric 1 ${DEVICE}
> > ifup-aliases: route add default gw ${GATEWAY} metric
>1 ${DEVICE}
> > ifup-plip: route add default gw ${GATEWAY} metric 1 ${DEVICE}
> > IIRC, the OS was installed Jan 2000. Is the Jan 2000 file the one that caused
> > the duplication? Should I just rem that line out? I suppose that file was last
> > modified by a Gnome ppp dialer configuration for my ISP?
> Where did you get those scripts? None of mine have the metric arg on the route
Came with the OS install?
> commands... so if you look closer, you'll probably find you have other route
> commands in these files without "metric" which would explain the duplicate
> routes. Send me a copy of these scripts; I'm curious...
Sent.
--
A fool gives full vent to his anger, but a wise man keeps himself under control.
Proverbs 29:11 NKJV
Team OS/2
Felix Miata *** http://mrmazda.members.atlantic.net/
