Summary: | sys-apps/systemd - Network connectivity is lost after hibernate if Ethernet adapter MAC address was changed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pavel Volkov <ao> |
Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | kernel |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pavel Volkov
2014-12-06 19:50:03 UTC
It looks to me like a kernel-space issue rather than systemd bug... Kernel team, any ideas here? Some corrections: actually the MAC address for eth0 on my machine during boot is not set by systemd-networkd, but by my custom unit. I made a mistake writing the original post because before I was changing the MAC for another interface (type veth) in .netdev file but then I found out it's not possible for physical adapter and wrote the custom unit: [Unit] Description=Set Custom MAC Address For eth0 Before=systemd-networkd.service [Service] Type=oneshot ExecStart=/bin/ip link set eth0 address 2a:5e:12:a0:bb:02 [Install] WantedBy=multi-user.target Is this still valid with kernel >= 4.0.5 and systemd-225? Yes, kernel 4.2.0 and systemd 225. I don't need this setup anymore but the problem remains. Modern test sequence: 1. Increase MAC by 1 with "ip link set address". 2. Hibernate. 3. Power on. 4. IPv4 address and routes are lost, IPv6 address and routes remain (SLAAC-configured, with custom token set on eth0 with "ip token"). 5. Ping my router with IPv6: address unreachable. 6. Restarting systemd-network does not update DHCP lease. 7. Issue the same "ip link set address" command again. 8. Ping with IPv6 works again and restarting systemd-networkd updates DHCP lease and restores routes. I would suggest you contact some kernel devs and/or some systemd devs on this; it seems nobody at Gentoo has a clue on this. |