Hello,

the 666 kernel patches [1,2,3] break the possibility for using an ip4ip6
tunnel interface as a fall back interface accepting ip4-in-ip6 tunneled
packets from any remote address. This works out of the box with any
normal (non-666-patched) 4.4 (and earlier) kernel and can be configured
by setting up an 'ip -6 tunnel' with type 'any' or 'ip4ip6' and a remote
address of '::'.

The misbehavior comes with line 290 of [3] which discards all packets
that do not show the expected saddr, even if no single fmr rule was
defined and despite the validity of the saddr was already approved earlier.

Attached diff would re-enable this fall back capability without
affecting the behavior in case of any configured FMR rules.

It would be nice if the proposed or a similar fix could be applied asap
because currently I see no way of recovering the standard kernel
behavior which breaks certain desired bmx6 and bmx7 tunneling features.

Best regards
/axel


[1]
https://github.com/openwrt-mirror/openwrt/blob/master/target/linux/generic/patches-3.18/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
[2]
https://github.com/openwrt-mirror/openwrt/blob/master/target/linux/generic/patches-4.1/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
[3]
https://github.com/openwrt-mirror/openwrt/blob/master/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch#L290

1032c1032
< 				if (fmr) {
---
> 				if (fmr)
1036,1039c1036,1038
< 					if (!ipv6_addr_equal(&ipv6h->saddr, &expected)) {
< 						rcu_read_unlock();
< 						goto discard;
< 					}
---
> 				if (!ipv6_addr_equal(&ipv6h->saddr, &expected)) {
> 					rcu_read_unlock();
> 					goto discard;
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to