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

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

restarting network

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

Contents

  restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-28 11:50 +0200
    Re: restarting network Brian <ad44@cityscape.co.uk> - 2016-03-28 15:40 +0200
      Re: restarting network Joe <joe@jretrading.com> - 2016-03-28 20:50 +0200
        Re: restarting network Brian <ad44@cityscape.co.uk> - 2016-03-28 21:10 +0200
          Re: restarting network Joe <joe@jretrading.com> - 2016-03-28 21:50 +0200
      Re: restarting network Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2016-03-28 23:30 +0200
        Re: restarting network "Andrew M.A. Cater" <amacater@galactic.demon.co.uk> - 2016-03-29 00:10 +0200
          Re: restarting network Joe <joe@jretrading.com> - 2016-03-29 09:30 +0200
            Re: restarting network Reco <recoverym4n@gmail.com> - 2016-03-29 09:50 +0200
    Re: restarting network Jörg-Volker Peetz <jvpeetz@web.de> - 2016-03-29 11:10 +0200
    Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-29 12:20 +0200
      Re: restarting network pedantsunited <ad44@cityscape.co.uk> - 2016-03-29 14:00 +0200
        Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-29 14:40 +0200
          Re: restarting network Brian <ad44@cityscape.co.uk> - 2016-03-29 15:10 +0200
            Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-29 15:20 +0200
              Re: restarting network Dan Ritter <dsr@randomstring.org> - 2016-03-29 16:00 +0200
              Re: restarting network Reco <recoverym4n@gmail.com> - 2016-03-29 16:40 +0200
                Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-29 16:50 +0200
                  Re: restarting network Reco <recoverym4n@gmail.com> - 2016-03-29 17:30 +0200
                    Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-29 18:10 +0200
                      Re: restarting network Reco <recoverym4n@gmail.com> - 2016-03-29 18:30 +0200
                        Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-29 18:40 +0200
                          Re: restarting network Reco <recoverym4n@gmail.com> - 2016-03-29 19:20 +0200
                            Re: restarting network Tony van der Hoff <tony@vanderhoff.org> - 2016-03-30 14:20 +0200
                      Re: restarting network Nemeth Gyorgy <friczy@freemail.hu> - 2016-03-29 18:50 +0200
              Re: restarting network Darac Marjal <mailinglist@darac.org.uk> - 2016-03-30 18:40 +0200
                Re: restarting network [SOLVED] Tony van der Hoff <tony@vanderhoff.org> - 2016-04-04 16:20 +0200
                  RE: restarting network [SOLVED] Bonno Bloksma <b.bloksma@tio.nl> - 2016-04-05 13:30 +0200
    RE: restarting network Bonno Bloksma <b.bloksma@tio.nl> - 2016-03-29 13:20 +0200

Page 1 of 2  [1] 2  Next page →

#166020 — restarting network

What is the recommended way of restarting network services after, say, 
changing the parameters in /etc/network/interfaces?

service networking restart doesn't seem to do the job properly.

-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

[toc] | [next] | [standalone]

#166025

On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:

> What is the recommended way of restarting network services after, say,
> changing the parameters in /etc/network/interfaces?

Guessing game number 1: No /e/n/i before; no /e/n/i after; no indication
of which parameters.

> service networking restart doesn't seem to do the job properly.

Guessing game number 2: No description of what is meant by "properly".

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

#166038

On Mon, 28 Mar 2016 14:34:50 +0100
Brian <ad44@cityscape.co.uk> wrote:

> On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> 
> > What is the recommended way of restarting network services after,
> > say, changing the parameters in /etc/network/interfaces?  
> 
> Guessing game number 1: No /e/n/i before; no /e/n/i after; no
> indication of which parameters.
> 
> > service networking restart doesn't seem to do the job properly.  
> 
> Guessing game number 2: No description of what is meant by "properly".
> 

For some years now (long before systemd) we have been advised that
restarting the 'networking' init.d script, even using the
Debian-recommended 'invoke-rc.d', may not bring up all interfaces
correctly, and the only safe way to restart everything was to... well,
restart everything, individually, manually. The 'deprecated' word was
used in anger.

I haven't yet seen any advice superseding this.

-- 
Joe

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

#166039

On Mon 28 Mar 2016 at 19:43:30 +0100, Joe wrote:

> On Mon, 28 Mar 2016 14:34:50 +0100
> Brian <ad44@cityscape.co.uk> wrote:
> 
> > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> > 
> > > What is the recommended way of restarting network services after,
> > > say, changing the parameters in /etc/network/interfaces?  
> > 
> > Guessing game number 1: No /e/n/i before; no /e/n/i after; no
> > indication of which parameters.
> > 
> > > service networking restart doesn't seem to do the job properly.  
> > 
> > Guessing game number 2: No description of what is meant by "properly".
> > 
> 
> For some years now (long before systemd) we have been advised that
> restarting the 'networking' init.d script, even using the
> Debian-recommended 'invoke-rc.d', may not bring up all interfaces
> correctly, and the only safe way to restart everything was to... well,
> restart everything, individually, manually. The 'deprecated' word was
> used in anger.
> 
> I haven't yet seen any advice superseding this.

And until the OP gets his act together you probably won't.

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

#166041

On Mon, 28 Mar 2016 20:07:05 +0100
Brian <ad44@cityscape.co.uk> wrote:

> On Mon 28 Mar 2016 at 19:43:30 +0100, Joe wrote:
> 
> > On Mon, 28 Mar 2016 14:34:50 +0100
> > Brian <ad44@cityscape.co.uk> wrote:
> >   
> > > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> > >   
> > > > What is the recommended way of restarting network services
> > > > after, say, changing the parameters
> > > > in /etc/network/interfaces?    
> > > 
> > > Guessing game number 1: No /e/n/i before; no /e/n/i after; no
> > > indication of which parameters.
> > >   
> > > > service networking restart doesn't seem to do the job
> > > > properly.    
> > > 
> > > Guessing game number 2: No description of what is meant by
> > > "properly". 
> > 
> > For some years now (long before systemd) we have been advised that
> > restarting the 'networking' init.d script, even using the
> > Debian-recommended 'invoke-rc.d', may not bring up all interfaces
> > correctly, and the only safe way to restart everything was to...
> > well, restart everything, individually, manually. The 'deprecated'
> > word was used in anger.
> > 
> > I haven't yet seen any advice superseding this.  
> 
> And until the OP gets his act together you probably won't.
> 

I believe the OP was asking the question: what is the official way to
restart all networking? The answer to this should surely not depend on
what specific problem the OP currently has. If this proposed official
way doesn't work, *then* we need to know in what way it doesn't work,
so that troubleshooting may begin.

I'm simply observing that I'm not aware that there is an official way
to restart networking with a single command i.e. that it may no longer
be possible to programmatically enumerate network interfaces, and that
the user must do this him/herself. Possibly you could shed some light on
this?

I should mention that I still do the 'networking restart' and I haven't
ever had any trouble with it, but I've long been aware of the
'deprecated' message.

-- 
Joe

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

#166045

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

On 29/03/2016 12:34 AM, Brian wrote:
> On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> 
>> What is the recommended way of restarting network services after, say,
>> changing the parameters in /etc/network/interfaces?
> 
> Guessing game number 1: No /e/n/i before; no /e/n/i after; no indication
> of which parameters.
> 
>> service networking restart doesn't seem to do the job properly.
> 
> Guessing game number 2: No description of what is meant by "properly".

What a ridiculous response.  IT was a simple and general question by the OP.

What is the correct answer for the poisoned systemd installation of
Jessie these days????

Kind Regards
AndrewM

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

#166046

On Tue, Mar 29, 2016 at 08:23:42AM +1100, Andrew McGlashan wrote:
> 
> 
> On 29/03/2016 12:34 AM, Brian wrote:
> > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> > 
> >> What is the recommended way of restarting network services after, say,
> >> changing the parameters in /etc/network/interfaces?
> > 
> > Guessing game number 1: No /e/n/i before; no /e/n/i after; no indication
> > of which parameters.
> > 
> >> service networking restart doesn't seem to do the job properly.
> > 
> > Guessing game number 2: No description of what is meant by "properly".
> 
> What a ridiculous response.  IT was a simple and general question by the OP.
> 
> What is the correct answer for the poisoned systemd installation of
> Jessie these days????
> 
> Kind Regards
> AndrewM
> 

Please stop disparaging systemd to no useful effect

service networking restart

or, if you are also running network-manager, possibly

service network-manger restart

Very similar to the syntax for /etc/init.d - you're restarting a running service

Hope this helps,

AndyC

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

#166049

On Mon, 28 Mar 2016 22:01:09 +0000
"Andrew M.A. Cater" <amacater@galactic.demon.co.uk> wrote:

> On Tue, Mar 29, 2016 at 08:23:42AM +1100, Andrew McGlashan wrote:
> > 
> > 
> > On 29/03/2016 12:34 AM, Brian wrote:  
> > > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> > >   
> > >> What is the recommended way of restarting network services
> > >> after, say, changing the parameters in /etc/network/interfaces?  
> > > 
> > > Guessing game number 1: No /e/n/i before; no /e/n/i after; no
> > > indication of which parameters.
> > >   
> > >> service networking restart doesn't seem to do the job properly.  
> > > 
> > > Guessing game number 2: No description of what is meant by
> > > "properly".  
> > 
> > What a ridiculous response.  IT was a simple and general question
> > by the OP.
> > 
> > What is the correct answer for the poisoned systemd installation of
> > Jessie these days????
> > 
> > Kind Regards
> > AndrewM
> >   
> 
> Please stop disparaging systemd to no useful effect

No, this is nothing to do with systemd.

> 
> service networking restart
> 
> or, if you are also running network-manager, possibly
> 
> service network-manger restart
> 
> Very similar to the syntax for /etc/init.d - you're restarting a
> running service
> 
Google finds a couple of thousand of these:

"Running /etc/init.d/networking restart is deprecated because it may
not enable again some interfaces ... (warning)."

This message apparently originated here, though not the problem:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550240

There are suggestions that using 'stop' and 'start' does work OK. I've
never found any kind of official statement from a Debian source.

-- 
Joe

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

#166051

	Hi.

On Tue, 29 Mar 2016 08:21:12 +0100
Joe <joe@jretrading.com> wrote:
> > 
> > service networking restart
> > 
> > or, if you are also running network-manager, possibly
> > 
> > service network-manger restart
> > 
> > Very similar to the syntax for /etc/init.d - you're restarting a
> > running service
> > 
> Google finds a couple of thousand of these:
> 
> "Running /etc/init.d/networking restart is deprecated because it may
> not enable again some interfaces ... (warning)."
> 
> This message apparently originated here, though not the problem:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550240
> 
> There are suggestions that using 'stop' and 'start' does work OK. I've
> never found any kind of official statement from a Debian source.

Why such statement is needed at all? It's all in the source.

/etc/init.d/networking says that:

a) 'restart' option does:
ifdown -a --exclude=lo
ifup -a --exclude=lo
plus some arcane trickery for interfaces defined as 'allow-hotplug'

b) 'stop' option does:
ifdown -a --exclude=lo

c) 'start' option does:
recreate /run/network/ifstate, if needed
ifup -a --exclude=lo
plus some arcane trickery for interfaces defined as 'allow-hotplug'

Reco

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

#166052

Debian has the very informative and advisable package debian-reference-en (also
available for some other languages). After installation its contents becomes
available via menu as "Debian reference". Chapter 5, "Network setup" has a lot
of answers dependent on the administrator's choices (which means there is no
such thing as "the recommended way of restarting network services" ;-).

Regards,
jvp.

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

#166054

On 28/03/16 10:49, Tony van der Hoff wrote:
> What is the recommended way of restarting network services after, say,
> changing the parameters in /etc/network/interfaces?
>
> service networking restart doesn't seem to do the job properly.
>

Thanks, everybody for your very helpful replies ;)

It is quite correct that the "deprecated" message has appeared since 
long before systemd. It is also true to say that this message no longer 
appears in Jessie. However, maybe I was a little terse in my request for 
assistance. So, for the pedants:

tony@tony-lx:~$ sudo service networking restart
[sudo] password for tony:
tony@tony-lx:~$

