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 1 of 3  [1] 2 3  Next page →

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

Greetings all;

32 bit Debian wheezy, updated at least daily.

This fact was brought to my attention because I needed a path to a router 
I needed to do a hard reset on, and reconfigure to do my stuff, but my 
normal home network isn't on the usual 192.168.1.1 class C, and a hard 
reset puts the router back to the 1.1 address.

So in order to use eth1 as a path to this router, I have to do a separate

sudo ifconfig eth1 up

as a sudo service networking restart will not restart the second eth1 
stanza in my interfaces file, starting only eth0.

Normally the interface is not even graced with a cat5 in the socket, and 
ATM it is but the far end of 5 feet of cat5 is laying on the floor.

Is it possible to make this init.d/networking script start everything it 
finds in the interfaces file?

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] | [next] | [standalone]

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

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

In /etc/network/interfaces change
    allow-hotplug eth1
to
    auto eth1

Regards,
/peter

Am 17.05.2016 um 14:05 schrieb Gene Heskett:
> Greetings all;
> 
> 32 bit Debian wheezy, updated at least daily.
> 
> This fact was brought to my attention because I needed a path to a router 
> I needed to do a hard reset on, and reconfigure to do my stuff, but my 
> normal home network isn't on the usual 192.168.1.1 class C, and a hard 
> reset puts the router back to the 1.1 address.
> 
> So in order to use eth1 as a path to this router, I have to do a separate
> 
> sudo ifconfig eth1 up
> 
> as a sudo service networking restart will not restart the second eth1 
> stanza in my interfaces file, starting only eth0.
> 
> Normally the interface is not even graced with a cat5 in the socket, and 
> ATM it is but the far end of 5 feet of cat5 is laying on the floor.
> 
> Is it possible to make this init.d/networking script start everything it 
> finds in the interfaces file?
> 
> Cheers, Gene Heskett
> 

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

#167943

On Tuesday 17 May 2016 08:11:50 Peter Ludikovsky wrote:

> In /etc/network/interfaces change
>     allow-hotplug eth1
> to
>     auto eth1

Blind as a bat, gonna have to get my cateracts fixed as I didn't see 
that. I don't have the allow-hotplug line, but the auto line didn't have 
eth1, added, works, that you very much Peter.

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]

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

* Gene Heskett <gheskett@shentel.net> [2016-05-17 08:05 -0400]:

> Greetings all;
> 
> 32 bit Debian wheezy, updated at least daily.
> 
> This fact was brought to my attention because I needed a path to a router 
> I needed to do a hard reset on, and reconfigure to do my stuff, but my 
> normal home network isn't on the usual 192.168.1.1 class C, and a hard 
> reset puts the router back to the 1.1 address.
> 
> So in order to use eth1 as a path to this router, I have to do a separate
> 
> sudo ifconfig eth1 up
> 
> as a sudo service networking restart will not restart the second eth1 
> stanza in my interfaces file, starting only eth0.
> 
> Normally the interface is not even graced with a cat5 in the socket, and 
> ATM it is but the far end of 5 feet of cat5 is laying on the floor.
> 
> Is it possible to make this init.d/networking script start everything it 
> finds in the interfaces file?

Ask your search engine: "init.d/networking restart is deprecated"

Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
         Friedrich Nietzsche

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

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

On 17.05.2016 15:16, Elimar Riesebieter wrote:
> Ask your search engine: "init.d/networking restart is deprecated"

This was the only tool to fully restart all networking even the 
interface thru which connection is made.
Are the `ifdown eth & ifup eth` the only option now?

-- 
Mimiko desu.

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

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

Le 17/05/2016 à 14:34, Mimiko a écrit :
> On 17.05.2016 15:16, Elimar Riesebieter wrote:
>> Ask your search engine: "init.d/networking restart is deprecated"
>
> This was the only tool to fully restart all networking even the 
> interface thru which connection is made.
> Are the `ifdown eth & ifup eth` the only option now?
>

Just to add these commands in that thread.

To restart all the interfaces as they are defined in 
/etc/network/interfaces, I do :

# ifdown -a; ifup -a

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

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

* Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17 19:09 +0200]:

