FS#56646 - [linux] IPv6 packets Forwarding or NAT not works on 4.14.4-1

Attached to Project: Arch Linux
Opened by joshu (joshu) - Saturday, 09 December 2017, 13:47 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:26 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: IPv6 packets Forwarding or NAT not works

Additional info:
Kernel 4.14.4-1-ARCH
When I downgrade to 4.13.12-1-ARCH this problem doesn't occur.

Steps to reproduce:
Enable ipv6 for every interface and set ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
when I try to run ip6tables -t nat -vL to see how many packets has been dealed with, there is 0 packets on PREROUTING, INPUT, OUTPUT, POSTROUTING chain, and I see no packets has been forwarded to eth0 using tcpdump
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 28 May 2023, 06:26 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. Assuming fixed. If still an issue, please report upstream.
Comment by Josef Hopfgartner (joho1001) - Thursday, 14 December 2017, 12:36 GMT
seems related to
https://bugs.archlinux.org/task/56718
Comment by loqs (loqs) - Thursday, 28 December 2017, 21:50 GMT
Is this still an issue with linux 4.14.9-1 currently in testing?
Comment by joshu (joshu) - Friday, 29 December 2017, 06:14 GMT
It seems that ipv6 packets forwarding works well with 4.14.9-1 because I can see packets being forwarded to interface eth0, but ipv6 NAT(MASQUERADE) doesn't work, and I see 0 packets captured on POSTROUTING chain in nat table.
Comment by loqs (loqs) - Friday, 29 December 2017, 18:00 GMT
I would suggest asking on the netdev mailing list or the kernel bugzilla to see if upstream is already aware of the issue.
Does upstream consider it a bug and if so is there is a fix available or if the issue requires an upstream fix.
Comment by Josef Hopfgartner (joho1001) - Wednesday, 03 January 2018, 18:12 GMT
maybe fixed with kernel 4.14.10-1-ARCH
Comment by mattia (nTia89) - Monday, 28 February 2022, 16:48 GMT
I cannot reproduce the issue. Is it still valid for you?

Loading...