<div dir="ltr"><div><div>Thank you for pointing this out. Unfortunately, the patch does not solve the issue.</div><div><br></div><div>The problem does not exist on the stable version of systemd(v242). I will consider the update of it.</div></div><div><br></div><div>On Tue, Jun 11, 2019 at 11:51 AM William Kennington <<a href="mailto:william@wkennington.com" target="_blank">william@wkennington.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">Probably related to this issue</div></div><div dir="auto"><div><a href="https://github.com/systemd/systemd/pull/12350" target="_blank">https://github.com/systemd/systemd/pull/12350</a></div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 11, 2019 at 02:25 Kaisrlík, Jan <<a href="mailto:jan.kaisrlik@avast.com" target="_blank">jan.kaisrlik@avast.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote">Hello here,<br> <br> I am running Yocto-thud with systemd 239 on my SoC and I've found<br> interesting, when DHCP lease was prolonged, I observe the connection<br> to the internet was completely stopped.<br> <br> Based on the logs in the system I strongly believe it is connected to<br> moment when networkd renews a dhcp lease when it expires:<br> <br> # cat /var/log/daemon.log | grep "networkd\["<br> 2019-05-29T11:55:12.159213+00:00 x systemd-networkd[250]: Enumeration completed<br> 2019-05-29T11:55:12.159253+00:00 x systemd-networkd[250]: lo: Link is not managed by us<br> 2019-05-29T11:55:12.159294+00:00 x systemd-networkd[250]: veth0: netdev ready<br> 2019-05-29T11:55:12.170082+00:00 x systemd-networkd[250]: request_name_destroy_callback n_ref=1<br> 2019-05-29T11:55:14.053408+00:00 x systemd-networkd[250]: eth0: Gained carrier<br> 2019-05-29T11:55:14.058588+00:00 x systemd-networkd[250]: veth0: Gained carrier<br> 2019-05-29T11:55:15.057317+00:00 x systemd-networkd[250]: eth0: DHCPv4 address <a href="http://192.168.0.122/24" rel="noreferrer" target="_blank">192.168.0.122/24</a> via 192.168.0.1<br> 2019-05-29T11:55:15.088632+00:00 x systemd-networkd[250]: veth0: Gained IPv6LL<br> 2019-05-29T11:55:15.088833+00:00 x systemd-networkd[250]: veth0: Configured<br> 2019-05-29T11:55:15.632514+00:00 x systemd-networkd[250]: eth0: Gained IPv6LL<br> 2019-05-29T11:55:15.632621+00:00 x systemd-networkd[250]: eth0: Configured<br> 2019-05-29T11:55:23.787104+00:00 x systemd-networkd[250]: tun0: Gained carrier<br> 2019-05-29T11:55:23.787425+00:00 x systemd-networkd[250]: tun0: Gained IPv6LL<br> 2019-06-03T08:27:42.019202+00:00 x systemd-networkd[250]: tun0: Lost carrier<br> 2019-06-03T08:28:14.017067+00:00 x systemd-networkd[250]: tun0: Gained carrier<br> 2019-06-03T08:28:14.017287+00:00 x systemd-networkd[250]: tun0: Gained IPv6LL<br> 2019-06-04T05:27:31.261841+00:00 x systemd-networkd[250]: eth0: DHCPv4 address <a href="http://192.168.0.125/24" rel="noreferrer" target="_blank">192.168.0.125/24</a> via 192.168.0.1<br> 2019-06-04T08:27:56.178984+00:00 x systemd-networkd[250]: tun0: Lost carrier<br> <br> >From the log above you can observe the lease was prolonged<br> successfully and new ip address was given and from this particular<br> moment the board was not able to connect to the internet.<br> During the debugging I found this : the routes in the system are wrong<br> and route with old ip address still exists in the system.<br> <br> # ip route<br> default via 192.168.0.1 dev eth0 proto dhcp src 192.168.0.122 metric 1024<br> default via 192.168.0.1 dev eth0 proto dhcp src 192.168.0.125 metric 1024<br> <a href="http://10.1.2.252/30" rel="noreferrer" target="_blank">10.1.2.252/30</a> dev veth0 proto kernel scope link src 10.255.254.253<br> <a href="http://192.168.0.0/24" rel="noreferrer" target="_blank">192.168.0.0/24</a> dev eth0 proto kernel scope link src 192.168.0.125<br> 192.168.0.1 dev eth0 proto dhcp scope link src 192.168.0.122 metric 1024<br> 192.168.0.1 dev eth0 proto dhcp scope link src 192.168.0.125 metric 1024<br> <br> In addition I'm adding outputs from ip tool and networkctl.<br> <br> # ip addr show eth0<br> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP<br> group default qlen 1000<br> link/ether e0:91:53:a3:9a:81 brd ff:ff:ff:ff:ff:ff<br> inet <a href="http://192.168.0.125/24" rel="noreferrer" target="_blank">192.168.0.125/24</a> brd 192.168.0.255 scope global dynamic eth0<br> valid_lft 55210sec preferred_lft 55210sec<br> inet6 fe80::e291:53ff:fea3:9a81/64 scope link<br> valid_lft forever preferred_lft forever<br> <br> # networkctl status eth0<br> ● 2: eth0<br> Link File: /lib/systemd/network/99-default.link<br> Network File: /etc/systemd/network/eth-p2p.network<br> Type: ether<br> State: routable (configured)<br> Path: platform-ff3f0000.ethernet<br> HW Address: e0:91:53:a3:9a:81 (XAVi Technologies Corp.)<br> Address: 192.168.0.125<br> fe80::e291:53ff:fea3:9a81<br> Gateway: 192.168.0.1 (Tenda Technology Co.,Ltd.Dongguan branch)<br> 192.168.0.1 (Tenda Technology Co.,Ltd.Dongguan branch)<br> DNS: 192.168.0.1<br> <br> What is even more interesting is the following output which does not<br> fully correlate with output from ip and networkctl.<br> <br> # cat /run/systemd/netif/links/2<br> # This is private data. Do not parse.<br> ADMIN_STATE=configured<br> OPER_STATE=routable<br> REQUIRED_FOR_ONLINE=yes<br> NETWORK_FILE=/etc/systemd/network/eth-p2p.network<br> DNS=192.168.0.1<br> NTP=<br> DOMAINS=<br> ROUTE_DOMAINS=<br> LLMNR=yes<br> MDNS=no<br> ADDRESSES=<a href="http://192.168.0.125/24" rel="noreferrer" target="_blank">192.168.0.125/24</a> <a href="http://192.168.0.122/24" rel="noreferrer" target="_blank">192.168.0.122/24</a><br> ROUTES=<a href="http://192.168.0.1/32/0/1024/254/18446744073709551615" rel="noreferrer" target="_blank">192.168.0.1/32/0/1024/254/18446744073709551615</a><br> <a href="http://0.0.0.0/0/0/1024/254/18446744073709551615" rel="noreferrer" target="_blank">0.0.0.0/0/0/1024/254/18446744073709551615</a><br> DHCP4_ADDRESS=192.168.0.125<br> DHCP_LEASE=/run/systemd/netif/leases/2<br> <br> Unfortunately, pcaps and more verbose systemd logs are not currently available.<br> <br> Have you ever seen similar issue?<br> <br> Thank you in you advice.<br> <br> Best regards,</div></div><div dir="ltr"><div class="gmail_quote"><br> -- <br> Jan Kaisrlik</div><div dir="ltr" class="m_-107484526400474760gmail-m_-3681861144792352843m_957850948233925547gmail_signature"></div></div> _______________________________________________<br> systemd-devel mailing list<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a></blockquote></div></div></blockquote></div><div dir="ltr" class="m_-107484526400474760gmail_signature"></div></div>