> Le 17/05/2016 à 14:34, Mimiko a écrit :
> > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > Ask your search engine: "init.d/networking restart is deprecated"
> > 
> > This was the only tool to fully restart all networking even the
> > interface thru which connection is made.
> > Are the `ifdown eth & ifup eth` the only option now?
> > 
> 
> Just to add these commands in that thread.
> 
> To restart all the interfaces as they are defined in
> /etc/network/interfaces, I do :
> 
> # ifdown -a; ifup -a

/etc/init.d/networking stop does ifdown -a
/etc/init.d/networking start does ifup -a

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

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

#168004

On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> * Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17 19:09 +0200]:
> > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > Ask your search engine: "init.d/networking restart is deprecated"
> > >
> > > This was the only tool to fully restart all networking even the
> > > interface thru which connection is made.
> > > Are the `ifdown eth & ifup eth` the only option now?
> >
> > Just to add these commands in that thread.
> >
> > To restart all the interfaces as they are defined in
> > /etc/network/interfaces, I do :
> >
> > # ifdown -a; ifup -a
>
> /etc/init.d/networking stop does ifdown -a
> /etc/init.d/networking start does ifup -a

But 
# ifdown -a; ifup -a
is much more elegant!!

Lisi

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

#168013

On Wednesday 18 May 2016 14:42:27 Elimar Riesebieter wrote:
> * Lisi Reisz <lisi.reisz@gmail.com> [2016-05-18 12:31 +0100]:
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
>
> [...]
>
> > > /etc/init.d/networking stop does ifdown -a
> > > /etc/init.d/networking start does ifup -a
> >
> > But
> > # ifdown -a; ifup -a
> > is much more elegant!!
>
> I would use '&&' in favour of ';' as ';' doesn't wait to complete
> the job:
>
> # ifdown -a && ifup -a

Sorry.  Granted.  I should ghave thought of that. 

> is much more secure!!

BUT if ifdown doesn't successfully complete, it is surely not insecure?  You 
just might not achieve your objective of restarting the whole caboosh.

Lisi

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

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

* Lisi Reisz <lisi.reisz@gmail.com> [2016-05-18 12:31 +0100]:

> On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
[...]
> > /etc/init.d/networking stop does ifdown -a
> > /etc/init.d/networking start does ifup -a
> 
> But 
> # ifdown -a; ifup -a
> is much more elegant!!

I would use '&&' in favour of ';' as ';' doesn't wait to complete
the job:

# ifdown -a && ifup -a

is much more secure!!

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

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

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, May 18, 2016 at 03:42:27PM +0200, Elimar Riesebieter wrote:
> * Lisi Reisz <lisi.reisz@gmail.com> [2016-05-18 12:31 +0100]:
> 
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> [...]
> > > /etc/init.d/networking stop does ifdown -a
> > > /etc/init.d/networking start does ifup -a
> > 
> > But 
> > # ifdown -a; ifup -a
> > is much more elegant!!
> 
> I would use '&&' in favour of ';' as ';' doesn't wait to complete
> the job:

It *does* wait[1] -- it just would continue doing the second part regardless
of the exit status of the first. So if the ifdown part exits with nonzero
(most probably signaling an error), the ifup part would be tried nevertheless.

So in this case, probably

> # ifdown -a && ifup -a

would be the right thing, as you say.

> is much more secure!!

That depends on what you want. Perhaps (probably not in this case, though)
you really want the second, third... command executed in any case. Then
the semicolon would be The Right Thing [TM]

regards

[1] As you can easily check yourself by issuing:

  sleep 10 ; echo "good morning"

- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlc8dcsACgkQBcgs9XrR2kaEaACfT7rPm/3SWV5eoI1pBZr900ey
kgMAnih/p/+vdJkkp0FiAxmid6/7spui
=xjHH
-----END PGP SIGNATURE-----

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

#168018

On Wednesday 18 May 2016 07:31:34 Lisi Reisz wrote:

> On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> > * Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17 19:09 
+0200]:
> > > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > Ask your search engine: "init.d/networking restart is
> > > > > deprecated"
> > > >
> > > > This was the only tool to fully restart all networking even the
> > > > interface thru which connection is made.
> > > > Are the `ifdown eth & ifup eth` the only option now?
> > >
> > > Just to add these commands in that thread.
> > >
> > > To restart all the interfaces as they are defined in
> > > /etc/network/interfaces, I do :
> > >
> > > # ifdown -a; ifup -a
> >
> > /etc/init.d/networking stop does ifdown -a
> > /etc/init.d/networking start does ifup -a
>
> But
> # ifdown -a; ifup -a
> is much more elegant!!
>
> Lisi

If it worked, but no one, including me, has found where the database of 
devices the -a is supposed to manage.  Apparently this is written at 
boot time. And I have no reason to reboot.

But if some kind soul knows where this database is, or knows of a utility 
that would update it once I have enabled the 2nd RJ45 jack as eth1, now 
that will get a hearty thank you and a tip of my hat in his/her 
direction.   And in terms of hand editing a file, it looks 
like /etc/network/run/ifstate may be that file. It currently contains:
lo=lo
eth0=eth0
so I fired up a root editor and added it. But a sudo service networking 
restart failed, and erased my hand edit from that file.

Snips from the verbose output of the restart:
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-down.d/upstart
run-parts: executing /etc/network/if-down.d/wpasupplicant
 ip route del default via 192.168.1.1  dev eth1 2>&1 1>/dev/null || true 
RTNETLINK answers: No such process
ip -4 addr flush dev eth1 label eth1
ip link set dev eth1 down

So that looks like it worked.  Later;
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
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.....  that router is still connected
gene@coyote:/etc/udev/rules.d$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.831 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.340 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.342 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.347 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.480 ms
64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=0.287 ms
^C
--- 192.168.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 0.287/0.437/0.831/0.187 ms

So despite the apparent failure, which seems to cause RTNETLINK to 
excrete the bogus fail message, and remove the eh1=eth1 from the ifstate 
file, it does work, but adding that line to the ifstate file everytime 
sure seems like the wrong way. FWIW that file is a link, 
to /var/run/network/ifstate.  And its date is updated when networking 
restart is executed.

RTNETLINK cannot find it going either way. But at least networking can 
find it, one time only.  And that is about as close to the bug as I can 
get, and thats not close enough to fix it.  Somebody else's turn if 
they've a mind to.

The real failure seems to be:
(why the leading space?)
 ip route del default via 192.168.1.1  dev eth1 2>&1 1>/dev/null || true

which if repeated from a root account, should I think, delete that route 
from the routing table, but it does not, the address remains:

root@coyote:/etc/network# ip route del default via 192.168.1.1  dev eth1
RTNETLINK answers: No such process
root@coyote:/etc/network# route -n
Kernel IP routing table
Destination    Gateway        Genmask       Flags Metric Ref    Use Iface
0.0.0.0        192.168.71.1   0.0.0.0       UG    0      0      0   eth0
169.254.0.0    0.0.0.0        255.255.0.0   U     1000   0      0   eth0
192.168.1.0    0.0.0.0        255.255.255.0 U     0      0      0   eth1
192.168.71.0   0.0.0.0        255.255.255.0 U     0      0      0   eth0

And the route to 1.0 remains, and the router is still pingable. I am 
seeing that sockets led on the router blink at every ping.

Now,  for those complaining about my lack of posting the complete 
interfaces file, here it is:
--------------------------------------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo eth0 eth1

# The loopback network interface
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# regular network for coyote.den
iface eth0 inet static
address 192.168.71.3
netmask 255.255.255.0
gateway 192.168.71.1

# to access reset routers at 192.168.1.1 on the 2nd cat5 port
iface eth1 inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.1
---------------------thats all folks!-------------
Thanks.

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]

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, May 18, 2016 at 10:56:01AM -0400, Gene Heskett wrote:
> On Wednesday 18 May 2016 07:31:34 Lisi Reisz wrote:
> 
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> > > * Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17 19:09 
> +0200]:
> > > > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > > Ask your search engine: "init.d/networking restart is
> > > > > > deprecated"
> > > > >
> > > > > This was the only tool to fully restart all networking even the
> > > > > interface thru which connection is made.
> > > > > Are the `ifdown eth & ifup eth` the only option now?
> > > >
> > > > Just to add these commands in that thread.
> > > >
> > > > To restart all the interfaces as they are defined in
> > > > /etc/network/interfaces, I do :
> > > >
> > > > # ifdown -a; ifup -a
> > >
> > > /etc/init.d/networking stop does ifdown -a
> > > /etc/init.d/networking start does ifup -a
> >
> > But
> > # ifdown -a; ifup -a
> > is much more elegant!!
> >
> > Lisi
> 
> If it worked, but no one, including me, has found where the database of 
> devices the -a is supposed to manage.  Apparently this is written at 
> boot time. And I have no reason to reboot.

I think this has been mentioned in this thread already: -a does
*exactly* those devices tagged as "auto" in /etc/network/interfaces.

So that should be the database you're looking for? Try, for starters

  grep auto /etc/network/interfaces

But perhaps I'm missing something.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlc8g9MACgkQBcgs9XrR2kY8UwCfdl9wJVODB45RkloTNDWakQVj
agoAnREM5FBay+Ao4MRsRGQlBgXlw2DQ
=WDBa
-----END PGP SIGNATURE-----

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

#168022

On Wednesday 18 May 2016 11:01:39 tomas@tuxteam.de wrote:

> On Wed, May 18, 2016 at 10:56:01AM -0400, Gene Heskett wrote:
> > On Wednesday 18 May 2016 07:31:34 Lisi Reisz wrote:
> > > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> > > > * Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17
> > > > 19:09
> >
> > +0200]:
> > > > > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > > > Ask your search engine: "init.d/networking restart is
> > > > > > > deprecated"
> > > > > >
> > > > > > This was the only tool to fully restart all networking even
> > > > > > the interface thru which connection is made.
> > > > > > Are the `ifdown eth & ifup eth` the only option now?
> > > > >
> > > > > Just to add these commands in that thread.
> > > > >
> > > > > To restart all the interfaces as they are defined in
> > > > > /etc/network/interfaces, I do :
> > > > >
> > > > > # ifdown -a; ifup -a
> > > >
> > > > /etc/init.d/networking stop does ifdown -a
> > > > /etc/init.d/networking start does ifup -a
> > >
> > > But
> > > # ifdown -a; ifup -a
> > > is much more elegant!!
> > >
> > > Lisi
> >
> > If it worked, but no one, including me, has found where the database
> > of devices the -a is supposed to manage.  Apparently this is written
> > at boot time. And I have no reason to reboot.
>
> I think this has been mentioned in this thread already: -a does
> *exactly* those devices tagged as "auto" in /etc/network/interfaces.
>
> So that should be the database you're looking for? Try, for starters
>
>   grep auto /etc/network/interfaces

auto lo eth0 eth1

Its there in the complete interfaces file I just posted, and you snipped.

> But perhaps I'm missing something.
>
> Regards
> -- tomás


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]

#168024

On Wednesday 18 May 2016 16:14:36 Gene Heskett wrote:
> auto lo eth0 eth1
>
> Its there in the complete interfaces file I just posted, and you snipped.

Gene - we have, I think, established that your set-up doesn't work the way 
predicted.

The one thing that looks very different to me is the sticking of all three 
interfaces in one line like that.  I have always had them separate, each in 
its own section.  Also you have:
address 127.0.0.1
netmask 255.0.0.0
which I haven't sen before.
I can't see they would matter, but something does.

Lisi
-----
Here is my "standard" file;

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# auto eth0
# iface eth0 inet dhcp

# iface eth0 inet static
#       address 192.168.0.2
#       netmask 255.255.255.0
#       gateway 192.168.0.1
#       network 192.168.0.0
#       dns-nameservers 212.23.3.100 212.23.6.100


# The secondary network interface
auto eth1
# iface eth1 inet dhcp

iface eth1 inet static
        address 192.168.0.2
        netmask 255.255.255.0
        gateway 192.168.0.1
        network 192.168.0.0
        dns-nameservers 212.23.3.100 212.23.6.100
----------------------------------------------------
At that point I was only using one, though not necessarily the same one, so I 
ad to comment out as necessary.

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

#168027

On Wednesday 18 May 2016 11:37:59 Lisi Reisz wrote:

> On Wednesday 18 May 2016 16:14:36 Gene Heskett wrote:
> > auto lo eth0 eth1
> >
> > Its there in the complete interfaces file I just posted, and you
> > snipped.
>
> Gene - we have, I think, established that your set-up doesn't work the
> way predicted.
>
> The one thing that looks very different to me is the sticking of all
> three interfaces in one line like that.  I have always had them
> separate, each in its own section.  Also you have:
> address 127.0.0.1
> netmask 255.0.0.0
> which I haven't sen before.
> I can't see they would matter, but something does.
>
> Lisi
> -----
> Here is my "standard" file;
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> # auto eth0
> # iface eth0 inet dhcp
>
> # iface eth0 inet static
> #       address 192.168.0.2
> #       netmask 255.255.255.0
> #       gateway 192.168.0.1
> #       network 192.168.0.0
> #       dns-nameservers 212.23.3.100 212.23.6.100
>
>
> # The secondary network interface
> auto eth1
> # iface eth1 inet dhcp
>
> iface eth1 inet static
>         address 192.168.0.2
>         netmask 255.255.255.0
>         gateway 192.168.0.1
>         network 192.168.0.0
>         dns-nameservers 212.23.3.100 212.23.6.100
> ----------------------------------------------------
> At that point I was only using one, though not necessarily the same
> one, so I ad to comment out as necessary.

