Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #167938 > unrolled thread

/etc/init.d/networking does not start everything in /etc/network/interfaces

Back to article view | Back to linux.debian.user

Contents

  /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 14:10 +0200
    Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Peter Ludikovsky <peter@ludikovsky.name> - 2016-05-17 14:20 +0200
      Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 14:40 +0200
    Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Elimar Riesebieter <riesebie@lxtec.de> - 2016-05-17 14:20 +0200
      Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Mimiko <vbvbrj@gmail.com> - 2016-05-17 14:40 +0200
        Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Gilles Mocellin <gilles.mocellin@nuagelibre.org> - 2016-05-17 19:20 +0200
          Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Elimar Riesebieter <riesebie@lxtec.de> - 2016-05-17 19:30 +0200
            Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-18 13:40 +0200
              Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-18 16:00 +0200
              Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Elimar Riesebieter <riesebie@lxtec.de> - 2016-05-18 16:00 +0200
                Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces <tomas@tuxteam.de> - 2016-05-18 16:10 +0200
              Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-18 17:00 +0200
                Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces <tomas@tuxteam.de> - 2016-05-18 17:10 +0200
                  Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-18 17:20 +0200
                    Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-18 17:40 +0200
                      Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-18 18:00 +0200
                        Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-18 18:10 +0200
                    Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Curt <curty@free.fr> - 2016-05-19 17:20 +0200
                Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Darac Marjal <mailinglist@darac.org.uk> - 2016-05-18 17:40 +0200
                Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces David Wright <deblis@lionunicorn.co.uk> - 2016-05-18 18:00 +0200
                  Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Brian <ad44@cityscape.co.uk> - 2016-05-18 18:50 +0200
                    Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces David Wright <deblis@lionunicorn.co.uk> - 2016-05-18 19:40 +0200
                      Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Brian <ad44@cityscape.co.uk> - 2016-05-19 00:40 +0200
          Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 21:00 +0200
            Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces David Wright <deblis@lionunicorn.co.uk> - 2016-05-17 21:40 +0200
      Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 15:00 +0200
      Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces <tomas@tuxteam.de> - 2016-05-17 15:10 +0200
        Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Elimar Riesebieter <riesebie@lxtec.de> - 2016-05-17 15:50 +0200
          Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces <tomas@tuxteam.de> - 2016-05-17 15:50 +0200
        Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 16:00 +0200
          Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Elimar Riesebieter <riesebie@lxtec.de> - 2016-05-17 16:40 +0200
            RE: /etc/init.d/networking does not start everything in  /etc/network/interfaces Bonno Bloksma <b.bloksma@tio.nl> - 2016-05-17 17:20 +0200
            Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-17 17:30 +0200
            Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 17:30 +0200
              Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces David Wright <deblis@lionunicorn.co.uk> - 2016-05-17 18:50 +0200
                Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 20:10 +0200
                Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces <tomas@tuxteam.de> - 2016-05-18 11:00 +0200
                  Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces David Wright <deblis@lionunicorn.co.uk> - 2016-05-18 19:30 +0200
              Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Elimar Riesebieter <riesebie@lxtec.de> - 2016-05-17 19:30 +0200
                Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-17 21:20 +0200
                  Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces Andy Smith <andy@strugglers.net> - 2016-05-17 21:30 +0200
                    Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-18 00:50 +0200
                      Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-18 01:40 +0200
                        Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Gene Heskett <gheskett@shentel.net> - 2016-05-18 04:10 +0200
            Re: /etc/init.d/networking does not start everything in  /etc/network/interfaces David Wright <deblis@lionunicorn.co.uk> - 2016-05-17 20:30 +0200
    Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Rodary Jacques <rodaryj@free.fr> - 2016-05-20 19:30 +0200
      Re: /etc/init.d/networking does not start everything in /etc/network/interfaces Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-20 20:10 +0200

Page 3 of 3 — ← Prev page 1 2 [3]

#167975 — Re: /etc/init.d/networking does not start everything in /etc/network/interfaces

[Multipart message — attachments visible in raw view] — view raw

Hi Gene,

