Re: restarting network
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 |
Reply to: