Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57829 - netctl when configured "IP6=stateless" does not configure the linux kernel to accept RA's.

Attached to Project: Arch Linux
Opened by Maarten Maathuis (madman2003) - Tuesday, 13 March 2018, 21:14 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 17 March 2018, 02:28 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The following settings are 0, when they should be 1:
net.ipv6.conf.<interface>.autoconf = 1
net.ipv6.conf.<interface>.accept_ra = 1

Additional info:
* netctl-1.15-1
* profile:

Description='Lalalala'
Interface=<interface>
Connection=wireless
Security=wpa
ESSID=Home
IP=dhcp
IP6=stateless
Key=<private>

Steps to reproduce:
Add above profile, activate the interface, observe that sysctl settings are not correct, and no IPV6 address is obtained.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 17 March 2018, 02:28 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#57854 
Comment by Doug Newgard (Scimmia) - Wednesday, 14 March 2018, 03:46 GMT
Using dhcpcd, I assume?
Comment by Daniel Lublin (quite) - Thursday, 15 March 2018, 17:09 GMT
Probably, since that's the default DHCPClient.

dhcpcd 7.0.1 until commit 8f483d192082a953dd035f38ee4555735106f1fc of 2018-02-02 disables kernel IPv6 RA handling and setup, if it is used for IPv4 only. See:

https://bbs.archlinux.org/viewtopic.php?id=235137

I was troubled by this myself and didn't solve it until today when I came across the above thread. Very unfortunate, I must say.

Comment by Maarten Maathuis (madman2003) - Thursday, 15 March 2018, 19:29 GMT
dhcpcd is active indeed, although not via the normal service, so I guess netctl invoked it.
So the gist of this is wait for a new dhcpcd version?
Comment by Jouke Witteveen (jouke) - Friday, 16 March 2018, 11:23 GMT
Are there any related messages in the journal?
Netctl should attempt to set
net.ipv6.conf.<interface>_sysctl.accept_ra
to 1 in this case.

Loading...