nmcli PPPoE connection stops working after 30 minutes (IPv6 only)

Issues related to configuring your network
Post Reply
jselke
Posts: 1
Joined: 2019/03/16 12:00:41

nmcli PPPoE connection stops working after 30 minutes (IPv6 only)

Post by jselke » 2019/03/16 12:29:51

EDIT: Problem description simplified, as the issue is unrelated to my setup of using two ISPs. Also, the issue only affects the IPv6 connectivity.

Hi all,

I use NetworkManager to establish my Internet connection via ADSL (PPPoE). My ISP offers native IPv4 + IPv6 connectivity (dual stack), which I would like to use. Setting up the connection via nmcli was easy, also establishing the connections works well. However, after exactly 30 minutes the connection stops working. It is still up, but it seems that no IPv6 traffic is transferred anymore. I used parallel pings (IPv4: 8.8.8.8, IPv6: ipv6.google.com), to check connectivity. The IPv6 ping stops working after exactly 30 minutes.

I configured and started the DSL connection as follows:

Code: Select all

yum -y install NetworkManager-ppp

# Set up connection
nmcli connection add con-name dsl-htp type pppoe ifname enp3s0 username <myusername> password <mypassword> connection.zone wan

# Enable autoconnect
nmcli con mod dsl-htp connection.autoconnect yes

# Start connection
nmcli con up dsl-htp
However, when starting the connection, the message "no IPV6CP notifier support; IPv6 not available" appears in the NetworkManager log.

Could this be related to my problem?

Do you need any further information (config, logs, ...)?



Here is the output of "journalctl -f -u NetworkManager" when starting the DSL connection:

Code: Select all

Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2118] device (enp3s0): Activation: starting connection 'dsl-htp' (9b656b7b-c9d6-45d7-987c-4cc6ce98bf9d)
Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2146] audit: op="connection-activate" uuid="9b656b7b-c9d6-45d7-987c-4cc6ce98bf9d" name="dsl-htp" pid=4717 uid=0 result="success"
Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2154] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2186] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2413] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2478] ppp-manager: starting PPP connection
Mar 16 13:21:28 router.lan NetworkManager[3042]: <info>  [1552738888.2667] ppp-manager: pppd started with pid 4721
Mar 16 13:21:28 router.lan pppd[4721]: Plugin rp-pppoe.so loaded.
Mar 16 13:21:28 router.lan pppd[4721]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
Mar 16 13:21:28 router.lan NetworkManager[3042]: Plugin rp-pppoe.so loaded.
Mar 16 13:21:28 router.lan NetworkManager[3042]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
Mar 16 13:21:28 router.lan pppd[4721]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Mar 16 13:21:28 router.lan NetworkManager[3042]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Mar 16 13:21:28 router.lan pppd[4721]: nm-ppp-plugin: (plugin_init): initializing
Mar 16 13:21:28 router.lan pppd[4721]: nm-ppp-plugin: no IPV6CP notifier support; IPv6 not available
Mar 16 13:21:28 router.lan pppd[4721]: pppd 2.4.5 started by root, uid 0
Mar 16 13:21:28 router.lan pppd[4721]: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
Mar 16 13:21:29 router.lan pppd[4721]: PPP session is 5369
Mar 16 13:21:29 router.lan NetworkManager[3042]: PPP session is 5369
Mar 16 13:21:29 router.lan pppd[4721]: Connected to 56:e0:32:c5:d8:15 via interface enp3s0
Mar 16 13:21:29 router.lan NetworkManager[3042]: Connected to 56:e0:32:c5:d8:15 via interface enp3s0
Mar 16 13:21:29 router.lan NetworkManager[3042]: Using interface ppp0
Mar 16 13:21:29 router.lan NetworkManager[3042]: Connect: ppp0 <--> enp3s0
Mar 16 13:21:29 router.lan pppd[4721]: Using interface ppp0
Mar 16 13:21:29 router.lan pppd[4721]: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
Mar 16 13:21:29 router.lan pppd[4721]: Connect: ppp0 <--> enp3s0
Mar 16 13:21:29 router.lan NetworkManager[3042]: <info>  [1552738889.4151] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/8)
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate'
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials...
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
Mar 16 13:21:32 router.lan pppd[4721]: CHAP authentication succeeded
Mar 16 13:21:32 router.lan pppd[4721]: CHAP authentication succeeded
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network'
Mar 16 13:21:32 router.lan NetworkManager[3042]: CHAP authentication succeeded
Mar 16 13:21:32 router.lan NetworkManager[3042]: CHAP authentication succeeded
Mar 16 13:21:32 router.lan NetworkManager[3042]: peer from calling number 56:E0:32:C5:D8:15 authorized
Mar 16 13:21:32 router.lan pppd[4721]: peer from calling number 56:E0:32:C5:D8:15 authorized
Mar 16 13:21:32 router.lan pppd[4721]: local  LL address fe80::d492:7946:768d:3b69
Mar 16 13:21:32 router.lan NetworkManager[3042]: local  LL address fe80::d492:7946:768d:3b69
Mar 16 13:21:32 router.lan NetworkManager[3042]: remote LL address fe80::56e0:32ff:fec5:d815
Mar 16 13:21:32 router.lan pppd[4721]: remote LL address fe80::56e0:32ff:fec5:d815
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (nm_phasechange): status 9 / phase 'running'
Mar 16 13:21:32 router.lan pppd[4721]: local  IP address 89.183.91.47
Mar 16 13:21:32 router.lan pppd[4721]: remote IP address 81.14.248.241
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (nm_ip_up): ip-up event
Mar 16 13:21:32 router.lan NetworkManager[3042]: local  IP address 89.183.91.47
Mar 16 13:21:32 router.lan NetworkManager[3042]: remote IP address 81.14.248.241
Mar 16 13:21:32 router.lan NetworkManager[3042]: primary   DNS address 81.14.244.9
Mar 16 13:21:32 router.lan NetworkManager[3042]: secondary DNS address 212.59.54.180
Mar 16 13:21:32 router.lan pppd[4721]: primary   DNS address 81.14.244.9
Mar 16 13:21:32 router.lan pppd[4721]: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager...
Mar 16 13:21:32 router.lan pppd[4721]: secondary DNS address 212.59.54.180
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.8301] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.8449] ppp-manager: (IPv4 Config Get) reply received.
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.8528] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.8608] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.9808] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.9825] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 16 13:21:32 router.lan NetworkManager[3042]: <info>  [1552738892.9968] policy: set 'dsl-htp' (ppp0) as default for IPv6 routing and DNS
Mar 16 13:21:33 router.lan NetworkManager[3042]: <info>  [1552738893.0081] device (enp3s0): Activation: successful, device activated.
Best wishes,
Joachim

Post Reply

Return to “CentOS 7 - Networking Support”