9 Nov
2018
9 Nov
'18
2:40 p.m.
Following an upgrade to Ubuntu 18.04, my network is not coming up
properly. The interface seems to come up, but traffic is not being
routed properly.
Andy checked and he can ping my VPS some within Bitfolk, but from the
machine I cannot see the outside world, nor can I see the machine from
the outside world.
/etc/network/interfaces is as below. Does anybody have any ideas as to
what is wrong?
#### BEGIN
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
iface eth0 inet6 static
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway fe80::fcff:ffff:feff:ffff
pre-up echo "/sbin/modprobe ipv6" &&
/sbin/modprobe ipv6 || true
post-up echo "/proc/sys/net/ipv6/conf/default/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/all/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/default/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/all/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/default/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/all/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/autoconf || true
#### END
9 Nov
9 Nov
3:08 p.m.
Hi Henry,
On Fri, Nov 09, 2018 at 02:40:05PM +0000, Henry Gomersall wrote:
Andy checked and he can ping my VPS some within
Bitfolk, but from the
machine I cannot see the outside world, nor can I see the machine from
the outside world.
Because it seems possible to ping it from within 85.119.80.0/21, I
think this means it does not have a default route. You can confirm
this by typing:
$ ip route
Do you see a "default via …" line?
If not, do:
$ sudo ip route add default via 85.119.80.1
Does that cause it to work?
/etc/network/interfaces is as below. Does anybody have
any ideas as to
what is wrong?
#### BEGIN
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
This looks okay.
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
The above should be removed as it is a legacy IP address that won't
work any more. It shouldn't be causing any problems but is best
gone.
iface eth0 inet6 static
auto lo
iface lo inet loopback
It's weird that you have another "auto lo" and "iface lo…" here.
Is
it a cut and paste error?
>
> auto eth0
> iface eth0 inet static
> address 85.119.83.128
> netmask 255.255.248.0
> gateway 85.119.80.1
>
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
Assuming the above is cut and paste error…
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway fe80::fcff:ffff:feff:ffff
pre-up echo "/sbin/modprobe ipv6" &&
/sbin/modprobe ipv6 || true
post-up echo "/proc/sys/net/ipv6/conf/default/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/all/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/default/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/all/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/default/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/all/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/autoconf || true
#### END
Try simplifying the above to:
iface eth0 inet6 static
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway 2001:ba8:1f1:f1e5::1
So, whole file should be:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
iface eth0 inet6 static
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway 2001:ba8:1f1:f1e5::1
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
3:13 p.m.
On 09/11/2018 15:08, Andy Smith wrote:
So, whole file should be:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
iface eth0 inet6 static
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway 2001:ba8:1f1:f1e5::1
It was a copy and paste error, so I've changed as suggested.
Thanks,
henry
3:12 p.m.
Hello Henry.
I was caught out by this with a home server running 18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
You'll need to create a .yaml file called "/etc/netplan/config.yaml" and
then run `sudo netplan apply` to set up the networking according to it.
See https://netplan.io/examples for examples.
Thanks
Gavin
On 09/11/2018 14:40, Henry Gomersall wrote:
Following an upgrade to Ubuntu 18.04, my network is
not coming up
properly. The interface seems to come up, but traffic is not being
routed properly.
Andy checked and he can ping my VPS some within Bitfolk, but from the
machine I cannot see the outside world, nor can I see the machine from
the outside world.
/etc/network/interfaces is as below. Does anybody have any ideas as to
what is wrong?
#### BEGIN
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
iface eth0 inet6 static
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 85.119.83.128
netmask 255.255.248.0
gateway 85.119.80.1
auto eth0:1
iface eth0:1 inet static
address 212.13.195.128
netmask 255.255.255.255
address 2001:ba8:1f1:f1e5::2
netmask 64
gateway fe80::fcff:ffff:feff:ffff
pre-up echo "/sbin/modprobe ipv6" &&
/sbin/modprobe ipv6 || true
post-up echo "/proc/sys/net/ipv6/conf/default/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/all/forwarding=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/forwarding || true
post-up echo "/proc/sys/net/ipv6/conf/default/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/all/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/accept_ra=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra || true
post-up echo "/proc/sys/net/ipv6/conf/default/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/default/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/all/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/all/autoconf || true
post-up echo "/proc/sys/net/ipv6/conf/$IFACE/autoconf=0" &&
echo 0 > /proc/sys/net/ipv6/conf/$IFACE/autoconf || true
#### END
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
3:14 p.m.
On 9/11/2018 17:12, Gavin Westwood wrote:
Hello Henry.
I was caught out by this with a home server running 18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
*SHAKES FIST IN ANGER*
3:15 p.m.
On 09/11/2018 15:12, Gavin Westwood wrote:
I was caught out by this with a home server running
18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
You'll need to create a .yaml file called "/etc/netplan/config.yaml" and
then run `sudo netplan apply` to set up the networking according to it.
See https://netplan.io/examples for examples.
How does that interact with /etc/networking/interfaces?
Cheers,
henry
3:16 p.m.
Hi,
On Fri, Nov 09, 2018 at 03:12:53PM +0000, Gavin Westwood wrote:
I was caught out by this with a home server running
18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
Doesn't ifupdown still work for interfaces listed in
/etc/network/interfaces?
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
3:23 p.m.
On 09/11/2018 15:16, Andy Smith wrote:
On Fri, Nov 09, 2018 at 03:12:53PM +0000, Gavin
Westwood wrote:
Hmmm, I'm not sure. Admittedly I was going for a less common use-case
of a bridge between VMs and the actual home network using a fixed IP.
Going back to Henry's issue, I'd say ignore netplan for now and move
interfaces to interfaces.bak and create a new interfaces file with the
entries that Andy specified, as I'm beginning to wonder if all the
gateway entries (and the mixing of ipv4 and ipv6 in one entry) might be
getting the networking in a muddle...
Gavin
I was caught out by this with a home server
running 18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
Doesn't ifupdown still work for
interfaces listed in
/etc/network/interfaces?
3:27 p.m.
Hello,
On Fri, Nov 09, 2018 at 03:23:52PM +0000, Gavin Westwood wrote:
On 09/11/2018 15:16, Andy Smith wrote:
If this doesn't work, it should be reported as a bug to Ubuntu:
https://netplan.io/faq#how-to-go-back-to-ifupdown
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
On Fri, Nov 09, 2018 at 03:12:53PM +0000, Gavin
Westwood wrote:
Hmmm, I'm not sure. Admittedly I was going for a less common use-case
of a bridge between VMs and the actual home network using a fixed IP. I was caught out by this with a home server
running 18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
Doesn't ifupdown still work for
interfaces listed in
/etc/network/interfaces?
3:37 p.m.
On 09/11/2018 15:23, Gavin Westwood wrote:
On 09/11/2018 15:16, Andy Smith wrote:
With Andy's suggested interfaces, it comes back up as expected after a
reboot. I still don't appear to have IPv6 though, which is puzzling (I
only have fe80 addresses, which I understand to be link-local, but then
I know next to nothing about IPv6).
Henry
On Fri, Nov 09, 2018 at 03:12:53PM +0000, Gavin
Westwood wrote:
Hmmm, I'm not sure. Admittedly I was going for a
less common use-case
of a bridge between VMs and the actual home network using a fixed IP.
Going back to Henry's issue, I'd say ignore netplan for now and move
interfaces to interfaces.bak and create a new interfaces file with the
entries that Andy specified, as I'm beginning to wonder if all the
gateway entries (and the mixing of ipv4 and ipv6 in one entry) might be
getting the networking in a muddle... I was caught out by this with a home server
running 18.04. The way you
configure networking has changed from that version to use a system
called Netplan (https://netplan.io).
Doesn't ifupdown still work for
interfaces listed in
/etc/network/interfaces?
3:59 p.m.
Hello,
On Fri, Nov 09, 2018 at 03:37:14PM +0000, Henry Gomersall wrote:
With Andy's suggested interfaces, it comes back up
as expected after a
reboot. I still don't appear to have IPv6 though, which is puzzling (I
only have fe80 addresses, which I understand to be link-local, but then
I know next to nothing about IPv6).
Weird. What does:
$ ip -6 a
$ ip -6 ro
Say?
If you add the IPv6 addresses manually:
# ip a add 2001:ba8:1f1:f1e5::2/64 dev eth0
# ip ro add default via 2001:ba8:1f1:f1e5::1/64
Does it work then?
"ping6 ipv6.google.com" for example to test.
Also the output of:
$ grep -r . /proc/sys/net/ipv6
Could be useful. It will be quite big.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
6:08 p.m.
Ok, so now I have no internet at all, and properly none, with no eth0
come up, though the services appears to have started.
That is odd, because I didn't apparently change anything.
wtf is going on!?
Henry
On 09/11/2018 15:59, Andy Smith wrote:
Hello,
On Fri, Nov 09, 2018 at 03:37:14PM +0000, Henry Gomersall wrote:
With Andy's suggested interfaces, it comes
back up as expected after a
reboot. I still don't appear to have IPv6 though, which is puzzling (I
only have fe80 addresses, which I understand to be link-local, but then
I know next to nothing about IPv6).
Weird. What does:
$ ip -6 a
$ ip -6 ro
Say?
If you add the IPv6 addresses manually:
# ip a add 2001:ba8:1f1:f1e5::2/64 dev eth0
# ip ro add default via 2001:ba8:1f1:f1e5::1/64
Does it work then?
"ping6 ipv6.google.com" for example to test.
Also the output of:
$ grep -r . /proc/sys/net/ipv6
Could be useful. It will be quite big.
Cheers,
Andy
6:25 p.m.
Hi henry,
I've not experienced this I'm afraid. You say "the service appears
to have started" - which service is this?
You could check if netplan and/or networkmanager are installed and
uninstall them if so - perhaps they are causing some confusion.
Or you could backup and delete /etc/network/interfaces file and go
fully netplan. I've no knowledge of that, but maybe that is the path
of least resistance.
Cheers,
Andy
On Fri, Nov 09, 2018 at 06:08:32PM +0000, Henry Gomersall wrote:
Ok, so now I have no internet at all, and properly
none, with no eth0
come up, though the services appears to have started.
That is odd, because I didn't apparently change anything.
wtf is going on!?
Henry
2234
days inactive
2234
days old
12 comments
5 participants
participants (5)
-
Andy Smith -
G. Miliotis -
Gavin Westwood -
Henry Gomersall -
Henry Gomersall