From: Martin Josefsson (gandalf_at_wlug.westbo.se)
Date: Wed 13 Feb 2002 - 17:29:52 GMT
On Wed, 13 Feb 2002, Roderick A. Anderson wrote:
> Here is the results of ifconfig in a virtaul server
>
> eth0 Link encap:Ethernet HWaddr 00:80:AD:71:22:2C
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:701060 errors:0 dropped:0 overruns:0 frame:0
> TX packets:48393 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:76531350 (72.9 Mb) TX bytes:7184647 (6.8 Mb)
> Interrupt:11 Base address:0xe800
>
> eth0:vs1 Link encap:Ethernet HWaddr 00:80:AD:71:22:2C
> inet addr:216.64.180.227 Bcast:216.64.180.255 Mask:255.255.255.255
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:11 Base address:0xe800
>
> lo Link encap:Local Loopback
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:877 errors:0 dropped:0 overruns:0 frame:0
> TX packets:877 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:75810 (74.0 Kb) TX bytes:75810 (74.0 Kb)
>
>
> > ifconfig works as it should but ip from the iproute2 package uses netlink
> > IIRC and there I can see all addresses of all interfaces.
>
>
> OOPS! Is the above relavant?
It shows that it works for the ifconfig case :)
ifconfig and iproute2 doesn't use the same method of communication with
the kernel.
/Martin
Never argue with an idiot. They drag you down to their level, then beat you with experience.