On Tue, May 17, 2016 at 03:12:45PM -0400, Gene Heskett wrote:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.1.3/255.255.255.0 broadcast 192.168.1.255 	  dev eth1 label eth1
> RTNETLINK answers: File exists
> Failed to bring up eth1.
> run-parts --verbose /etc/network/if-up.d
> run-parts: executing /etc/network/if-up.d/avahi-autoipd
> run-parts: executing /etc/network/if-up.d/avahi-daemon
> run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
> run-parts: executing /etc/network/if-up.d/mountnfs
> run-parts: executing /etc/network/if-up.d/ntpdate
> run-parts: executing /etc/network/if-up.d/openssh-server
> run-parts: executing /etc/network/if-up.d/upstart
> run-parts: executing /etc/network/if-up.d/wpasupplicant
> done.
> ====================
> It makes no attempt to shut down eth1, so of course it exists.
> 
> Here is the REAL bug.

I think this problem is quite likely to be as a result of the things
you did in the earlier thread, where you were manually setting eth1
up with ifconfig.

It is a known deficiency of ifupdown that it doesn't know the state
of the system unless it made those state changes itself. It did not
do anything to eth1 because you hadn't earlier told it to manage
eth1. So when it came to shut down all interfaces it didn't do
anything with eth1. And then later when it tries to configure it, it
finds it is already configured.

I think that possibly you could return things to a state that
ifupdown can cope with by either rebooting, or by manually removing
the IP address from eth1 and setting it down:

# ip addr del 192.168.1.3/24 dev eth1
# ip link set down dev eth1

