Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Traceroute using Virtual NIC (bond0:0) over bonded interfaces (bond0) fails.

Traceroute using Virtual NIC (bond0:0) over bonded interfaces (bond0) fails.

2005-08-15       - By Tom Sightler

 Back
Reply:     1     2  

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.