{"action":"created","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/5625","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/5625/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/5625/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/5625/events","html_url":"https://github.com/systemd/systemd/issues/5625","id":216276618,"number":5625,"title":"systemd-networkd won't renew DHCPv4 address after NDisc error","user":{"login":"Malvineous","id":171656,"avatar_url":"https://avatars0.githubusercontent.com/u/171656?v=3","gravatar_id":"","url":"https://api.github.com/users/Malvineous","html_url":"https://github.com/Malvineous","followers_url":"https://api.github.com/users/Malvineous/followers","following_url":"https://api.github.com/users/Malvineous/following{/other_user}","gists_url":"https://api.github.com/users/Malvineous/gists{/gist_id}","starred_url":"https://api.github.com/users/Malvineous/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Malvineous/subscriptions","organizations_url":"https://api.github.com/users/Malvineous/orgs","repos_url":"https://api.github.com/users/Malvineous/repos","events_url":"https://api.github.com/users/Malvineous/events{/privacy}","received_events_url":"https://api.github.com/users/Malvineous/received_events","type":"User","site_admin":false},"labels":[{"id":191919606,"url":"https://api.github.com/repos/systemd/systemd/labels/bug","name":"bug","color":"e11d21","default":true},{"id":253688058,"url":"https://api.github.com/repos/systemd/systemd/labels/dhcp","name":"dhcp","color":"bfd4f2","default":false},{"id":219549709,"url":"https://api.github.com/repos/systemd/systemd/labels/network","name":"network","color":"fad8c7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2017-03-23T03:07:05Z","updated_at":"2017-04-05T00:25:21Z","closed_at":null,"body":"### Submission type\r\n\r\n  - [X] Bug report\r\n  - [ ] Request for enhancement (RFE)\r\n\r\n### systemd version the issue has been seen with\r\n\r\nsystemd 232\r\n\r\n### Used distribution\r\n\r\nArch Linux ARM\r\n\r\n### In case of bug report: Expected behaviour you didn't see\r\n\r\nWhen DHCPv4 lease expires, the address should be renewed from the DHCP server.\r\n\r\n### In case of bug report: Unexpected behaviour you saw\r\n\r\nWhen DHCPv4 lease expired, the address was not renewed and the machine lost IPv4 connectivity.  IPv6 connectivity remained.\r\n\r\n### In case of bug report: Steps to reproduce the problem\r\n\r\nI am not sure how to reproduce the problem as I do not know what is causing the error message.\r\n\r\nI see this in my logs when starting `systemd-networkd`:\r\n\r\n```\r\nsystemd-networkd[245]: Enumeration completed\r\nsystemd-networkd[245]: eth0: IPv6 enabled for interface: Success\r\nsystemd-networkd[245]: eth0: Gained carrier\r\nsystemd-networkd[245]: eth0: Lost carrier\r\nsystemd-networkd[245]: eth0: Gained IPv6LL\r\nsystemd-networkd[245]: eth0: Gained carrier\r\nsystemd-networkd[245]: eth0: DHCPv4 address 192.168.0.25/24 via 192.168.0.10\r\nsystemd-networkd[245]: eth0: Could not set NDisc route or address: Invalid argument\r\nsystemd-networkd[245]: eth0: Failed\r\n```\r\nThen 24 hours later (the length of the IPv4 lease) the IPv4 address is removed again with nothing written to the logs.  This has happened on three different machines.\r\n\r\n`systemctl status systemd-networkd` shows it as active and running.\r\n\r\nRestarting `systemd-networkd` restores the IPv4 address, and displays the following log messages:\r\n```\r\nsystemd-networkd[750]: eth0: Gained IPv6LL\r\nsystemd-networkd[750]: Enumeration completed\r\nsystemd-networkd[750]: eth0: DHCPv4 address 192.168.0.25/24 via 192.168.0.10\r\nsystemd-networkd[750]: eth0: Could not set NDisc route or address: Invalid argument\r\nsystemd-networkd[750]: eth0: Failed\r\n```\r\nI presume in another 24 hours the IPv4 address will drop out again.\r\n\r\nI am not sure what it causing the `NDisc` error message.  I have IPv6 enabled on this network so it may be related to that, however any IPv6 errors should not prevent IPv4 addresses from being renewed.\r\n\r\nPlease advise if there are further troubleshooting steps I can take to help narrow down the problem.\r\n\r\nHere is the content of my `/etc/systemd/network/default.network` file, the only one I have in that directory:\r\n```\r\n[Match]\r\nName=eth*\r\n\r\n[Network]\r\nDHCP=v4\r\n\r\nAddress=fdaa::ba27:ebff:fe48:1c6b\r\n\r\n[DHCPv4]\r\nUseHostname=false\r\n```"},"comment":{"url":"https://api.github.com/repos/systemd/systemd/issues/comments/291689171","html_url":"https://github.com/systemd/systemd/issues/5625#issuecomment-291689171","issue_url":"https://api.github.com/repos/systemd/systemd/issues/5625","id":291689171,"user":{"login":"Malvineous","id":171656,"avatar_url":"https://avatars0.githubusercontent.com/u/171656?v=3","gravatar_id":"","url":"https://api.github.com/users/Malvineous","html_url":"https://github.com/Malvineous","followers_url":"https://api.github.com/users/Malvineous/followers","following_url":"https://api.github.com/users/Malvineous/following{/other_user}","gists_url":"https://api.github.com/users/Malvineous/gists{/gist_id}","starred_url":"https://api.github.com/users/Malvineous/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Malvineous/subscriptions","organizations_url":"https://api.github.com/users/Malvineous/orgs","repos_url":"https://api.github.com/users/Malvineous/repos","events_url":"https://api.github.com/users/Malvineous/events{/privacy}","received_events_url":"https://api.github.com/users/Malvineous/received_events","type":"User","site_admin":false},"created_at":"2017-04-05T00:25:21Z","updated_at":"2017-04-05T00:25:21Z","body":"Thanks for the link - `armv6h` unfortunately though (Raspberry Pi).  Is there any way to figure out what command is being run (assuming it's a command being executed) when the `Invalid argument` response is generated?  If I can fiddle with parameters maybe I can work out what the problem is.  Although I guess the real issue is that this IPv6 error shouldn't break IPv4.\r\n\r\nThis is what `radvdump` says when restarting `systemd-networkd`:\r\n```\r\n#\r\n# radvd configuration generated by radvdump 2.16\r\n# based on Router Advertisement from fe80::6666:b3ff:feb0:9a60\r\n# received by interface eth0\r\n#\r\n\r\ninterface eth0\r\n{\r\n\tAdvSendAdvert on;\r\n\t# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump\r\n\tAdvManagedFlag on;\r\n\tAdvOtherConfigFlag on;\r\n\tAdvReachableTime 0;\r\n\tAdvRetransTimer 0;\r\n\tAdvCurHopLimit 64;\r\n\tAdvDefaultLifetime 65535;\r\n\tAdvHomeAgentFlag off;\r\n\tAdvDefaultPreference medium;\r\n\tAdvSourceLLAddress on;\r\n\tAdvLinkMTU 1280;\r\n\tAdvIntervalOpt on;\r\n\r\n\tprefix 2001:4479:cbce:f309::/64\r\n\t{\r\n\t\tAdvValidLifetime infinity; # (0xffffffff)\r\n\t\tAdvPreferredLifetime infinity; # (0xffffffff)\r\n\t\tAdvOnLink on;\r\n\t\tAdvAutonomous on;\r\n\t\tAdvRouterAddr off;\r\n\t}; # End of prefix definition\r\n\r\n\r\n\tprefix fdaa:f00b::/64\r\n\t{\r\n\t\tAdvValidLifetime infinity; # (0xffffffff)\r\n\t\tAdvPreferredLifetime infinity; # (0xffffffff)\r\n\t\tAdvOnLink on;\r\n\t\tAdvAutonomous on;\r\n\t\tAdvRouterAddr off;\r\n\t}; # End of prefix definition\r\n\r\n\r\n\tprefix fdaa::/64\r\n\t{\r\n\t\tAdvValidLifetime infinity; # (0xffffffff)\r\n\t\tAdvPreferredLifetime infinity; # (0xffffffff)\r\n\t\tAdvOnLink on;\r\n\t\tAdvAutonomous on;\r\n\t\tAdvRouterAddr off;\r\n\t}; # End of prefix definition\r\n\r\n\r\n\tRDNSS fdaa::baae:edff:fe72:7d5f fdaa::7e05:7ff:fe0f:dcaa\r\n\t{\r\n\t\tAdvRDNSSLifetime 18000;\r\n\t}; # End of RDNSS definition\r\n\r\n\r\n\tDNSSL my.domain.here\r\n\t{\r\n\t\tAdvDNSSLLifetime 18000;\r\n\t}; # End of DNSSL definition\r\n\r\n}; # End of interface definition\r\n```"}}
{"actor":{"display_login":"Malvineous"}}