Then assuming eth1 is correctly configured in
/etc/network/interfaces (which you have not yet shown us in full, so
we don't know for sure), I would think that ifup -a and ifdown -a
would work as expected.

But, is this not now all academic since the task you needed this
interface for is done?

Cheers,
Andy

-- 
http://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#167978

On Tuesday 17 May 2016 15:25:47 Andy Smith wrote:

> Hi Gene,
>
> On Tue, May 17, 2016 at 03:12:45PM -0400, Gene Heskett wrote:
> > Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> > ip addr add 192.168.1.3/255.255.255.0 broadcast 192.168.1.255 	  dev
> > eth1 label eth1 RTNETLINK answers: File exists
> > Failed to bring up eth1.
> > run-parts --verbose /etc/network/if-up.d
> > run-parts: executing /etc/network/if-up.d/avahi-autoipd
> > run-parts: executing /etc/network/if-up.d/avahi-daemon
> > run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
> > run-parts: executing /etc/network/if-up.d/mountnfs
> > run-parts: executing /etc/network/if-up.d/ntpdate
> > run-parts: executing /etc/network/if-up.d/openssh-server
> > run-parts: executing /etc/network/if-up.d/upstart
> > run-parts: executing /etc/network/if-up.d/wpasupplicant
> > done.
> > ====================
> > It makes no attempt to shut down eth1, so of course it exists.
> >
> > Here is the REAL bug.
>
> I think this problem is quite likely to be as a result of the things
> you did in the earlier thread, where you were manually setting eth1
> up with ifconfig.
>
> It is a known deficiency of ifupdown that it doesn't know the state
> of the system unless it made those state changes itself. It did not
> do anything to eth1 because you hadn't earlier told it to manage
> eth1. So when it came to shut down all interfaces it didn't do
> anything with eth1. And then later when it tries to configure it, it
> finds it is already configured.
>
> I think that possibly you could return things to a state that
> ifupdown can cope with by either rebooting, or by manually removing
> the IP address from eth1 and setting it down:
>
> # ip addr del 192.168.1.3/24 dev eth1
> # ip link set down dev eth1
>
> Then assuming eth1 is correctly configured in
> /etc/network/interfaces (which you have not yet shown us in full, so
> we don't know for sure), I would think that ifup -a and ifdown -a
> would work as expected.
>
No, it still does not shutdown eth1. Then it does the opposite at uptime
and NETLINK says file exists, failed to start eth1. But ifconfig says is
configured again.  I've reset that router so lets see if I can see it at
192.168.1.1 with a browser.  Nope, unreachable. Route -n says that route
is there.  ifconfig says it is configured correctly.

So, why do I get this error now?
 
ip addr add 192.168.1.3/255.255.255.0 broadcast 192.168.1.255 dev eth1 label eth1
ip link set dev eth1   up
ip route add default via 192.168.1.1  dev eth1 
RTNETLINK answers: File exists
Failed to bring up eth1.

> But, is this not now all academic since the task you needed this
> interface for is done?
>
> Cheers,
> Andy

Yes and no, I have another router (the one I took out yesterday) to do 
the same hard reset & reconfigure on, but will probably tackle that 
long before I reboot. See above.

The bottom line is that it seems I have destroyed the setup I did have 
working yesterday.  And I'm lost again.

But I just got it, I noted no green leds for occupied LAN sockets,
push the plug in another 1/8 inch and bingo, its alive for firefox.
Damn these molded cables.  Gimme on I made anytime.

And I am looking at the mandatory change username & password screen 
of a never configured dd-wrt install.

So I'm off to reconfigure this one again.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#167981

On Tuesday 17 May 2016 23:43:08 Gene Heskett wrote:
[snip]

If it ain't broke, hit it with a hammer? ;-)

Lisi

[toc] | [prev] | [next] | [standalone]

#167988

On Tuesday 17 May 2016 19:30:06 Lisi Reisz wrote:

> On Tuesday 17 May 2016 23:43:08 Gene Heskett wrote:
> [snip]
>
> If it ain't broke, hit it with a hammer? ;-)
>
> Lisi

Yup, have you got a bigger one my lady?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#167970 — Re: /etc/init.d/networking does not start everything in /etc/network/interfaces

On Tue 17 May 2016 at 16:38:52 (+0200), Elimar Riesebieter wrote:
> * Gene Heskett <gheskett@shentel.net> [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 tomas@tuxteam.de wrote:
> [...]
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems exaggerated to me.
> > >
> > > [1] Schocking Truth! Not everything seen on the Internet is true!
> > 
> > About 4th or 5th down in that list of hits, this one labeled for debian, 
> > is a bit long winded  but finishes up recommending one edit his 
> > personal .bash-aliases file to contain this:
> > 
> > alias netrestart="sudo nohup sh -c 'invoke-rc.d networking stop; date; 
> > echo sleeping; sleep 2; echo waking; date; invoke-rc.d networking 
> > start'"
> > 
> > Is that simple?  Elegant and correct?  No, if the networking script was 
> > broken, its still broken!
> 
> Again, I recommend to read [0] and [1].
> 
> [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550240

My reading of this is:

Problem: A doesn't work.

Solution: Put message in B saying B might not work.

Is that right? And is it helpful to Gene?

> [1] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

I'm not sure what this has to do with the problem in hand.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#168099

[Multipart message — attachments visible in raw view] — view raw

I read quite a lot of the answers to your post, and I still think there is a problem, not 
linked to the kernel's interface name name. I have a wifi interface named *everywhere* 
wlan0. It isn't found  by network-pre.target, network-target or networking-service, I 
don't know which one. What I know is bind9 (named in fact) can't start, because 
/etc/insserv.conf asks for $network to start $named; after boot, when network is 
started there is no problem starting named by hand with: 
"named -u named -t /my-chroot-dir -c /etc/named.conf"
 but bind9.service doesn' start and tells me:
 Drop-In: /run/systemd/generator/bind9.service
└─50-insserv.conf-$named.conf
I suppose it's a bug, but as it works like this!! (See bind9-named post in debian-user-
french list
		Jacques

[toc] | [prev] | [next] | [standalone]

#168101

On Friday 20 May 2016 18:08:37 Rodary Jacques wrote:
> I read quite a lot of the answers to your post, and I still think there is
> a problem, not linked to the kernel's interface name name. I have a wifi
> interface named *everywhere* wlan0. It isn't found  by network-pre.target,
> network-target or networking-service, I don't know which one. What I know
> is bind9 (named in fact) can't start, because /etc/insserv.conf asks for
> $network to start $named; after boot, when network is started there is no
> problem starting named by hand with:
> "named -u named -t /my-chroot-dir -c /etc/named.conf"
>  but bind9.service doesn' start and tells me:
>  Drop-In: /run/systemd/generator/bind9.service
> └─50-insserv.conf-$named.conf
> I suppose it's a bug, but as it works like this!! (See bind9-named post in
> debian-user- french list


That was your problem, but it cannot be Gene's, because he is running Wheezy.

Lisi

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | linux.debian.user

csiph-web