Hey!
Traceroute usually defaults to the primary interface (eth0) when multiple
interfaces are involved. You should specifically tell traceroute to use a
different interface which in your case should be "eth1":
# traceroute -i eth1 192.168.101.4
That should work.
Sean Roe wrote:
> Hi all,
>
> I have a kinda weird setup and its doing some strange stuff.
>
> I have three Linux boxes behind a cisco 2501 router hooked to a T-1 frame.
> One of the boxes is an IP_Masq box. The Cisco is using NAT to talk to the
> linux boxes. My problem is I can telnet to the Masq box from the
> Internet, I can run lynx from it ftp, ect. But I cant ping anything on
> the LAN. Here is a copy of my routing table:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 26 eth0
> 192.168.101.0 192.168.101.10 255.255.255.0 UG 0 0 25 eth1
> 192.168.101.0 0.0.0.0 255.255.255.0 U 0 0 4 eth1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 22 lo
> 0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 37 eth0
>
> Anyway, whenever I try to traceroute a LAN Address (192.168.101.XX) I get:
>
> [sean@proxy sean]$ traceroute 192.168.101.4
> traceroute: Warning: Multiple interfaces found; using 192.168.100.10 @
> eth0
> traceroute to 192.168.101.4 (192.168.101.4), 30 hops max, 40 byte packets
>
> It uses the wrong interface and dies. What am I doing wrong?
>
> Thanks,
> Sean Roe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> For daily digest info, email [EMAIL PROTECTED]
--
Audie P.
The perimeters that we put on ourselves
are self-imposed...There are no boundaries.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
