Bug 1743189 - Cannot set IPv6 manual address and gateway
Summary: Cannot set IPv6 manual address and gateway
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.1
Hardware: x86_64
OS: Linux
Target Milestone: rc
: 8.1
Assignee: sushil kulkarni
QA Contact: Desktop QE
Depends On:
Blocks: nmstate-nm-prio
TreeView+ depends on / blocked
Reported: 2019-08-19 09:56 UTC by Gris Ge
Modified: 2019-10-15 12:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-15 12:59:41 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
Reproduce script. (984 bytes, application/x-shellscript)
2019-08-19 09:56 UTC, Gris Ge
no flags Details
System logs with NM trace enabled (469.14 KB, text/plain)
2019-08-19 10:02 UTC, Gris Ge
no flags Details

Description Gris Ge 2019-08-19 09:56:49 UTC
Created attachment 1605727 [details]
Reproduce script.

Description of problem:

Cannot switch ipv6.method from ignore to ipv6.method manual with gateway

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. sudo ./ipv6_bug.sh

Actual results:

Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)
Hint: use 'journalctl -xe NM_CONNECTION=6850b6a2-e8d0-4a02-aa37-76818b4d7636 + NM_DEVICE=dhcpcli' to get more details.

Expected results:
No failure.

Additional info:

If I remove the `ipv6.gateway 2001:db8:1::`, it works well.

Comment 1 Gris Ge 2019-08-19 10:02:11 UTC
Created attachment 1605728 [details]
System logs with NM trace enabled

Comment 2 Beniamino Galvani 2019-08-19 11:41:12 UTC
The route can't be added because gateway address 2001:db8:1:: is already assigned to interface dhcpsrv, and kernel complains with:

  platform-linux: netlink: recvmsg: error message from kernel: Invalid argument (22) "Gateway can not be a local address" for request 50

You should put the two dhcp* interfaces in different namespaces to reproduce a valid scenario, or use a different gateway address.

Comment 3 Beniamino Galvani 2019-08-19 11:50:31 UTC
For example, I use a script like this to test DHCPv4 and IPv6 autoconf locally without conflicts between the two veth interfaces:


ip link add veth0 type veth peer name veth1
ip netns add ns1
ip link set veth1 netns ns1
ip link set veth0 up
ip -n ns1 link set veth1 up
ip -n ns1 address add dev veth1
ip -n ns1 address add dev veth1 fd01::1/64
ip netns exec ns1 dnsmasq --bind-interfaces --interface veth1 -d --dhcp-range=,,1m --dhcp-range=fd01::100,fd01::200,slaac --enable-ra -h

Comment 4 Gris Ge 2019-08-20 03:48:00 UTC
Hi Beniamino Galvani,

Thanks. Changing the gateway address fixed the problem.

Note You need to log in before you can comment on or make changes to this bug.