{"action":"closed","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/64","labels_url":"https://api.github.com/repos/systemd/systemd/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/64/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/64/events","html_url":"https://github.com/systemd/systemd/issues/64","id":84739102,"number":64,"title":"DHCP license renewal causes disconnect","user":{"login":"nicolasbock","id":841385,"avatar_url":"https://avatars.githubusercontent.com/u/841385?v=3","gravatar_id":"","url":"https://api.github.com/users/nicolasbock","html_url":"https://github.com/nicolasbock","followers_url":"https://api.github.com/users/nicolasbock/followers","following_url":"https://api.github.com/users/nicolasbock/following{/other_user}","gists_url":"https://api.github.com/users/nicolasbock/gists{/gist_id}","starred_url":"https://api.github.com/users/nicolasbock/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nicolasbock/subscriptions","organizations_url":"https://api.github.com/users/nicolasbock/orgs","repos_url":"https://api.github.com/users/nicolasbock/repos","events_url":"https://api.github.com/users/nicolasbock/events{/privacy}","received_events_url":"https://api.github.com/users/nicolasbock/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/systemd/systemd/labels/networkd","name":"networkd","color":"fad8c7"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-03T19:40:15Z","updated_at":"2015-06-04T11:56:26Z","closed_at":"2015-06-04T11:56:26Z","body":"Disclaimer: this may not be at all related to systemd...\r\n\r\nWhen I run the Juniper Network Connect client (ncsvc) it terminates every time the DHCP license is renewed. It doesn't make a difference whether I specify CriticalConnection=true or false. Since systemd-networkd is managing the NIC and the DHCP license, I am suspecting it as the cause for the ncsvc problem. But then again, correlation is not causation as they say.\r\n\r\nThe log files of ncsvc are unfortunately rather cryptic. The only information I could extract from them is the following line:\r\n\r\n20150603133456.514649 ncsvc[p6870.t6870] rmon.error Route to destination 192.168.1.1 is missing mask 255.255.255.255 with gw 0.0.0.0, metric 1, if_id 0, disconnecting (routemon.cpp:628)\r\n\r\nwhich coincides with the following journal entries:\r\n\r\nJun 03 13:34:55.454967 host NetworkManager[1805]: <info>    address 192.168.1.16\r\nJun 03 13:34:55.454985 host NetworkManager[1805]: <info>    plen 24\r\nJun 03 13:34:55.454990 host NetworkManager[1805]: <info>    expires in 300 seconds\r\nJun 03 13:34:55.455026 host NetworkManager[1805]: <info>    gateway 192.168.1.1\r\nJun 03 13:34:55.455035 host NetworkManager[1805]: <info>    nameserver '192.168.1.1'\r\nJun 03 13:34:55.455210 host NetworkManager[1805]: <info>  (wlp6s0): DHCPv4 state changed bound -> bound\r\nJun 03 13:34:55.456679 host dbus[1799]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'\r\nJun 03 13:34:55.461372 host dbus[1799]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'\r\nJun 03 13:34:55.462021 host nm-dispatcher[8295]: Dispatching action 'dhcp4-change' for wlp6s0\r\nJun 03 13:34:56.514958 host systemd-networkd[1803]: tun0            : lost carrier\r\n\r\nIs the DHCP renewal triggering a change in the routing table, which in turn makes ncsvc unhappy?\r\n\r\nsystemd-218\r\nnetworkmanager-1.0.2\r\n\r\nThanks for any suggestions"}}