[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: eth0 "disabled" after upgrade Squeeze to Wheezy



On Friday 15 November 2013 18:33:21 Tom H wrote:
> 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:
>>>>>>  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?

Not noticeably, but the beginning was out of reach anyway.  (Konsole 
will only go back so far.)

I see that there are in fact error messages during the operation of 
the daemon.  But the main problem must still be whatever is 
overwriting everything to do with networks.

Thanks, guys,
Lisi


Reply to: