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!
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!
FS#57854 - [dhcpcd] 7.0.1-1 overwrites accept_ra if called IPv4only
Attached to Project:
Arch Linux
Opened by No No (bk) - Thursday, 15 March 2018, 19:37 GMT
Last edited by Ronald van Haren (pressh) - Wednesday, 28 March 2018, 08:57 GMT
Opened by No No (bk) - Thursday, 15 March 2018, 19:37 GMT
Last edited by Ronald van Haren (pressh) - Wednesday, 28 March 2018, 08:57 GMT
|
DetailsDescription:
Before starting dhcpcd via netctl net.ipv6.conf.wlp2s0.accept_ra is set to 1. After a started profile with dhcpcd it is set to 0, resulting in disabled SLAAC on the host. As dhcpcd is started with with option -4 (IPv4only) it should not touch anything regarding IPv6. Additional info: * dhcpcd 7.0.1-1 * used arguments: dhcpcd -4 -q -t 30 -L wlp2s0 * (Line which sets accept_ra)[https://github.com/rsmarples/dhcpcd/blob/dhcpcd-7.0.1/src/if-linux.c#L1722] Steps to reproduce: * Use a network with IPv4 via DHCP and IPv6 via SLAAC. |
This task depends upon
Closed by Ronald van Haren (pressh)
Wednesday, 28 March 2018, 08:57 GMT
Reason for closing: Fixed
Additional comments about closing: fixed upstream in 7.0.2-1
Wednesday, 28 March 2018, 08:57 GMT
Reason for closing: Fixed
Additional comments about closing: fixed upstream in 7.0.2-1
Comment by Doug Newgard (Scimmia) -
Saturday, 17 March 2018, 02:26 GMT
Yes, this was an upstream decision that has already been reversed. https://github.com/rsmarples/dhcpcd/commit/8f483d192082a953dd035f38ee4555735106f1fc
Comment by Roy Marples (rsmarples) -
Tuesday, 27 March 2018, 06:40 GMT
dhcpcd-7.0.2 has been released which should solve this.