Re: eth0 "disabled" after upgrade Squeeze to Wheezy
On Fri, Nov 15, 2013 at 5:38 PM, Lisi Reisz <lisi.reisz@gmail.com> wrote:
> On Friday 15 November 2013 17:05:04 Tom H wrote:
>> On Fri, Nov 15, 2013 at 3:55 PM, Lisi Reisz <lisi.reisz@gmail.com>
> wrote:
>>> On Friday 15 November 2013 15:29:00 Tom H wrote:
>>>> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
>>>> <lisi.reisz@gmail.com> wrote:
>>>>>
>>>>> I have just upgraded a client's computer to Wheezy. It appeared
>>>>> to go well and there was certainly an internet connection: it
>>>>> would not have been able to upgrade otherwise!
>>>>>
>>>>> Now there is none. I have checked /etc/network/interfaces and
>>>>> changed "allow-hotplug" to "auto", just for something to try.
>>>>> :-( It made no difference. I pinged the gateway, largely so
>>>>> that I could report that I had done so. I got the error message
>>>>> "Network is unreachable".
>>>>>
>>>>> KControl tells me that eth0 is "disabled". How and why is it
>>>>> disabled? More importantly, **how do I enable it?**
>>>
>>> # ifup -a
>>> ifup: failed to open statefile /run/network/ifstate: No such file
>>> or directory
>>
>> "ifup -a" should bring up all interfaces marked "auto" (or
>> "allow-auto") in "/etc/network/interfaces". (Is the latter OK?)
>>
>> The "networking" init script must (I haven't checked it) create
>> "/run/network". etc.
>>
>> Change the shebang of "/etc/init.d/networking" to "#!/bin/sh -ex"
>> and run "/etc/init.d/networking stop" then "/etc/init.d/networking
>> start".
>
> Done.
> #ping 192.168.0.1
> connect: Network is unreachable
>
> :-(
:(
Indeed!
Did the "-x" make the start of the daemon more verbose?
Reply to: