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

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

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

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

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

On 2016-05-18, Gene Heskett 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

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

On Wed 18 May 2016 at 12:32:24 -0500, David Wright wrote: > On Wed 18 May 2016 at 17:39:45 (+0100), Brian wrote: > > On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote: > > > > > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote: > > > > > > > > auto lo eth0 eth1 > > > > > >

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

On Wed 18 May 2016 at 17:39:45 (+0100), Brian wrote: > On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote: > > > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote: > > > > > > auto lo eth0 eth1 > > > > Agree with Lisi, I've never seen this (though I'm not claiming it's > > either

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

On Wed 18 May 2016 at 10:50:23 (+0200), to...@tuxteam.de wrote: > On Tue, May 17, 2016 at 11:22:29AM -0500, David Wright wrote: > > On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote: > > [...] What was snipped is "I do not see that as a disadvantage, udev can do that much unwanted

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

On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote: > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote: > > > > auto lo eth0 eth1 > > Agree with Lisi, I've never seen this (though I'm not claiming it's > either wrong or harmful). It's an ok line. From interfaces(5): Lines

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

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

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

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

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 [2016-05-17 19:09 > +0200]: > > > > Le 17/05/2016 à 14:34,

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

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

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

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 [2016-05-17 19:09 +0200]: > > Le 17/05/2016 à 14:34, Mimiko a écrit

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

On Wednesday 18 May 2016 11:01:39 to...@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

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

On Wednesday 18 May 2016 07:31:34 Lisi Reisz wrote: > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote: > > * Gilles Mocellin [2016-05-17 19:09 +0200]: > > > Le 17/05/2016 à 14:34, Mimiko a écrit : > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote: >

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 [2016-05-17

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 [2016-05-18 12:31 +0100]: > > > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote: > [...] > > > /etc/init.d/networking stop does ifdown

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

On Wednesday 18 May 2016 14:42:27 Elimar Riesebieter wrote: > * Lisi Reisz [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 > >

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

* Lisi Reisz [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 '&&'

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

On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote: > * Gilles Mocellin [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

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 17, 2016 at 11:22:29AM -0500, David Wright wrote: > On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote: [...] > You don't see any disadvantage to removing the "hotplug stuff". > Hooray, let's go back to PCs as static boxes. Shut

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

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:

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

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

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

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 > >

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

On Tue 17 May 2016 at 14:51:57 (-0400), Gene Heskett wrote: > Interesting is that in a man 5 interfaces, it says the gateway address is > colon delimited. I don't recall ever seeing that since my first install > in early 1998. Does anyone ever actually read these man pages but me? Yes, but I

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

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

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

On Tuesday 17 May 2016 13:26:35 Elimar Riesebieter wrote: > * Gene Heskett [2016-05-17 11:26 -0400]: > > [...] > > > Because of some rare condition, you make > > all the other users with a less rare condition suffer? > > I was just talking about facts, nothing else. If you

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

On Tuesday 17 May 2016 13:09:33 Gilles Mocellin wrote: > 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 > >

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 [2016-05-17 09:56 -0400]: > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote: > [...] > > > In my opinion, a warning is in order ("this might not be doing > > > what you think it

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

On Tuesday 17 May 2016 12:22:29 David Wright wrote: > On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote: > > On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote: > > > * Gene Heskett [2016-05-17 09:56 -0400]: > > > > On Tuesday 17 May 2016 09:08:55

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

* Gilles Mocellin [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

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

* Gene Heskett [2016-05-17 11:26 -0400]: [...] > Because of some rare condition, you make > all the other users with a less rare condition suffer? I was just talking about facts, nothing else. If you open /etc/init.d/networking (ifupdown_0.7.8) in an editor and scroll

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`

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

On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote: > On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote: > > * Gene Heskett [2016-05-17 09:56 -0400]: > > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote: > > [...] > > > > In my opinion, a warning is in

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

On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote: > * Gene Heskett [2016-05-17 09:56 -0400]: > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote: > > [...] > > > > In my opinion, a warning is in order ("this might not be doing > > > what you think it does"),

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

On Tuesday 17 May 2016 15:38:52 Elimar Riesebieter wrote: > * Gene Heskett [2016-05-17 09:56 -0400]: > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote: > > [...] > > > > In my opinion, a warning is in order ("this might not be doing > > > what you think it does"),

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

Hi Elimar, >> On Tuesday 17 May 2016 09:08:55 to...@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. >> > >> > regards >> > >> > [1] Schocking Truth! Not everything seen on the

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

* Gene Heskett [2016-05-17 09:56 -0400]: > On Tuesday 17 May 2016 09:08:55 to...@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. > > > > regards > > > > [1]

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

On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote: > On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote: > > [...] > > > Ask your search engine: "init.d/networking restart is deprecated" > > I don't know about yours, but *my* /etc/init.d/networking is alive > and healthy!

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 17, 2016 at 03:36:58PM +0200, Elimar Riesebieter wrote: [...] > I don't understand why "init.d/networking restart is deprecated" is > scaring off people? It is a matter of fact! Reading the results will > give all answers a user want.

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

* to...@tuxteam.de [2016-05-17 15:08 +0200]: > On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote: > > [...] > > > Ask your search engine: "init.d/networking restart is deprecated" > > I don't know about yours, but *my* /etc/init.d/networking is alive > and

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote: [...] > Ask your search engine: "init.d/networking restart is deprecated" I don't know about yours, but *my* /etc/init.d/networking is alive and healthy! More to the point, it's so

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

On Tuesday 17 May 2016 08:16:32 Elimar Riesebieter wrote: > * Gene Heskett [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

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.

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

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,

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

* Gene Heskett [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

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

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