Re: Ipv6, but no Ipv4 after reboot
On Wednesday, 9 December 2020 16:43:01 CET Andrei POPESCU wrote:
> Did something change or has it "always" been like this? What about other
> systems on the same network (if any).
I had this problem on a tower on the same network. It's now gone (or flapping...)
I currently have this is issue on a laptop through the wired lan (eno2).
Looks like the Ipv6 connection is setup by the kernel:
$ journalctl -b -g eno2
-- Journal begins at Sun 2020-08-09 16:30:57 CEST, ends at Wed 2020-12-09 18:20:06 CET. --
Dec 09 18:13:45 ylum kernel: e1000e 0000:00:1f.6 eno2: renamed from eth0
Dec 09 18:13:45 ylum kernel: e1000e 0000:00:1f.6 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Dec 09 18:13:45 ylum kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready
Dec 09 18:13:46 ylum avahi-daemon[968]: Joining mDNS multicast group on interface eno2.IPv6 with address 2a01:e0a:3d9:ddd0:c23e:baff:fe4e:7ad2.
Dec 09 18:13:46 ylum avahi-daemon[968]: New relevant interface eno2.IPv6 for mDNS.
Dec 09 18:13:46 ylum avahi-daemon[968]: Registering new address record for 2a01:e0a:3d9:ddd0:c23e:baff:fe4e:7ad2 on eno2.*.
Dec 09 18:13:46 ylum avahi-daemon[968]: Failed to parse address 'fe80::211:32ff:fe97:4c1a%eno2', ignoring.
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7753] device (eno2): carrier: link connected
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7756] manager: (eno2): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7778] device (eno2): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7787] device (eno2): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7794] device (eno2): Activation: starting connection 'eno2' (7336013e-afac-4377-972e-6a44ba571385)
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7867] device (eno2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7872] device (eno2): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7876] device (eno2): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7880] device (eno2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7898] device (eno2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7900] device (eno2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Dec 09 18:13:46 ylum NetworkManager[972]: <info> [1607534026.7909] device (eno2): Activation: successful, device activated.
For what it's worth, the whole NetworkManager log can be found there:
https://paste.debian.net/1176256/
But I could not find more relevant information.
After boot, NetworkManager lists 2 eno2 interface:
- one created at boot time with Ipv6 and no DNS (even though /etc/resolv.conf
contains the dns entries given by dhcp)
- one configured before which requires Ipv4
This configuration is detailed in the output of "nmcli c show eno2":
https://paste.debian.net/1176258/
> > Still, this is cumbersome. I've found no obvious problems in the logs.
>
> How / where did you check? What is the difference in the logs between
> reboot and disconnect / reconnect?
When reconnecting with NM, I can see that DHCP is run and both Ipv4 and v6 are
setup:
https://paste.debian.net/1176261/
> In case it helps, 'journalctl --unit NetworkManager.service' will filter
> entries (need to be root or member of 'adm' or 'systemd-journald').
See above
> Is this with DHCP or static IP? If DHCP, can you tell us more about the
> DHCP server (device, software, etc.)? It might be useful to check the
> status / logs / etc. there if you have access.
DHCP server is provided by my internet box (for French readers, that's Free's
pop box ).
I don't think there's a DHCP request sent when the eno2 interface is set by
the kernel.
> Does it still happen if you switch to a static config?
ipv4 is brought up:
$ journalctl -b -g eno2
-- Journal begins at Sun 2020-08-09 16:30:57 CEST, ends at Wed 2020-12-09 18:57:15 CET. --
Dec 09 18:51:47 ylum kernel: e1000e 0000:00:1f.6 eno2: renamed from eth0
Dec 09 18:51:47 ylum kernel: e1000e 0000:00:1f.6 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Dec 09 18:51:47 ylum kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready
Dec 09 18:51:48 ylum avahi-daemon[1232]: Joining mDNS multicast group on interface eno2.IPv6 with address 2a01:e0a:3d9:ddd0:c23e:baff:fe4e:7ad2.
Dec 09 18:51:48 ylum avahi-daemon[1232]: New relevant interface eno2.IPv6 for mDNS.
Dec 09 18:51:48 ylum avahi-daemon[1232]: Registering new address record for 2a01:e0a:3d9:ddd0:c23e:baff:fe4e:7ad2 on eno2.*.
Dec 09 18:51:48 ylum avahi-daemon[1232]: Failed to parse address 'fe80::211:32ff:fe97:4c1a%eno2', ignoring.
Dec 09 18:51:49 ylum NetworkManager[1236]: <info> [1607536309.1434] ifupdown: guessed connection type (eno2) = 802-3-ethernet
Dec 09 18:51:49 ylum NetworkManager[1236]: <info> [1607536309.1440] ifupdown: guessed connection type (eno2) = 802-3-ethernet
Dec 09 18:51:49 ylum NetworkManager[1236]: <info> [1607536309.1538] device (eno2): carrier: link connected
Dec 09 18:51:49 ylum NetworkManager[1236]: <info> [1607536309.1555] manager: (eno2): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 09 18:51:50 ylum avahi-daemon[1232]: Joining mDNS multicast group on interface eno2.IPv4 with address 192.168.1.6.
Dec 09 18:51:50 ylum avahi-daemon[1232]: New relevant interface eno2.IPv4 for mDNS.
Dec 09 18:51:50 ylum avahi-daemon[1232]: Registering new address record for 192.168.1.6 on eno2.IPv4.
All the best
Reply to: