18 Nov
2019
18 Nov
'19
11:41 a.m.
Hi All,
It has come to my attention - thanks Andy - that my IP6 configuration
may be wrong. My VPS is receiving IP6 traffic, but sending none, and is
(perhaps sometimes) unable to route to an IP6 address.
This is way beyond my pay grade, so I need some help here.
When I look in my cpanel, it says my IP6 address is
2001:ba8:1f1:f00d::/64
But ip a gives ....
ian@hobsoni:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 00:16:5e:00:04:89 brd ff:ff:ff:ff:ff:ff
inet 85.119.82.210/21 brd 85.119.87.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2001:ba8:1f1:f06e::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::216:5eff:fe00:489/64 scope link
valid_lft forever preferred_lft forever
ian@hobsoni:~$ ip -6 route show
2001:ba8:1f1:f06e::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:ba8:1f1:f06e::1 dev eth0 metric 1024 pref medium
ian@hobsoni:~$ ip -6 address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2001:ba8:1f1:f06e::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::216:5eff:fe00:489/64 scope link
valid_lft forever preferred_lft forever
ian@hobsoni:~$
And here is the netplan config
ian@hobsoni:/etc/netplan$ cat 01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
eth0:
addresses:
- "85.119.82.210/21"
- "2001:ba8:1f1:f00d::2/64"
gateway4: 85.119.80.1
gateway6: "2001:ba8:1f1:f00d::1"
nameservers:
addresses: [85.119.80.232 85.119.80.233]
ian@hobsoni:/etc/netplan$
I'm guessing that f06e is not f00d for netplan and its barfing on it.
(Sorry).
But I don't know which is correct.
Regards
Ian
--
Ian Hobson
Tel (+351) 910 418 473
18 Nov
18 Nov
5:10 p.m.
Hi Ian,
On Mon, Nov 18, 2019 at 11:41:39AM +0000, Ian Hobson wrote:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
1500 qdisc mq state UP group
default qlen 1000
link/ether 00:16:5e:00:04:89 brd ff:ff:ff:ff:ff:ff
inet 85.119.82.210/21 brd 85.119.87.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2001:ba8:1f1:f06e::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::216:5eff:fe00:489/64 scope link
valid_lft forever preferred_lft forever
Unclear how or why it has been assigned an address that ends in
f06e. All other records (including on BitFolk's side) say it should
be f00d.
I take it you don't have an /etc/network/interfaces file (you
shouldn't) and haven't tried to put any network configuration into
systemd units, right? Just wondering where that address could have
come from.
And here is the netplan config
ian@hobsoni:/etc/netplan$ cat 01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
eth0:
addresses:
- "85.119.82.210/21"
- "2001:ba8:1f1:f00d::2/64"
gateway4: 85.119.80.1
gateway6: "2001:ba8:1f1:f00d::1"
nameservers:
addresses: [85.119.80.232 85.119.80.233]
This looks correct so I am puzzled why it has come up with an
address and route for f06e instead…
If you don't know where f06e has come from maybe you could do a
recursive grep of /etc to see if it is mentioned anywhere in there?
# grep -r f06e /etc
I am reluctant to suggest that you reboot, because presumably you
have done that recently (at the scheduled maintenance a couple of
weeks ago if nothing else) and this is how it came up after that.
Temporarily if you want to make this work, you could of course do:
# ip addr add 2001:ba8:1f1:f00d::2/64 dev eth0
# ip addr del 2001:ba8:1f1:f06e::2/64
# ip route change default via 2001:ba8:1f1:f00d::1
and then I'd expect it to all work, but that only stays until next
boot.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
The optimum programming team size is 1.
Has
Jurassic Park taught us nothing? — pfilandr
6:02 p.m.
On 18/11/2019 17:10, Andy Smith wrote:
[snip]
If you don't know where f06e has come from maybe
you could do a
recursive grep of /etc to see if it is mentioned anywhere in there?
# grep -r f06e /etc
As a bit of an aside, can I put in a plug here for ag, aka The Silver
Searcher.
https://github.com/ggreer/the_silver_searcher
It is startlingly fast and I'm a recent convert.
Cheers,
John
--
Xronos Scheduler - https://xronos.uk/
All your school's schedule information in one place.
Timetable, activities, homework, public events - the lot
Live demo at https://schedulerdemo.xronos.uk/
9:19 p.m.
Hi Andy,
The address was from /etc/network/interfaces, which I have renamed.
So I
sudo netplan apply
and
sudo apt purge ifupdown
and rebooted
Now I appear to have two IP6 addresses:
ian@hobsoni:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 85.119.82.210 netmask 255.255.248.0 broadcast 85.119.87.255
inet6 2001:ba8:1f1:f00d::2 prefixlen 64 scopeid 0x0<global>
inet6 fe80::216:5eff:fe00:489 prefixlen 64 scopeid 0x20<link>
ether 00:16:5e:00:04:89 txqueuelen 1000 (Ethernet)
RX packets 163 bytes 16662 (16.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 165 bytes 50514 (50.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 56 bytes 130891 (130.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 56 bytes 130891 (130.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ian@hobsoni:~$
Is that what you would expect?
Regards
Ian
On 18/11/2019 17:10, Andy Smith wrote:
Hi Ian,
On Mon, Nov 18, 2019 at 11:41:39AM +0000, Ian Hobson wrote:
--
Ian Hobson
Tel (+351) 910 418 473
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP>
mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 00:16:5e:00:04:89 brd ff:ff:ff:ff:ff:ff
inet 85.119.82.210/21 brd 85.119.87.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2001:ba8:1f1:f06e::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::216:5eff:fe00:489/64 scope link
valid_lft forever preferred_lft forever
Unclear how or why it has been assigned an address that ends in
f06e. All other records (including on BitFolk's side) say it should
be f00d.
I take it you don't have an /etc/network/interfaces file (you
shouldn't) and haven't tried to put any network configuration into
systemd units, right? Just wondering where that address could have
come from.
And here is the netplan config
ian@hobsoni:/etc/netplan$ cat 01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
eth0:
addresses:
- "85.119.82.210/21"
- "2001:ba8:1f1:f00d::2/64"
gateway4: 85.119.80.1
gateway6: "2001:ba8:1f1:f00d::1"
nameservers:
addresses: [85.119.80.232 85.119.80.233]
This looks correct so I am puzzled why it has come up with an
address and route for f06e instead…
If you don't know where f06e has come from maybe you could do a
recursive grep of /etc to see if it is mentioned anywhere in there?
# grep -r f06e /etc
I am reluctant to suggest that you reboot, because presumably you
have done that recently (at the scheduled maintenance a couple of
weeks ago if nothing else) and this is how it came up after that.
Temporarily if you want to make this work, you could of course do:
# ip addr add 2001:ba8:1f1:f00d::2/64 dev eth0
# ip addr del 2001:ba8:1f1:f06e::2/64
# ip route change default via 2001:ba8:1f1:f00d::1
and then I'd expect it to all work, but that only stays until next
boot.
Cheers,
Andy
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
9:47 p.m.
Hi Ian,
It would be best to get out of the habit of using "ifconfig" as for
quite some years now it has been unable to show all of the
information that the kernel holds. It would be better to use:
ip address show
for this purpose. It can be shortened to:
ip a
if you wish, and you can also do:
ip -6 a
to only show IPv6 addresses as opposed to also showing IPv4 and MAC
addresses.
In this case though, ifconfig has shown enough to answer your
question.
On Mon, Nov 18, 2019 at 09:19:06PM +0000, Ian Hobson wrote:
Now I appear to have two IP6 addresses:
ian@hobsoni:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 85.119.82.210 netmask 255.255.248.0 broadcast 85.119.87.255
inet6 2001:ba8:1f1:f00d::2 prefixlen 64 scopeid 0x0<global>
inet6 fe80::216:5eff:fe00:489 prefixlen 64 scopeid 0x20<link>
The "scopeid" shows that one is a global address, the other is a
link address. The "global" one is the one that you're able to use on
the Internet. Every IPv6 interface also has (should have) one or
more link-local addresses that only work on that local network.
Is that what you would expect?
Yes, this looks normal. Does IPv6 work for you now? e.g. can you
ping ipv6.google.com and other IPv6-only hosts?
I would suggest removing your /etc/network/interfaces file on Ubuntu
18.04 and beyond as it is intended to use netplan to configure
the network on that release. In past discussion on this list we've
found that support for /etc/network/interfaces seems to be either
non-existent or unreliable when netplan is in use, but here it seems
that it got some IPv6 configuration from that file.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
10:13 p.m.
Hi Andy
Thanks for the update - dragging me out of the 80's!
On 18/11/2019 21:47, Andy Smith wrote:
[snip]
Yes, this looks normal. Does IPv6 work for you now?
e.g. can you
ping ipv6.google.com and other IPv6-only hosts?
Yes that works. And so does the lets encrypt site I had trouble with.
/etc/network/interfaces removed.
Thanks for your help.
Ian
1860
days inactive
1860
days old
5 comments
3 participants
participants (3)
-
Andy Smith -
Ian Hobson -
John Winters