 | | | Traceroute using Virtual NIC (bond0:0) over bonded, interfaces (bond0) fails | Traceroute using Virtual NIC (bond0:0) over bonded, interfaces (bond0) fails 2005-08-16 - By Anu Matthew
Back
Ed/Tom,
Many thanks for the replies. Much appreciated..!!
--AM
Date: Mon, 15 Aug 2005 13:44:04 -0600
From: Ed Brown <ebrown@(protected)>
Subject: Re: Traceroute using Virtual NIC (bond0:0) over bonded
interfaces (bond0) fails. Any ideas why?
To: "Discussion of Red Hat Enterprise Linux 3 (Taroon)"
<taroon-list@(protected)>
Cc: General Red Hat Linux discussion list <redhat-list@(protected)>
Message-ID: <1124135044.29357.8.camel@(protected)>
Content-Type: text/plain
For what it's worth, traceroute also fails from a non-bonded virtual
interface:
# ifconfig eth0:1
eth0:1 Link encap:Ethernet HWaddr 00:30:48:10:yy:xx
inet addr:x.y.z.48 Bcast:x.y.z.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
# traceroute -i eth0:1 nsx
setsockopt: No such device
unable to bind to device: eth0:1
-Ed
On Mon, 2005-08-15 at 12:52, Anu Matthew wrote:
>> I've two NICs bonded together as bond0. I can do traceroutes using
>> bond0 as the interface. But when I configure a virtual IP over bond0
>> (virtual i/f bond0:0), I cannot do traceroutes using bond0:0
>>
>> Its RHEL AS 3.0 (update 5) btw..
>>
>> Any ideas?
>>
>>
>> [root@(protected) root]# ifconfig bond0
>> bond0 Link encap:Ethernet HWaddr 00:0E:0C:6D:60:A9
>> inet addr:A.B.C.30 Bcast:A.B.C.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
>> RX packets:204934735 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:157330806 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:3717085046 (3544.8 Mb) TX bytes:1706013707 (1626.9 Mb)
>>
>> Traceroutes using bond0 to any other hosts works:
>>
>> [root@(protected) root]# traceroute plinux11 -i bond0
>> traceroute to plinux11.net.bms.com (A.B.C.29), 30 hops max, 38 byte packets
>> 1 plinux11 (A.B.C.29) 0.305 ms 0.190 ms 0.238 ms
>>
>> Now, here the virtual nic bond0:0.
>>
>> [root@(protected) root]# ifconfig bond0:0
>> bond0:0 Link encap:Ethernet HWaddr 00:0E:0C:6D:60:A9
>> inet addr:A.B.C.9 Bcast:A.B.C.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
>>
>> [root@(protected) root]# traceroute plinux11 -i bond0:0
>> setsockopt: No such device
>> unable to bind to device:
>> bond0:0 <-- ---- --- It fails.
>> bond0:0 -- unable to bind..????
>>
>> I am able to ping bond0:0 from other hosts.
>>
>> Is there a limitation that, bonded nic is already a virtual interface
>> (well kind of), and one cannot create a virtual nic over a bonded interface?
>>
>> Many thanks in advance.
>>
>> --AM
>>
>>
>>
>>
>> --
>> Taroon-list mailing list
>> Taroon-list@(protected)
>> http://www.redhat.com/mailman/listinfo/taroon-list
>
>
-- ---- ---- ---- ---- ---- --
Date: Mon, 15 Aug 2005 17:16:22 -0400
From: Tom Sightler <ttsig@(protected)>
Subject: Re: Traceroute using Virtual NIC (bond0:0) over bonded
interfaces (bond0) fails. Any ideas why?
To: "Discussion of Red Hat Enterprise Linux 3 (Taroon)"
<taroon-list@(protected)>
Message-ID: <1124140583.3107.39.camel@(protected)>
Content-Type: text/plain
On Mon, 2005-08-15 at 14:52 -0400, Anu Matthew wrote:
>> I've two NICs bonded together as bond0. I can do traceroutes using
>> bond0 as the interface. But when I configure a virtual IP over bond0
>> (virtual i/f bond0:0), I cannot do traceroutes using bond0:0
>>
>> Its RHEL AS 3.0 (update 5) btw..
>>
>> Any ideas?
>
>
I think this is simply a limitation of the traceroute command, it seems
only to know about physical interfaces. Many of the network tools
(route for example) seem to have this limitation.
That being said, it's pretty easy to work around, simply use traceroute
-s and specify the source IP address instead of the interface, then you
can trace via your "virtual" interface.
Later,
Tom
-- ----
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|