I just re-arranged my interfaces file with 3 auto lines like you 
suggested. One iface name above each iface description. No diffs that I 
can see.  As installed it had an
 "auto lo eth0"
line at the top of the file.

Thanks Lisi.

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]

#168029

On Wednesday 18 May 2016 16:54:49 Gene Heskett wrote:
> "auto lo eth0"

auto lo
and 
auto eth0
now??

Lisi

It may not solve anything, but when rationality seems to fail one has to 
resort to magic, and just get the incantation right!!!!

Lisi

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

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

On 2016-05-18, Gene Heskett <gheskett@shentel.net> wrote:
>> *exactly* those devices tagged as "auto" in /etc/network/interfaces.
>>
>> So that should be the database you're looking for? Try, for starters
>>
>>   grep auto /etc/network/interfaces
>
> auto lo eth0 eth1
>
> Its there in the complete interfaces file I just posted, and you snipped.
>
>> But perhaps I'm missing something.
>>
>> Regards
>> -- tomás
>
>
> Cheers, Gene Heskett


I have 

 auto lo
 iface lo inet loopback

 allow-hotplug eth0

in /etc/network/interfaces file on Wheezy LTS.

-- 
Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and
so entirely in harmony with the demagogic appeals to cultural democracy that
accompany (and distract one’s attention from) the ever-tightening grip of 
plutocratic capitalism. - Susan Sontag

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

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

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

On Wed, May 18, 2016 at 10:56:01AM -0400, Gene Heskett wrote:
>On Wednesday 18 May 2016 07:31:34 Lisi Reisz wrote:
>
>> On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
>> > * Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17 19:09
>+0200]:
>> > > Le 17/05/2016 à 14:34, Mimiko a écrit :
>> > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
>> > > > > Ask your search engine: "init.d/networking restart is
>> > > > > deprecated"
>> > > >
>> > > > This was the only tool to fully restart all networking even the
>> > > > interface thru which connection is made.
>> > > > Are the `ifdown eth & ifup eth` the only option now?
>> > >
>> > > Just to add these commands in that thread.
>> > >
>> > > To restart all the interfaces as they are defined in
>> > > /etc/network/interfaces, I do :
>> > >
>> > > # ifdown -a; ifup -a
>> >
>> > /etc/init.d/networking stop does ifdown -a
>> > /etc/init.d/networking start does ifup -a
>>
>> But
>> # ifdown -a; ifup -a
>> is much more elegant!!
>>
>> Lisi
>
>If it worked, but no one, including me, has found where the database of
>devices the -a is supposed to manage.  Apparently this is written at
>boot time. And I have no reason to reboot.

If I'm reading the manpage for ifquery correctly, it's at 
/run/network/ifstate

