On Thu, Sep 06, 2001 at 07:50:06PM +0200, Roland Dworschak wrote:
> Linux unity 2.4.7 #1 Fri Jul 27 15:58:56 CEST 2001 i686 unknown
>
> root@unity:~# ifconfig -a
>
> eth0 Link encap:Ethernet HWaddr 00:00:21:C6:28:A7
> inet addr:192.168.1.10 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr: fe80::200:21ff:fec6:28a7/10 Scope:Link
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:11014845 errors:8 dropped:2146 overruns:0
> frame:1038
> TX packets:1371156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:293564 txqueuelen:100
> RX bytes:2589121816 (2469.1 Mb) TX bytes:754456076 (719.5 Mb)
> Interrupt:10 Base address:0xb800
>
> eth1 Link encap:Ethernet HWaddr 00:01:02:FA:2D:EB
> inet addr:194.163.14.195 Bcast:194.163.14.223
> Mask:255.255.255.224
> inet6 addr: fe80::201:2ff:fefa:2deb/10 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:12369475 errors:0 dropped:0 overruns:258 frame:0
> TX packets:16482441 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:2699367596 (2574.3 Mb) TX bytes:1705285817 (1626.2
> Mb)
> Interrupt:10 Base address:0xd000
Note here the lack of the address that we're concerned with,
194.163.14.210. Where and how is that address configured, and how does
ifconfig not know about it?
> root@unity:~# ip addr
>
> 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:01:02:fa:2d:eb brd ff:ff:ff:ff:ff:ff
> inet 194.163.14.195/27 brd 194.163.14.223 scope global eth1
> inet 194.163.14.205/32 scope global eth1
> inet 194.163.14.210/32 scope global eth1
> inet 194.163.14.211/32 scope global eth1
> inet6 fe80::201:2ff:fefa:2deb/10 scope link
I'm not familiar with that program, or that output...
--
Greg White
