You are not logged in.

#1 2022-03-04 19:45:59

Morta
Member
Registered: 2019-07-07
Posts: 660

IPv6 on NetworkManager but not on ip addr command

sudo nmcli
enp4s0: connected to Wired connection 1
        "Intel I225-V"
        ethernet (igc), D8:5E:D3:20:C3:9D, hw, mtu 1500
        ip4 default
        inet4 192.168.1.118/24
        route4 default via 192.168.1.1 metric 100
        route4 192.168.1.0/24 metric 100
        inet6 fe80::2f0a:6c3a:a3fd:e7ce/64
        route6 2a02:168:a774:0:8973:c92c:b96f:18ba/128 metric 100
        route6 fe80::/64 metric 100
        route6 fe80::/64 metric 1024
 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d8:5e:d3:20:c3:9d brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.118/24 brd 192.168.1.255 scope global dynamic noprefixroute enp4s0
       valid_lft 5865sec preferred_lft 5865sec
    inet6 fe80::2f0a:6c3a:a3fd:e7ce/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 4e:1f:21:e2:01:28 brd ff:ff:ff:ff:ff:ff permaddr 08:5b:d6:50:0b:5e

Why my NetworkManager shows a IPv6 but ip addr not? They also not reachable over the internal network nor from internet?

Offline

#2 2022-03-04 21:01:53

loqs
Member
Registered: 2014-03-06
Posts: 18,256

Re: IPv6 on NetworkManager but not on ip addr command

 ip a
....
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet6 fe80::2f0a:6c3a:a3fd:e7ce/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
....

Offline

#3 2022-03-04 21:21:09

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: IPv6 on NetworkManager but not on ip addr command

Yes but I should receive a IPv6 from the ISP

Like this one above

2a02:168:a774:0:8973:c92c:b96f:18ba

I have three ArchLinux system and all the same problem Nm receive a IPv6 from the ISP ip addr not

I have OPNsense router which receive a IPv6 an delegate it with ddclient.

So why have nm one an the system not?

Offline

#4 2022-03-04 21:38:09

loqs
Member
Registered: 2014-03-06
Posts: 18,256

Re: IPv6 on NetworkManager but not on ip addr command

Does the following show the IPV6 route?

ip -6 r

Offline

#5 2022-03-04 22:52:09

-thc
Member
Registered: 2017-03-15
Posts: 775

Re: IPv6 on NetworkManager but not on ip addr command

Morta wrote:
route6 2a02:168:a774:0:8973:c92c:b96f:18ba/128 metric 100

This is a IPv6 host route and not a usable IPv6 adress. A real address starts with "inet6".

Morta wrote:

I have OPNsense router which receive a IPv6 an delegate it with ddclient.

Prefix delegation is not ddclient's job.

Your router should obtain a valid IPv6 address (as a DHCPv6 client) from your ISP for the WAN interface and a prefix for your clients. The router advertising daemon (radvd) should hand this prefix out to your clients via SLAAC.

Offline

#6 2022-03-05 11:52:49

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: IPv6 on NetworkManager but not on ip addr command

loqs wrote:

Does the following show the IPV6 route?

ip -6 r

ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2a02:168:a774:0:8973:c92c:b96f:18ba dev enp4s0 proto kernel metric 100 pref medium
fe80::/64 dev enp4s0 proto kernel metric 100 pref medium
fe80::/64 dev enp4s0 proto kernel metric 1024 pref medium

Offline

#7 2022-03-05 11:55:10

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: IPv6 on NetworkManager but not on ip addr command

-thc wrote:
Morta wrote:
route6 2a02:168:a774:0:8973:c92c:b96f:18ba/128 metric 100

This is a IPv6 host route and not a usable IPv6 adress. A real address starts with "inet6".

Morta wrote:

I have OPNsense router which receive a IPv6 an delegate it with ddclient.

Prefix delegation is not ddclient's job.

Your router should obtain a valid IPv6 address (as a DHCPv6 client) from your ISP for the WAN interface and a prefix for your clients. The router advertising daemon (radvd) should hand this prefix out to your clients via SLAAC.

Ok.

 Enable 	Enable DHCPv6 server on LAN interface
Subnet 	2a02:168:a774::
Subnet mask 	64 bits
Available range 	2a02:168:a774:: - 2a02:168:a774:0:ffff:ffff:ffff:ffff
Range 	
from 	to
	
Prefix Delegation Range 	
from 	to
	
Prefix Delegation Size: 

But no delegation of IPv6 for any client? Why? Even iPhone.

Offline

#8 2022-03-05 12:11:57

-thc
Member
Registered: 2017-03-15
Posts: 775

Re: IPv6 on NetworkManager but not on ip addr command

Morta wrote:
 Enable 	Enable DHCPv6 server on LAN interface
Subnet 	2a02:168:a774::
Subnet mask 	64 bits
Available range 	2a02:168:a774:: - 2a02:168:a774:0:ffff:ffff:ffff:ffff
Range 	
from 	to
	
Prefix Delegation Range 	
from 	to
	
Prefix Delegation Size: 

This looks like a stateful DHCPv6 server on the LAN side. Stateful DHCPv6 servers do not serve prefixes to DHCPv6 clients, but complete IPv6 addresses. Even if OPNSense starts a DHCPv6 server (prerequisite is a static IPv6 address on the LAN side) the router advertisement still has to work - and has to announce such a server via "M" flag.

So - please disable the DHCPv6 service on the LAN side and activate the router advertising (radvd) on the LAN side announcing the correct client prefix.

Offline

#9 2022-03-05 12:54:26

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: IPv6 on NetworkManager but not on ip addr command

-thc wrote:
Morta wrote:
 Enable 	Enable DHCPv6 server on LAN interface
Subnet 	2a02:168:a774::
Subnet mask 	64 bits
Available range 	2a02:168:a774:: - 2a02:168:a774:0:ffff:ffff:ffff:ffff
Range 	
from 	to
	
Prefix Delegation Range 	
from 	to
	
Prefix Delegation Size: 

This looks like a stateful DHCPv6 server on the LAN side. Stateful DHCPv6 servers do not serve prefixes to DHCPv6 clients, but complete IPv6 addresses. Even if OPNSense starts a DHCPv6 server (prerequisite is a static IPv6 address on the LAN side) the router advertisement still has to work - and has to announce such a server via "M" flag.

So - please disable the DHCPv6 service on the LAN side and activate the router advertising (radvd) on the LAN side announcing the correct client prefix.

I did this Tutorial

https://www.tuxone.ch/2021/02/fiber7-ac … e.html?m=1

But my ISP should do both statefull and stateless

Offline

#10 2022-03-05 13:02:22

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: IPv6 on NetworkManager but not on ip addr command

https://abload.de/img/0f7a9162-44cc-4b48-865kkst.png

It’s now also possible to get fixed ipv6 with NM on client side?

Mod Edit - Replaced oversized image with link.
CoC - Pasting pictures and code

Last edited by Slithery (2022-03-05 13:13:50)

Offline

#11 2022-03-05 13:47:25

progandy
Member
Registered: 2012-05-17
Posts: 5,279

Re: IPv6 on NetworkManager but not on ip addr command

So you did not follow your tutorial. That said something about using "Unmanaged" or "Assisted" mode.
You'll have to set "Router advertisements" to Unmanaged (to enable SLAAC), Assisted (SLAAC or DHCPv6 allowed), Managed (to force DHCPv6). There is also Stateless DHCP (SLAAC for address assignment and DHCP for DNS/NTP)
https://docs.netgate.com/pfsense/en/lat … v6-ra.html

Last edited by progandy (2022-03-05 13:51:49)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#12 2022-03-05 14:32:40

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: IPv6 on NetworkManager but not on ip addr command

So I did a few changes after wasn’t working anymore.  But it’s was working flawless before. Never had problems but all possibilities don’t have a effect. So I belive its a ISP problem or a Update of OPNsene destory the setup.

Offline

#13 2022-03-05 20:41:37

-thc
Member
Registered: 2017-03-15
Posts: 775

Re: IPv6 on NetworkManager but not on ip addr command

The first option in this dialog (Router Advertisements: Router Only) is the reason no client receives a prefix or address.

Offline

Board footer

Powered by FluxBB