>
>But if some kind soul knows where this database is, or knows of a utility
>that would update it once I have enabled the 2nd RJ45 jack as eth1, now
>that will get a hearty thank you and a tip of my hat in his/her
>direction.   And in terms of hand editing a file, it looks
>like /etc/network/run/ifstate may be that file. It currently contains:
>lo=lo
>eth0=eth0
>so I fired up a root editor and added it. But a sudo service networking
>restart failed, and erased my hand edit from that file.
>
>Snips from the verbose output of the restart:
>Configuring interface eth1=eth1 (inet)
>run-parts --verbose /etc/network/if-down.d
>run-parts: executing /etc/network/if-down.d/avahi-autoipd
>run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
>run-parts: executing /etc/network/if-down.d/upstart
>run-parts: executing /etc/network/if-down.d/wpasupplicant
> ip route del default via 192.168.1.1  dev eth1 2>&1 1>/dev/null || true
>RTNETLINK answers: No such process
>ip -4 addr flush dev eth1 label eth1
>ip link set dev eth1 down
>
>So that looks like it worked.  Later;
>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
>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.....  that router is still connected
>gene@coyote:/etc/udev/rules.d$ ping 192.168.1.1
>PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
>64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.831 ms
>64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.340 ms
>64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.342 ms
>64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.347 ms
>64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.480 ms
>64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=0.287 ms
>^C
>--- 192.168.1.1 ping statistics ---
>6 packets transmitted, 6 received, 0% packet loss, time 4999ms
>rtt min/avg/max/mdev = 0.287/0.437/0.831/0.187 ms
>
>So despite the apparent failure, which seems to cause RTNETLINK to
>excrete the bogus fail message, and remove the eh1=eth1 from the ifstate
>file, it does work, but adding that line to the ifstate file everytime
>sure seems like the wrong way. FWIW that file is a link,
>to /var/run/network/ifstate.  And its date is updated when networking
>restart is executed.
>
>RTNETLINK cannot find it going either way. But at least networking can
>find it, one time only.  And that is about as close to the bug as I can
>get, and thats not close enough to fix it.  Somebody else's turn if
>they've a mind to.
>
>The real failure seems to be:
>(why the leading space?)
> ip route del default via 192.168.1.1  dev eth1 2>&1 1>/dev/null || true
>
>which if repeated from a root account, should I think, delete that route
>from the routing table, but it does not, the address remains:
>
>root@coyote:/etc/network# ip route del default via 192.168.1.1  dev eth1
>RTNETLINK answers: No such process
>root@coyote:/etc/network# route -n
>Kernel IP routing table
>Destination    Gateway        Genmask       Flags Metric Ref    Use Iface
>0.0.0.0        192.168.71.1   0.0.0.0       UG    0      0      0   eth0
>169.254.0.0    0.0.0.0        255.255.0.0   U     1000   0      0   eth0
>192.168.1.0    0.0.0.0        255.255.255.0 U     0      0      0   eth1
>192.168.71.0   0.0.0.0        255.255.255.0 U     0      0      0   eth0
>
>And the route to 1.0 remains, and the router is still pingable. I am
>seeing that sockets led on the router blink at every ping.
>
>Now,  for those complaining about my lack of posting the complete
>interfaces file, here it is:
>--------------------------------------------
># This file describes the network interfaces available on your system
># and how to activate them. For more information, see interfaces(5).
>
>auto lo eth0 eth1
>
># The loopback network interface
>iface lo inet loopback
>address 127.0.0.1
>netmask 255.0.0.0
>
># regular network for coyote.den
>iface eth0 inet static
>address 192.168.71.3
>netmask 255.255.255.0
>gateway 192.168.71.1
>
># to access reset routers at 192.168.1.1 on the 2nd cat5 port
>iface eth1 inet static
>address 192.168.1.3
>netmask 255.255.255.0
>gateway 192.168.1.1
>---------------------thats all folks!-------------
>Thanks.
>
>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>
>

-- 
For more information, please reread.

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

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

On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> On Wednesday 18 May 2016 07:31:34 Lisi Reisz wrote:
> 
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> > > * Gilles Mocellin <gilles.mocellin@nuagelibre.org> [2016-05-17 19:09 
> +0200]:
> > > > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > > Ask your search engine: "init.d/networking restart is
> > > > > > deprecated"
> > > > >
> > > > > This was the only tool to fully restart all networking even the
> > > > > interface thru which connection is made.
> > > > > Are the `ifdown eth & ifup eth` the only option now?
> > > >
> > > > Just to add these commands in that thread.
> > > >
> > > > To restart all the interfaces as they are defined in
> > > > /etc/network/interfaces, I do :
> > > >
> > > > # ifdown -a; ifup -a
> > >
> > > /etc/init.d/networking stop does ifdown -a
> > > /etc/init.d/networking start does ifup -a
> >
> > But
> > # ifdown -a; ifup -a
> > is much more elegant!!
> >
> > Lisi
> 
> If it worked, but no one, including me, has found where the database of 
> devices the -a is supposed to manage.  Apparently this is written at 
> boot time. And I have no reason to reboot.
> 
> But if some kind soul knows where this database is, or knows of a utility 
> that would update it once I have enabled the 2nd RJ45 jack as eth1, now 
> that will get a hearty thank you and a tip of my hat in his/her 
> direction.   And in terms of hand editing a file, it looks 
> like /etc/network/run/ifstate may be that file. It currently contains:
> lo=lo
> eth0=eth0
> so I fired up a root editor and added it. But a sudo service networking 
> restart failed, and erased my hand edit from that file.
> 
> Snips from the verbose output of the restart:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-down.d
> run-parts: executing /etc/network/if-down.d/avahi-autoipd
> run-parts: executing /etc/network/if-down.d/clamav-freshclam-ifupdown
> run-parts: executing /etc/network/if-down.d/upstart
> run-parts: executing /etc/network/if-down.d/wpasupplicant
>  ip route del default via 192.168.1.1  dev eth1 2>&1 1>/dev/null || true 
> RTNETLINK answers: No such process