Then, from syslog
**********************************************************************
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Withdrawing address record 
for 192.168.1.7 on eth0.
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Leaving mDNS multicast group 
on interface eth0.IPv4 with address 192.168.1.7.
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Interface eth0.IPv4 no longer 
relevant for mDNS.
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Interface eth0.IPv6 no longer 
relevant for mDNS.
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Leaving mDNS multicast group 
on interface eth0.IPv6 with address 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76.
Mar 29 10:14:59 tony-lx NetworkManager[882]: <info> (eth0): link 
disconnected
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Withdrawing address record 
for 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 on eth0.
Mar 29 10:14:59 tony-lx networking[21457]: Deconfiguring network 
interfaces...done.
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Joining mDNS multicast group 
on interface eth0.IPv4 with address 192.168.1.7.
Mar 29 10:14:59 tony-lx avahi-daemon[910]: New relevant interface 
eth0.IPv4 for mDNS.
Mar 29 10:14:59 tony-lx kernel: [233902.408076] r8169 0000:04:06.0 eth0: 
link down
Mar 29 10:14:59 tony-lx kernel: [233902.408116] r8169 0000:04:06.0 eth0: 
link down
Mar 29 10:14:59 tony-lx kernel: [233902.408538] IPv6: 
ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 29 10:14:59 tony-lx avahi-daemon[910]: Registering new address 
record for 192.168.1.7 on eth0.IPv4.
Mar 29 10:15:01 tony-lx ntpd[971]: Deleting interface #15 eth0, 
fe80::6efd:b9ff:fe00:6f76#123, interface stats: received=0, sent=0, 
dropped=0, active_time=42528 secs
Mar 29 10:15:01 tony-lx ntpd[971]: Deleting interface #14 eth0, 
2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76#123, interface stats: 
received=48, sent=48, dropped=0, active_time=42528 secs
Mar 29 10:15:01 tony-lx ntpd[971]: 2001:67c:564::12 interface 
2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 -> (none)
Mar 29 10:15:01 tony-lx ntpd[971]: peers refreshed
Mar 29 10:15:01 tony-lx NetworkManager[882]: <info> (eth0): link connected
Mar 29 10:15:01 tony-lx kernel: [233904.748562] r8169 0000:04:06.0 eth0: 
link up
Mar 29 10:15:01 tony-lx kernel: [233904.748582] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 29 10:15:03 tony-lx avahi-daemon[910]: Joining mDNS multicast group 
on interface eth0.IPv6 with address 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76.
Mar 29 10:15:03 tony-lx avahi-daemon[910]: New relevant interface 
eth0.IPv6 for mDNS.
Mar 29 10:15:03 tony-lx avahi-daemon[910]: Registering new address 
record for 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 on eth0.*.
Mar 29 10:15:05 tony-lx ntpd[971]: Listen normally on 16 eth0 
2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 UDP 123
Mar 29 10:15:05 tony-lx ntpd[971]: Listen normally on 17 eth0 
fe80::6efd:b9ff:fe00:6f76 UDP 123
Mar 29 10:15:05 tony-lx ntpd[971]: peers refreshed
Mar 29 10:15:06 tony-lx networking[21563]: Configuring network 
interfaces...RTNETLINK answers: File exists
Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1.
Mar 29 10:15:06 tony-lx networking[21563]: done.
**********************************************************************

All good up to the last 3 lines, where it appears that eth1 has not been 
brought up. In fact, that's a lie; AFAICT interface eth1 is working fine.

So, there you have the background for my cry for help.

-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

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

#166056

On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:

> Thanks, everybody for your very helpful replies ;)
> 
> It is quite correct that the "deprecated" message has appeared since long
> before systemd. It is also true to say that this message no longer appears
> in Jessie. However, maybe I was a little terse in my request for assistance.
> So, for the pedants:
> 
> tony@tony-lx:~$ sudo service networking restart
> [sudo] password for tony:
> tony@tony-lx:~$
> 
> Then, from syslog

[Snip]

> Mar 29 10:15:06 tony-lx networking[21563]: Configuring network
> interfaces...RTNETLINK answers: File exists
> Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1.
> Mar 29 10:15:06 tony-lx networking[21563]: done.
> **********************************************************************
> 
> All good up to the last 3 lines, where it appears that eth1 has not been
> brought up. In fact, that's a lie; AFAICT interface eth1 is working fine.

What happens when you comment out eth0 and eth0 in turn and retry?

Any chance of seeing /e/n/i?

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

#166058

On 29/03/16 12:58, pedantsunited wrote:
> On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
>
> Any chance of seeing /e/n/i?
>
Not until you explain what you're talking about

-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

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

#166059

On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:

> On 29/03/16 12:58, pedantsunited wrote:
> >On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
> >
> >Any chance of seeing /e/n/i?
> >
> Not until you explain what you're talking about

/etc/network/interfaces

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

#166060

On 29/03/16 14:00, Brian wrote:
> On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
>
>> On 29/03/16 12:58, pedantsunited wrote:
>>> On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
>>>
>>> Any chance of seeing /e/n/i?
>>>
>> Not until you explain what you're talking about
>
> /etc/network/interfaces
>

Ah, OK:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
auto eth0
iface eth0 inet static
	address 192.168.1.7
	netmask 255.255.255.0
	network 192.168.1.0
	broadcast 192.168.1.255
	gateway 192.168.1.1
##	up ip addr add dev eth0 2001:8b0:ff60:6a91::7
##	up ip route add default via fe80::1 dev eth0

# dns-* options are implemented by the resolvconf package, if installed
	dns-nameservers 192.168.1.1 2001:8b0:ff60:6a90:5a8b:f3ff:fede:839c
	dns-search magpieway.net

auto eth1
iface eth1 inet static
	address 192.168.2.8
	netmask 255.255.255.0
	network 192.168.2.0
	broadcast 192.168.2.255
	gateway 192.168.1.1
	up ip addr add dev eth1 2001:8b0:ff60:6a91::8
	up ip route add default via fe80::1 dev eth0

# dns-* options are implemented by the resolvconf package, if installed
	dns-nameservers 192.168.1.1
	dns-search magpieway.net



-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

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

#166061

On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
> On 29/03/16 14:00, Brian wrote:
> >On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
> >
> >>On 29/03/16 12:58, pedantsunited wrote:
> >>>On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
> >>>
> >>>Any chance of seeing /e/n/i?
> >>>
> >>Not until you explain what you're talking about
> >
> >/etc/network/interfaces
> >
> 
> Ah, OK:
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> #allow-hotplug eth0
> auto eth0
> iface eth0 inet static
> 	address 192.168.1.7
> 	netmask 255.255.255.0
> 	network 192.168.1.0
> 	broadcast 192.168.1.255
> 	gateway 192.168.1.1
> ##	up ip addr add dev eth0 2001:8b0:ff60:6a91::7
> ##	up ip route add default via fe80::1 dev eth0

You probably want to do the IPv6 part this way:

iface eth0 inet6 static
  address 2001:8b0:ff60:6a91::7
  gateway fe80::1
## but note that you need to establish reachability to fe80::1
## first.


> auto eth1
> iface eth1 inet static
> 	address 192.168.2.8
> 	netmask 255.255.255.0
> 	network 192.168.2.0
> 	broadcast 192.168.2.255
> 	gateway 192.168.1.1
> 	up ip addr add dev eth1 2001:8b0:ff60:6a91::8
> 	up ip route add default via fe80::1 dev eth0
> 
> # dns-* options are implemented by the resolvconf package, if installed
> 	dns-nameservers 192.168.1.1
> 	dns-search magpieway.net

You could consolidate your dns control statements here, or just
put them all into /etc/resolv.conf and not make them dynamic, if
that's suitable.

-dsr-

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

#166067

	Hi.

On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:

>>Mar 29 10:15:06 tony-lx networking[21563]: Configuring network
>>interfaces...RTNETLINK answers: File exists
>>Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1.
>>Mar 29 10:15:06 tony-lx networking[21563]: done.

Lines above are something to be expected, because your
/etc/network/interfaces tells the kernel to do the impossible:


> iface eth0 inet static
> 	address 192.168.1.7
> 	netmask 255.255.255.0
> 	network 192.168.1.0
> 	broadcast 192.168.1.255
> 	gateway 192.168.1.1

You have default gateway for eth0. All is good so far.


> iface eth1 inet static
> 	address 192.168.2.8
> 	netmask 255.255.255.0
> 	network 192.168.2.0
> 	broadcast 192.168.2.255
> 	gateway 192.168.1.1

And - you have yet another default gateway for eth1.
No wonder that the kernel refuses to add the same route second time.

Reco

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

#166068

