On Sat, 11 Feb 2012 17:16:36 -0500, Harry Putnam wrote:
> Camaleón <noela...@gmail.com> writes:
>
>> On Sat, 11 Feb 2012 14:13:22 -0500, Harry Putnam wrote:
>>
>>> Running wheezy - 3.0.0-1-686-pae
>>
>> Wheezy has now 3.1.0 :-?
>
> I've missed a couple of updates... the last notice I received on my kde
> desktop showed 200+... yikes.
He... yes, that hurts :-)
>>> I'm getting confused by what I see in /etc/network/interfaces,
>>> compared to what I see with ifconfig -a.
>>
>> (...)
>>
>>> So it appears at a superficial reckoning that dhcp has assigned an
>>> address to eth0, but that address appears to be attached to eth1 in
>>> ifconfig and netstat output.
>>>
>>> What explains this apparent anomaly?
>>
>> Check out "dmesg | grep -i eth", maybe the interface got renamed
>> sometime.
>
> dmesg | grep -i eth
>
> [1178198.100780] device eth1 entered promiscuous mode
> [1188657.808177] device eth1 left promiscuous mode
What did you run to get the card into promiscous mode? ntop, tcpdump...?
> Those were the only hits, so apparently eth0 is not being seen at all.
Only that two entries? I woul have expected more lines because both cards
should be at least detected :-?
> The machine does have two nics and looking again at ifconfig -a it
> shows different MAC and interrupt for each:
>
> eth0 Link encap:Ethernet HWaddr 00:40:f4:b5:29:41
> inet addr:192.168.1.54 Bcast:192.168.1.255
> Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1
> [...]
> Interrupt:19 Base address:0x6f00
>
> eth1 Link encap:Ethernet HWaddr 00:11:09:ee:6c:04
> inet addr:192.168.1.42 Bcast:192.168.1.255
> Mask:255.255.255.0 inet6 addr: fe80::211:9ff:feee:6c04/64
> Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> [...]
> Interrupt:9 Base address:0xce0
Yes, and most curious is that both cards have been configured which is
strange given the first card (eth0) has not been connected. What device/
tool provided the data to eth0 and how? Really weird.
Okay, I would start by shutting down the network service ("service
networking stop"), restarting it, manually up eth0 and eth1 and then
review your syslog ("grep -i eth /var/log/syslog") and just in case also
dmesg.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jh81ot$ai9$1...@dough.gmane.org
