At 02:48 PM 12/10/1998 -0800, [EMAIL PROTECTED] wrote:
>Dave> In fact, even if I set up a static route for all MC addresses as
follows:
>Dave> /sbin/route add -net 224.0.0.0 netmask 240.0.0.0 eth1
>Dave> and then do a "traceroute 224.0.0.1" or "ping 224.0.0.1" (I realize
that nobody
>Dave> will answer this), Linux automatically routes these to eth0 by default.
>Dave> AAargh! This has got to be broken!
>
>Let me put it another way:
>
>[root@foo /root]# /sbin/route
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use Iface
>192.168.2.0 * 255.255.255.0 U 0 0 4 eth1
>xxx.yyy.zzz.0 * 255.255.255.0 U 0 0 8 eth0
>127.0.0.0 * 255.0.0.0 U 0 0 26 lo
>224.0.0.0 * 240.0.0.0 U 0 0 7 eth1
>default some.name.here 0.0.0.0 UG 0 0 2 eth0
>[root@skyfeed /root]# /usr/sbin/traceroute 224.0.0.1
>traceroute: Warning: Multiple interfaces found; using 207.168.228.71 @ eth0
>traceroute to 224.0.0.1 (224.0.0.1), 30 hops max, 40 byte packets
>
>[root@foo /root]#
>
>What's up with that "eth0" shit?
>
>Dave
>-
What is happening is that for some reason traceroute defaults to
eth0 if you have more then one network interface. You can specify
the interface with the -i option. (man traceroute) Why traceroute
doesn't use the routing tables may have something to with the fact
that is a diagnostic tool, but it would be nice if it would
use them unless overridden on the command line...
Mikkel
---
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