On 29/03/16 15:34, Reco wrote:
> 	Hi.
>
> On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
>
>>> Mar 29 10:15:06 tony-lx networking[21563]: Configuring network
>>> interfaces...RTNETLINK answers: File exists
>>> Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1.
>>> Mar 29 10:15:06 tony-lx networking[21563]: done.
>
> Lines above are something to be expected, because your
> /etc/network/interfaces tells the kernel to do the impossible:
>
>
>> iface eth0 inet static
>> 	address 192.168.1.7
>> 	netmask 255.255.255.0
>> 	network 192.168.1.0
>> 	broadcast 192.168.1.255
>> 	gateway 192.168.1.1
>
> You have default gateway for eth0. All is good so far.
>
>
>> iface eth1 inet static
>> 	address 192.168.2.8
>> 	netmask 255.255.255.0
>> 	network 192.168.2.0
>> 	broadcast 192.168.2.255
>> 	gateway 192.168.1.1
>
> And - you have yet another default gateway for eth1.
> No wonder that the kernel refuses to add the same route second time.
>
> Reco
>

Thanks, Reco.
I've now commented out that line for eth1, but I still get

Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1.
Mar 29 15:37:47 tony-lx networking[24921]: done.


-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

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

#166069

	Hi.

On Tue, 29 Mar 2016 15:44:16 +0100
Tony van der Hoff <tony@vanderhoff.org> wrote:
> > And - you have yet another default gateway for eth1.
> > No wonder that the kernel refuses to add the same route second time.
> >
> > Reco
> >
> 
> Thanks, Reco.
> I've now commented out that line for eth1, but I still get
> 
> Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1.
> Mar 29 15:37:47 tony-lx networking[24921]: done.

Now *that* requires actual investigation.

What does the following sequence yield:

ifdown -v eth1

ifquery eth1

ip a l dev eth1

ifup -v eth1

ip a l dev eth1

Reco

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

#166070

On 29/03/16 16:25, Reco wrote:
> 	Hi.
>
> On Tue, 29 Mar 2016 15:44:16 +0100
> Tony van der Hoff <tony@vanderhoff.org> wrote:
>>> And - you have yet another default gateway for eth1.
>>> No wonder that the kernel refuses to add the same route second time.
>>>
>>> Reco
>>>
>>
>> Thanks, Reco.
>> I've now commented out that line for eth1, but I still get
>>
>> Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1.
>> Mar 29 15:37:47 tony-lx networking[24921]: done.
>
> Now *that* requires actual investigation.
>
> What does the following sequence yield:
>
> ifdown -v eth1
>
root@tony-lx:~# ifdown -v eth1
ifdown: interface eth1 not configured
root@tony-lx:~#

> ifquery eth1
>
root@tony-lx:~# ifquery eth1
address: 192.168.2.8
netmask: 255.255.255.0
network: 192.168.2.0
broadcast: 192.168.2.255
up: ip addr add dev eth1 2001:8b0:ff60:6a91::8
up: ip route add default via fe80::1 dev eth0
dns-nameservers: 192.168.1.1
dns-search: magpieway.net
root@tony-lx:~#

> ip a l dev eth1
>
root@tony-lx:~# ip a l dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000
     link/ether bc:ae:c5:29:77:d8 brd ff:ff:ff:ff:ff:ff
     inet 192.168.2.8/24 brd 192.168.2.255 scope global eth1
        valid_lft forever preferred_lft forever
     inet6 2001:8b0:ff60:6a91::8/128 scope global
        valid_lft forever preferred_lft forever
     inet6 fe80::beae:c5ff:fe29:77d8/64 scope link
        valid_lft forever preferred_lft forever
root@tony-lx:~#

> ifup -v eth1
>
root@tony-lx:~#  ifup -v eth1
Configuring interface eth1=eth1 (inet)
run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
ip addr add 192.168.2.8/255.255.255.0 broadcast 192.168.2.255     dev 
eth1 label eth1
RTNETLINK answers: File exists
Failed to bring up eth1.
root@tony-lx:~#

> ip a l dev eth1
>
root@tony-lx:~# ip a l dev eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000
     link/ether bc:ae:c5:29:77:d8 brd ff:ff:ff:ff:ff:ff
     inet 192.168.2.8/24 brd 192.168.2.255 scope global eth1
        valid_lft forever preferred_lft forever
     inet6 2001:8b0:ff60:6a91::8/128 scope global
        valid_lft forever preferred_lft forever
     inet6 fe80::beae:c5ff:fe29:77d8/64 scope link
        valid_lft forever preferred_lft forever
root@tony-lx:~#

I guess, if it never goes down, it can never come up

Cheers,
-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web