According to your routing table, the default route doesn't go through
dev eth1, so that line can't work.

(> 0.0.0.0        192.168.71.1   0.0.0.0       UG    0      0      0   eth0)

> ip -4 addr flush dev eth1 label eth1
> ip link set dev eth1 down
> 
> So that looks like it worked.  Later;
> 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
> ip link set dev eth1   up
>  ip route add default via 192.168.1.1  dev eth1 
> RTNETLINK answers: File exists

According to your routing table, the default route is already set up,
so yoou can't have another one.

(> 0.0.0.0        192.168.71.1   0.0.0.0       UG    0      0      0   eth0)

> Failed to bring up eth1.
> 
> But.....  that router is still connected
> gene@coyote:/etc/udev/rules.d$ ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> 64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.831 ms
> 64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.340 ms
> 64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.342 ms
> 64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.347 ms
> 64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.480 ms
> 64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=0.287 ms
> ^C
> --- 192.168.1.1 ping statistics ---
> 6 packets transmitted, 6 received, 0% packet loss, time 4999ms
> rtt min/avg/max/mdev = 0.287/0.437/0.831/0.187 ms
> 
> So despite the apparent failure, which seems to cause RTNETLINK to 
> excrete the bogus fail message, and remove the eh1=eth1 from the ifstate 
> file, it does work, but adding that line to the ifstate file everytime 
> sure seems like the wrong way. FWIW that file is a link, 
> to /var/run/network/ifstate.  And its date is updated when networking 
> restart is executed.
> 
> RTNETLINK cannot find it going either way. But at least networking can 
> find it, one time only.  And that is about as close to the bug as I can 
> get, and thats not close enough to fix it.  Somebody else's turn if 
> they've a mind to.
> 
> The real failure seems to be:
> (why the leading space?)
>  ip route del default via 192.168.1.1  dev eth1 2>&1 1>/dev/null || true
> 
> which if repeated from a root account, should I think, delete that route 
> from the routing table, but it does not, the address remains:
> 
> root@coyote:/etc/network# ip route del default via 192.168.1.1  dev eth1
> RTNETLINK answers: No such process
> root@coyote:/etc/network# route -n
> Kernel IP routing table
> Destination    Gateway        Genmask       Flags Metric Ref    Use Iface
> 0.0.0.0        192.168.71.1   0.0.0.0       UG    0      0      0   eth0
> 169.254.0.0    0.0.0.0        255.255.0.0   U     1000   0      0   eth0
> 192.168.1.0    0.0.0.0        255.255.255.0 U     0      0      0   eth1
> 192.168.71.0   0.0.0.0        255.255.255.0 U     0      0      0   eth0
> 
> And the route to 1.0 remains, and the router is still pingable. I am 
> seeing that sockets led on the router blink at every ping.
> 
> Now,  for those complaining about my lack of posting the complete 
> interfaces file, here it is:
> --------------------------------------------
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> auto lo eth0 eth1
> 
> # The loopback network interface
> iface lo inet loopback
> address 127.0.0.1
> netmask 255.0.0.0

Agree with Lisi, I've never seen this (though I'm not claiming it's
either wrong or harmful).

> # regular network for coyote.den
> iface eth0 inet static
> address 192.168.71.3
> netmask 255.255.255.0
> gateway 192.168.71.1
> 
> # to access reset routers at 192.168.1.1 on the 2nd cat5 port
> iface eth1 inet static
> address 192.168.1.3
> netmask 255.255.255.0
> gateway 192.168.1.1
> ---------------------thats all folks!-------------

Cheers,
David.

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

Page 1 of 3  [1] 2 3  Next page →

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

csiph-web