Re: nm eth0 connection
On Wed, Sep 11, 2013 at 5:00 PM, Robert Holtzman <holtzm@cox.net> wrote:
> On Wed, Sep 11, 2013 at 08:15:35AM -0400, Tom H wrote:
>> On Tue, Sep 10, 2013 at 6:28 PM, Robert Holtzm <holtzm@cox.net> wrote:
>>> On Tue, Sep 10, 2013 at 04:48:03PM -0400, Patrick Wiseman wrote:
>>>> On Tue, Sep 10, 2013 at 4:01 PM, Robert Holtzm <holtzm@cox.net> wrote:
>>>>>
>>>>> Running updated wheezy on a thinkpad T420i w/ xfce DE.
>>>>>
>>>>> With great embarrassment, after stoutly defending nm, eth0 no longer
>>>>> connects. This only happens when I run wheezy. The connection is fine
>>>>> when I run the other distros on the hdd, squeeze and ubuntu 12.04.
>>>>> Under wheezy it also happens when the laptop is hard wired directly to
>>>>> the cable modem.
>>>>>
>>>>> looking at dmesg
>>>>> root@localhost:/home/holtzm# tail --lines=50 /var/log/dmesg | grep eth0
>>>>> [ 18.864912] ADDRCONF(NETDEV_UP): eth0: link is not ready
>>>>>
>>>>> Looking at messages
>>>>> root@localhost:/var/log# less messages | grep eth0 | less
>>>>> Sep 8 15:13:25 localhost kernel: [10656.049605] e1000e: eth0 NIC Link
>>>>> is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
>>>>> Sep 8 15:13:25 localhost kernel: [10656.049617] e1000e 0000:00:19.0:
>>>>> eth0: 10/100 speed: disabling TSO
>>>>> Notice the difference between 15:13:25 and 15:13:26.
>>>>>
>>>>> Don't know how to approach trouble shooting this. Any pointers
>>>>> appreciated.
>>>>
>>>> This is just a stab in the dark, but is there any reference in
>>>> /etc/network/interfaces to eth0? If so, it is not managed by nm (with
>>>> which I, too, have never had any trouble, except very recently on a
>>>> new 'testing' install where the problem was as I speculate yours could
>>>> possibly be).
>>>
>>> # The loopback network interface
>>> auto lo
>>> iface lo inet loopback
>>>
>>> # The primary network interface
>>> allow-hotplug eth0
>>> #iface eth0 inet dhcp
>>>
>>> When I first loaded wheezy the last line was uncommented and eth0
>>> wouldn't connect. After I commented it out eth0 fired right up and was
>>> perfectly stable until the other day. As a test I tried commenting the
>>> other line referring to eth0 with no luck.
>>
>> NM will not manage a NIC with "iface ..." in "/etc/network/interfaces"
>> if you don't have the following two settings in
>> "/etc/NetworkManager/NetworkManager.conf":
>>
>> "plugins=ifupdown" in the "[main]" section
>> and
>> "managed=true" in the "[ifupdown]" section
>
> holtzm@localhost:~$ cat /etc/NetworkManager/NetworkManager.conf
> [main]
> plugins=ifupdown,keyfile
>
> no-auto-default=00:21:CC:B6:06:8F,
>
> [ifupdown]
> managed=false
>
> To my knowledge nm has always worked with
> /etc/NetworkManager/NetworkManager.conf as shown above unless something
> changed managed=true to managed=false. Tried changing to managed=true
> and, for the hell of it, rebooted. Still no joy. Any other ideas?
>
> Thanks for the reply.
You're welcome.
The difference between "managed=false" and "managed=true" is that with
"managed=false", a NIC defined in "/etc/network/interfaces" is managed
by ifupdown and with "managed=true" NIC defined in
"/etc/network/interfaces" is managed by NM (or more accurately NM's
ifupdown plugin).
According to your other email, eth0 is up and managed by NM...
Reply to: