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:
>> 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@???
> https://lists.bitfolk.com/mailman/listinfo/users
>
--
Ian Hobson
Tel (+351) 910 418 473
