Missing IPv6 config on PPPoE connection
- From: Joachim Selke <mail joachim-selke de>
- To: networkmanager-list gnome org
- Subject: Missing IPv6 config on PPPoE connection
- Date: Mon, 06 Jan 2020 11:57:29 +0100
Hello everyone,
I use a PPPoE connection in NetworkManager (RHEL 8.1, NM 1.20.0) to
connect with my ISP via DSL modem. My ISP supports IPv4 and IPv6 in
dual stack mode and provides the IPv6 config information via router
advertisements (i.e., no DHCPv6). I would like to use IPv4 as well as
IPv6 for this connection. However, for some reason, NM does not perform
any IPv6 configuration. For comparison purposes, I used a Windows PC to
set up the DSL connection. Then, IPv6 works as expected.
I provided more details below. What did I miss?
Best wishes,
Joachim
My connection is set up as follows in nmcli:
nmcli connection add con-name htp type pppoe
ifname enp3s0
username <MYUSER>
password <MPASS>
connection.zone wan
Activating the connection works fine, but there just doesn't seem to by
any IPv6 config:
[root@router ~]# nmcli con show htp | grep IP6
IP6.ADDRESS[1]: fe80::XXXX:XXXX:XXXX:XXXX/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 300
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256, table=255
[root@router ~]# nmcli -g GENERAL.IP-IFACE dev show enp3s0
ppp0
[root@router ~]# ip -6 route show dev ppp0
fe80::/10 metric 1 pref medium
fe80::/10 proto kernel metric 256 pref medium
I neither see a global IPv6 address, nor a default gateway.
I receive router advertisements (as expected) when the connection is
activated as well as every 10 minutes afterwards, but NM seems to
ignore them:
[root@router ~]# radvdump
#
# radvd configuration generated by radvdump 2.17
# based on Router Advertisement from fe80::56e0:XXXX:XXXX:XXXX
# received by interface ppp0
#
interface ppp0
{
AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with
radvdump
AdvManagedFlag off;
AdvOtherConfigFlag off;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvDefaultLifetime 1800;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvLinkMTU 1492;
prefix 2a02:560:XXXX:XXXX::/64
{
AdvValidLifetime 2592000;
AdvPreferredLifetime 604800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
}; # End of interface definition
[root@router ~]# rdisc6 ppp0
Soliciting ff02::2 (ff02::2) on ppp0...
Hop limit : 64 ( 0x40)
Stateful address conf. : No
Stateful other conf. : No
Mobile home agent : No
Router preference : medium
Neighbor discovery proxy : No
Router lifetime : 1800 (0x00000708) seconds
Reachable time : unspecified (0x00000000)
Retransmit time : unspecified (0x00000000)
MTU : 1492 bytes (valid)
Prefix : 2a02:560:XXXX:XXXX::/64
On-link : Yes
Autonomous address conf.: Yes
Valid time : 2592000 (0x00278d00) seconds
Pref. time : 604800 (0x00093a80) seconds
from fe80::56e0:XXXX:XXXX:XXXX
Here is an extract from the log (set on INFO level) when activating the
connection. (I have also a log with DEBUG level available but would
rather not post it publicly due to privacy reasons. I can provide it
via personal email if needed.)
[root@router ~]# journalctl -f -u NetworkManager
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.3872] agent-manager: req[0x5620d38b9000,
:1.4973/nmcli-connect/0]: agent registered
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.3922] device (enp3s0): Activation: starting
connection 'htp' (d90bf9a9-dc80-40a9-827a-7e5a44fb6611)
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.3926] audit: op="connection-activate"
uuid="d90bf9a9-dc80-40a9-827a-7e5a44fb6611" name="htp" pid=29955 uid=0
result="success"
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.3933] device (enp3s0): state change: disconnected
-> prepare (reason 'none', sys-iface-state: 'managed')
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.3956] manager: NetworkManager state is now
CONNECTING
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.3966] device (enp3s0): state change: prepare ->
config (reason 'none', sys-iface-state: 'managed')
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.4153] device (enp3s0): state change: config -> ip-
config (reason 'none', sys-iface-state: 'managed')
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.4189] ppp-manager: starting PPP connection
Jan 05 17:14:11 router.lan NetworkManager[1047]:
<info> [1578240851.4253] ppp-manager: pppd started with pid 29959
Jan 05 17:14:11 router.lan pppd[29959]: Plugin rp-pppoe.so loaded.
Jan 05 17:14:11 router.lan NetworkManager[1047]: Plugin rp-pppoe.so
loaded.
Jan 05 17:14:11 router.lan NetworkManager[1047]: RP-PPPoE plugin
version 3.8p compiled against pppd 2.4.7
Jan 05 17:14:11 router.lan pppd[29959]: RP-PPPoE plugin version 3.8p
compiled against pppd 2.4.7
Jan 05 17:14:11 router.lan pppd[29959]: Plugin
/usr/lib64/pppd/2.4.7/nm-pppd-plugin.so loaded.
Jan 05 17:14:11 router.lan NetworkManager[1047]: Plugin
/usr/lib64/pppd/2.4.7/nm-pppd-plugin.so loaded.
Jan 05 17:14:11 router.lan pppd[29959]: nm-ppp-plugin: initializing
Jan 05 17:14:11 router.lan pppd[29959]: pppd 2.4.7 started by root, uid
0
Jan 05 17:14:11 router.lan pppd[29959]: nm-ppp-plugin: status 3 / phase
'serial connection'
Jan 05 17:14:12 router.lan pppd[29959]: PPP session is 4482
Jan 05 17:14:12 router.lan NetworkManager[1047]: PPP session is 4482
Jan 05 17:14:12 router.lan NetworkManager[1047]: Connected to
56:e0:32:c5:d8:15 via interface enp3s0
Jan 05 17:14:12 router.lan NetworkManager[1047]: Using interface ppp0
Jan 05 17:14:12 router.lan pppd[29959]: Connected to 56:e0:32:c5:d8:15
via interface enp3s0
Jan 05 17:14:12 router.lan pppd[29959]: nm-ppp-plugin: status 5 / phase
'establish'
Jan 05 17:14:12 router.lan NetworkManager[1047]: Connect: ppp0 <-->
enp3s0
Jan 05 17:14:12 router.lan pppd[29959]: Using interface ppp0
Jan 05 17:14:12 router.lan pppd[29959]: Connect: ppp0 <--> enp3s0
Jan 05 17:14:12 router.lan NetworkManager[1047]:
<info> [1578240852.5642] manager: (ppp0): new Ppp device
(/org/freedesktop/NetworkManager/Devices/16)
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: status 6 / phase
'authenticate'
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: passwd-hook,
requesting credentials...
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: got credentials
from NetworkManager
Jan 05 17:14:15 router.lan pppd[29959]: CHAP authentication succeeded
Jan 05 17:14:15 router.lan pppd[29959]: CHAP authentication succeeded
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: status 8 / phase
'network'
Jan 05 17:14:15 router.lan NetworkManager[1047]: CHAP authentication
succeeded
Jan 05 17:14:15 router.lan NetworkManager[1047]: peer from calling
number 56:E0:32:C5:D8:15 authorized
Jan 05 17:14:15 router.lan pppd[29959]: peer from calling number
56:E0:32:C5:D8:15 authorized
Jan 05 17:14:15 router.lan NetworkManager[1047]: local LL address
fe80::90c4:e255:a8d5:2a9f
Jan 05 17:14:15 router.lan NetworkManager[1047]: remote LL address
fe80::56e0:32ff:fec5:d815
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: status 9 / phase
'running'
Jan 05 17:14:15 router.lan pppd[29959]: local LL address
fe80::90c4:e255:a8d5:2a9f
Jan 05 17:14:15 router.lan pppd[29959]: remote LL address
fe80::56e0:32ff:fec5:d815
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: ip6-up event
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: sending IPv6
config to NetworkManager...
Jan 05 17:14:15 router.lan NetworkManager[1047]:
<info> [1578240855.8586] ppp-manager: (IPv6 Config Get) reply
received.
Jan 05 17:14:15 router.lan pppd[29959]: local IP address
89.183.120.101
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: ip-up event
Jan 05 17:14:15 router.lan NetworkManager[1047]: local IP address
89.183.120.101
Jan 05 17:14:15 router.lan NetworkManager[1047]: remote IP address
81.14.248.241
Jan 05 17:14:15 router.lan NetworkManager[1047]: primary DNS address
81.14.244.9
Jan 05 17:14:15 router.lan NetworkManager[1047]: secondary DNS address
212.59.54.180
Jan 05 17:14:15 router.lan pppd[29959]: remote IP address 81.14.248.241
Jan 05 17:14:15 router.lan pppd[29959]: nm-ppp-plugin: sending IPv4
config to NetworkManager...
Jan 05 17:14:15 router.lan pppd[29959]: primary DNS address
81.14.244.9
Jan 05 17:14:15 router.lan NetworkManager[1047]:
<info> [1578240855.9498] device (ppp0): state change: unmanaged ->
unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Jan 05 17:14:15 router.lan pppd[29959]: secondary DNS address
212.59.54.180
Jan 05 17:14:15 router.lan NetworkManager[1047]:
<info> [1578240855.9572] ppp-manager: (IPv4 Config Get) reply
received.
Jan 05 17:14:15 router.lan NetworkManager[1047]:
<info> [1578240855.9618] device (enp3s0): state change: ip-config ->
ip-check (reason 'none', sys-iface-state: 'managed')
Jan 05 17:14:15 router.lan NetworkManager[1047]:
<info> [1578240855.9661] device (ppp0): state change: unavailable ->
disconnected (reason 'none', sys-iface-state: 'external')
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.3070] device (enp3s0): state change: ip-check ->
secondaries (reason 'none', sys-iface-state: 'managed')
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.3085] device (enp3s0): state change: secondaries ->
activated (reason 'none', sys-iface-state: 'managed')
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.3116] manager: NetworkManager state is now
CONNECTED_LOCAL
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.3184] manager: NetworkManager state is now
CONNECTED_SITE
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.3193] policy: set 'htp' (ppp0) as default for IPv4
routing and DNS
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.3256] device (enp3s0): Activation: successful,
device activated.
Jan 05 17:14:16 router.lan NetworkManager[1047]:
<info> [1578240856.7680] manager: NetworkManager state is now
CONNECTED_GLOBAL
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
