Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #166020 > unrolled thread
| Started by | Tony van der Hoff <tony@vanderhoff.org> |
|---|---|
| First post | 2016-03-28 11:50 +0200 |
| Last post | 2016-03-29 13:20 +0200 |
| Articles | 9 on this page of 29 — 12 participants |
Back to article view | Back to linux.debian.user
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 2 of 2 — ← Prev page 1 [2]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2016-03-29 18:30 +0200 |
| Message-ID | <ri4GL-pQ-37@gated-at.bofh.it> |
| In reply to | #166070 |
On Tue, 29 Mar 2016 17:08:01 +0100 Tony van der Hoff <tony@vanderhoff.org> wrote: > 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 Ok, let's try it like this then: ifdown --force eth1 ip l s dev eth1 down ip a d dev eth1 192.168.2.8/24 ip a d dev eth1 2001:8b0:ff60:6a91::8 ifup -v eth1 > > 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 First, if you're configuring eth1, what's the point of setting the route via eth0. Second, if you're configuring ipv6 route, you should use 'ip -6' instead of straight 'ip'. And third, using default link-local ipv6 address as a gateway is kind of weird. Although if ipv6 /128 address mask works for you - who am I to argue. > 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. This seems to be the current source of trouble. I wonder what
[toc] | [prev] | [next] | [standalone]
| From | Tony van der Hoff <tony@vanderhoff.org> |
|---|---|
| Date | 2016-03-29 18:40 +0200 |
| Message-ID | <ri4Qr-sQ-19@gated-at.bofh.it> |
| In reply to | #166071 |
On 29/03/16 17:20, Reco wrote: > On Tue, 29 Mar 2016 17:08:01 +0100 > Tony van der Hoff <tony@vanderhoff.org> wrote: > >> 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 > > Ok, let's try it like this then: > > ifdown --force eth1 > ip l s dev eth1 down > ip a d dev eth1 192.168.2.8/24 > ip a d dev eth1 2001:8b0:ff60:6a91::8 > ifup -v eth1 > root@tony-lx:~# ifdown --force eth1 root@tony-lx:~# ip l s dev eth1 down root@tony-lx:~# ip a d dev eth1 192.168.2.8/24 RTNETLINK answers: Cannot assign requested address root@tony-lx:~# ip a d dev eth1 2001:8b0:ff60:6a91::8 RTNETLINK answers: Cannot assign requested address 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 ip link set dev eth1 up ip addr add dev eth1 2001:8b0:ff60:6a91::8 ip route add default via fe80::1 dev eth0 RTNETLINK answers: File exists Failed to bring up eth1. root@tony-lx:~# > > First, if you're configuring eth1, what's the point of setting the > route via eth0. > Second, if you're configuring ipv6 route, you should use 'ip -6' > instead of straight 'ip'. > And third, using default link-local ipv6 address as a gateway is kind > of weird. Although if ipv6 /128 address mask works for you - who am I > to argue. > Hah, well, I don't really understand the detail. I got itfrom various howtos and wikis, which I can't now identify. I just kept following instructions - a bit like following yours - until it seemed to work. I have hosts on eth1, which need access to the world through the router, which is on eth0. It didn't seem unreasonable to set up a route via eth0 to do this. It's been running satisfactorily for years like this. It's only recently that I've been able to dedicate the time to chase up this potential problem. > >> 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. > > This seems to be the current source of trouble. I wonder what > what indeed? cheers, -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England |
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Date | 2016-03-29 19:20 +0200 |
| Message-ID | <ri5t8-Xc-1@gated-at.bofh.it> |
| In reply to | #166072 |
On Tue, 29 Mar 2016 17:38:07 +0100 Tony van der Hoff <tony@vanderhoff.org> wrote: > On 29/03/16 17:20, Reco wrote: > > On Tue, 29 Mar 2016 17:08:01 +0100 > > Tony van der Hoff <tony@vanderhoff.org> wrote: > > > >> 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 > > > > Ok, let's try it like this then: > > > > ifdown --force eth1 > > ip l s dev eth1 down > > ip a d dev eth1 192.168.2.8/24 > > ip a d dev eth1 2001:8b0:ff60:6a91::8 > > ifup -v eth1 > > > > root@tony-lx:~# ifdown --force eth1 > root@tony-lx:~# ip l s dev eth1 down > root@tony-lx:~# ip a d dev eth1 192.168.2.8/24 > RTNETLINK answers: Cannot assign requested address > root@tony-lx:~# ip a d dev eth1 2001:8b0:ff60:6a91::8 > RTNETLINK answers: Cannot assign requested address > 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 > ip link set dev eth1 up > > ip addr add dev eth1 2001:8b0:ff60:6a91::8 > ip route add default via fe80::1 dev eth0 > RTNETLINK answers: File exists > Failed to bring up eth1. Haha, bullseye! The whole mess is caused by exotic 'ip route' "up" hook. So, first things first: ifdown --force eth1 ip l s dev eth1 down ip a d dev eth1 192.168.2.8/24 ip a d dev eth1 2001:8b0:ff60:6a91::8 And then modify your /etc/network/interfaces like this: 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 up /sbin/ip addr add dev eth1 2001:8b0:ff60:6a91::8/128 up /sbin/ip -6 route add default via fe80::1 dev eth1 'ifup -v eth1' should configure the interface cleanly then. As should conventional 'ifup eth1'. Next, ifup (and ifdown for that matter) is kind of paranoid. Every time you tell ifup to do something - it executes each and every 'pre-up' and 'up' in succession and all it takes is one faulty hook to get (in)famous 'Failed to bring up foo' message. The interface in question may be in UP state, and even have some IPs assigned, *but* since something went wrong - the interface must be absent from /run/network/ifstate. ifdown should only proceed if the interface is listed in the ifstate file (unless you supply --force of course). PS To answer your original query. '/sbin/service networking restart' is a valid way of changing network interface configuration *if* the network interface is configured correctly *before* and *after* the change. Else it's more-or-less required to do things a hard way - by manual reconfiguration via iproute (or ifconfig). Reco
[toc] | [prev] | [next] | [standalone]
| From | Tony van der Hoff <tony@vanderhoff.org> |
|---|---|
| Date | 2016-03-30 14:20 +0200 |
| Message-ID | <ringm-5c9-7@gated-at.bofh.it> |
| In reply to | #166074 |
On 29/03/16 18:13, Reco wrote: > On Tue, 29 Mar 2016 17:38:07 +0100 > Tony van der Hoff <tony@vanderhoff.org> wrote: > >> On 29/03/16 17:20, Reco wrote: >>> On Tue, 29 Mar 2016 17:08:01 +0100 >>> Tony van der Hoff <tony@vanderhoff.org> wrote: >>> >>>> 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 >>> >>> Ok, let's try it like this then: >>> >>> ifdown --force eth1 >>> ip l s dev eth1 down >>> ip a d dev eth1 192.168.2.8/24 >>> ip a d dev eth1 2001:8b0:ff60:6a91::8 >>> ifup -v eth1 >>> >> >> root@tony-lx:~# ifdown --force eth1 >> root@tony-lx:~# ip l s dev eth1 down >> root@tony-lx:~# ip a d dev eth1 192.168.2.8/24 >> RTNETLINK answers: Cannot assign requested address >> root@tony-lx:~# ip a d dev eth1 2001:8b0:ff60:6a91::8 >> RTNETLINK answers: Cannot assign requested address >> 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 >> ip link set dev eth1 up >> >> ip addr add dev eth1 2001:8b0:ff60:6a91::8 >> ip route add default via fe80::1 dev eth0 >> RTNETLINK answers: File exists >> Failed to bring up eth1. > > Haha, bullseye! The whole mess is caused by exotic 'ip route' "up" hook. > So, first things first: > > ifdown --force eth1 > ip l s dev eth1 down > ip a d dev eth1 192.168.2.8/24 > ip a d dev eth1 2001:8b0:ff60:6a91::8 > > And then modify your /etc/network/interfaces like this: > > 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 > up /sbin/ip addr add dev eth1 2001:8b0:ff60:6a91::8/128 > up /sbin/ip -6 route add default via fe80::1 dev eth1 > > 'ifup -v eth1' should configure the interface cleanly then. > As should conventional 'ifup eth1'. > > > Next, ifup (and ifdown for that matter) is kind of paranoid. > Every time you tell ifup to do something - it executes each and every > 'pre-up' and 'up' in succession and all it takes is one faulty hook to > get (in)famous 'Failed to bring up foo' message. > The interface in question may be in UP state, and even have some IPs > assigned, *but* since something went wrong - the interface must be > absent from /run/network/ifstate. > ifdown should only proceed if the interface is listed in the ifstate > file (unless you supply --force of course). > > > PS To answer your original query. > '/sbin/service networking restart' is a valid way of changing network > interface configuration *if* the network interface is configured > correctly *before* and *after* the change. > > Else it's more-or-less required to do things a hard way - by manual > reconfiguration via iproute (or ifconfig). > > Reco > Well, sadly that was an unmitigated failure, probably due to my cack-handedness. I followed your instructions, and double-checked them, and found I lost *all* networking. I restored .../interfaces settings as they were, but failed to restart networking, and had to reboot. Obviously, Something must have gone wrong. I then got tied up with pressing stuff. I'll try again later. Cheers, -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England |
[toc] | [prev] | [next] | [standalone]
| From | Nemeth Gyorgy <friczy@freemail.hu> |
|---|---|
| Date | 2016-03-29 18:50 +0200 |
| Message-ID | <ri506-wp-15@gated-at.bofh.it> |
| In reply to | #166070 |
2016-03-29 18:08 keltezéssel, Tony van der Hoff írta: > I guess, if it never goes down, it can never come up If you modified your /etc/network interfaces when the network was up and running then you can face similar messages. If you want to modify your network settings then the proper order is - stop your network (either via /etc/init.d/networking or systemctl) - modify your interfaces file - start your network. Now if you don't want to reboot try ifconfig eth1 down first then ifdown eth1 then ifup eth1 again. If you are lucky (and I remember well :) this will solve your problem. -- --- Friczy --- 'Death is not a bug, it's a feature'
[toc] | [prev] | [next] | [standalone]
| From | Darac Marjal <mailinglist@darac.org.uk> |
|---|---|
| Date | 2016-03-30 18:40 +0200 |
| Message-ID | <rirk0-87s-45@gated-at.bofh.it> |
| In reply to | #166060 |
[Multipart message — attachments visible in raw view] — view raw
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 > ># 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 The RTNETLINK message is probably related to these lines. You've told ifupdown that, when eth1 comes up, an address and route should be added. However, you've not told it to remove those when the interface is taken down. So, when you restart networking, the 'up' lines are run again and there is a conflict. Try adding: pre-down ip addr del dev eth0 2001:8db:ff60:6a91::8/<something> pre-down ip route del default > ># 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 | > -- For more information, please reread.
[toc] | [prev] | [next] | [standalone]
| From | Tony van der Hoff <tony@vanderhoff.org> |
|---|---|
| Date | 2016-04-04 16:20 +0200 |
| Subject | Re: restarting network [SOLVED] |
| Message-ID | <rkdwd-4bf-5@gated-at.bofh.it> |
| In reply to | #166107 |
On 29/03/16 15:42, Darac Marjal wrote: > 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? My thanks to everyone who helped resolve this question, especially Reco and Darjac, who set me on the right path to the solution. It turned out that indeed having two default routes was a killer, but having sorted that, restarting the networking service was upsetting openvpn, which somehow consumed 100% of my network capability, and gave every impression of the network being dead. Disabling openvpn sorted that. As I don't normally use openvpn, I can easily start it on occasions when I need it. I'll get back to sorting out what it's doing wrong when I've got more time. Thanks again, chaps! -- Tony van der Hoff | mailto:tony@vanderhoff.org Buckinghamshire, England |
[toc] | [prev] | [next] | [standalone]
| From | Bonno Bloksma <b.bloksma@tio.nl> |
|---|---|
| Date | 2016-04-05 13:30 +0200 |
| Subject | RE: restarting network [SOLVED] |
| Message-ID | <rkxlf-2sv-7@gated-at.bofh.it> |
| In reply to | #166359 |
Hi Tony, >>>>> Any chance of seeing /e/n/i? > > My thanks to everyone who helped resolve this question, especially Reco and Darjac, who set me on the right path to the solution. > > It turned out that indeed having two default routes was a killer, but having sorted that, restarting the networking service was upsetting openvpn, which somehow consumed 100% of my network capability, and gave every impression of the network being dead. > > Disabling openvpn sorted that. As I don't normally use openvpn, I can easily start it on occasions when I need it. I'll get back to sorting out what it's doing wrong when I've got more time. > Like I wrote before, some services do not like it when network part they rely on disappears for a (short) while when the network restarts. In my case Quagga was one of them, it seems OpenVPN is another one. Unless you really want to debug why, Just create a script that does a service network restart first and then a service openvpn restart Bonno Bloksma
[toc] | [prev] | [next] | [standalone]
| From | Bonno Bloksma <b.bloksma@tio.nl> |
|---|---|
| Date | 2016-03-29 13:20 +0200 |
| Message-ID | <rhZQK-5mP-17@gated-at.bofh.it> |
| In reply to | #166020 |
Hi Tony, > 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. Although that is the "proper way" I have noticed that other services depending on specific network settings may need to be restarted as well. I have had to restart quagga mostly too after a network restart. I have made sure to connect to the system via ssh via a non routed ip address in order to make sure I can reconnect afterwards. Another thing is special routing lines you added that depend on an ip-address being reachable. Other services / settings may need to be restarted as well. Bonno Bloksma
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web