On Sun, 12 Feb 2012 11:39:45 -0500, Harry Putnam wrote:
> Camaleón <noela...@gmail.com> writes:
(...)
> I've made the updates now but my kernel has not changed. Should it
> have? I have rebooted.
You need to install the kernel metapackage ("linux-image-686-pae") so it
can be automatically updated on every new version. And today we got a new
kernel 3.2 :-)
>> What did you run to get the card into promiscous mode? ntop,
>> tcpdump...?
>
>
> I don't know but following a reboot yesterday, I still see something
> similar in dmesg today. Posted further along
Okay, that's indeed weird.
>>> 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 :-?
>
> Today there are 30+ hits.... posted at the end.
Okay... let's take a look.
>> 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.
>
> I mentioned I vaguely remembered tinking with ifconfig and setting the
> address previously posted .. (ending ..54) by hand.
Mmm...
> In the output below, and you can see the full dmesg from today along
> with the boot log from /var/log/boot at:
> www.jtan.com/~reader/vu/disp.cgi
[ 14.496990] r8169 0000:02:03.0: eth0: link down
[ 14.497172] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.201255] r8169 0000:02:03.0: eth0: link up
[ 17.201399] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Wow... why becames ready? Who/what/how awoke it?
[ 20.276085] r8169 0000:02:06.0: eth1: link down
[ 20.276290] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 23.055553] r8169 0000:02:06.0: eth1: link up
[ 23.055697] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 28.032021] eth0: no IPv6 routers present
>> 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.
>
> I post a few things following todays reboot
>
> I have connected something to the other ethernet port now ... and so
> ifconfig -a reports (with me doing nothing special but having rebooted):
>
> eth0 Link encap:Ethernet HWaddr 00:40:f4:b5:29:41
> inet addr:192.168.2.126 Bcast:192.168.2.255
> Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:feb5:2941/64
> Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> [...]
>
> 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
>
> both have received a dns served address (the one ending 42 is hard coded
> at the router by MAC. The range 100-150 is left for misc).
But did you attach a network cable to both cards?
> Here is a current grep of dmesg.
>
> Note in the /var/log/boot file that something called `NetworkManager' is
> setting up the connections. I don't know what the virutal private stuff
> is about... not my doing.
>
> grep network /var/log/boot
>
> [...]
> Sun Feb 12 09:32:53 2012: Setting up networking....
> Sun Feb 12 09:32:53 2012: Configuring network interfaces...done.
> Sun Feb 12 09:32:58 2012: Starting network connection manager:
> NetworkManager.
> Sun Feb 12 09:32:59 2012: Starting virtual private network daemon:. [...]
Do you have a VPN server running? :-?
Stop network-manager and try again:
service network-manager stop
service networking stop
service networking start
ifup eth0 eth1
ifconfig
> NOTE: the full files are available at:
>
> www.jtan.com/~reader/vu/disp.cgi
>
> dmesg|grep -i 'eth'
>
> [...]
> [ 1.396523] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [ 1.397341] r8169 0000:02:03.0: eth0: RTL8110s at 0xf8206f00,
> 00:40:f4:b5:29:41, XID 04000000 IRQ 19
> [ 1.404151] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [ 1.405063] r8169 0000:02:06.0: eth1: RTL8110s at 0xf8214e00,
> 00:11:09:ee:6c:04, XID 04000000 IRQ 9
> [ 14.658191] r8169 0000:02:03.0: eth0: link down
> [ 14.658374] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 20.503682] r8169 0000:02:06.0: eth1: link down
> [ 20.503886] ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 23.251961] r8169 0000:02:06.0: eth1: link up
> [ 23.252132] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [ 34.032016] eth1: no IPv6 routers present
> [ 170.364214] device eth0 entered promiscuous mode
> [ 193.266247] device eth0 left promiscuous mode
(...)
This promiscous mode, could it be related to the virtualbox driver being
loaded?
Stop any service related to virtualbos and retry.
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/jh8slv$hiu$1...@dough.gmane.org
