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#43956 - [linux] per interface forwarding does _not_ follow net.ipv4.conf.all.forwarding
Attached to Project:
Arch Linux
Opened by James (thx1138) - Thursday, 26 February 2015, 03:40 GMT
Last edited by Jan de Groot (JGC) - Thursday, 05 October 2017, 07:38 GMT
Opened by James (thx1138) - Thursday, 26 February 2015, 03:40 GMT
Last edited by Jan de Groot (JGC) - Thursday, 05 October 2017, 07:38 GMT
|
Detailslinux 3.19-1
Setting "net.ipv4.conf.all.forwarding=1" and "net.ipv4.conf.default.forwarding=1" does _not_ set forwarding on the per interface configurations, leaving "net.ipv4.conf.<interface>.forwarding=0". Of course, the result is that routing then fails, where this use to work up to linux 3.18.6-1. This is on a "mixed" router/host setup, with accept_ra=2. This will mean that per interface forwarding will have to be set explicitly, in /etc/sysctl.conf, or in /etc/sysctl.d/*.conf, or manually, assuming that this behavior is not a kernel bug. A warning note should be added to the install for this upgrade, describing the need for explicit per interface forwarding. |
This task depends upon
So I'd say this is no longer an issue, and the bug report can be closed. Thanks.