Hmm the last email I just sent on this subject the ifconfig now looks more
normal: but I think this is deceptive.
In the mean time I loaded Cisco VPN client kernel modules and the byte
counts of the interface match the (usually hidden) cipsec0 interface.
The cisco VPN client modules had not been loaded into the kernel prior to
this and I bet (but can't test right now) that if the cipsec0 device
goes away eth0:1 takes back the eth1 counters...
cipsec0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1400 Metric:1
RX packets:181172 errors:0 dropped:0 overruns:0 frame:0
TX packets:152075 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0:0 Link encap:Ethernet HWaddr 08:00:2B:C5:0D:7A
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1356 Metric:1
RX packets:181172 errors:0 dropped:0 overruns:0 frame:0
TX packets:152075 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x2c00
