diff options
| author | Axel Neumann <neumann@cgws.de> | 2018-05-21 20:32:09 +0200 |
|---|---|---|
| committer | Daniel Golle <daniel@makrotopia.org> | 2018-07-31 06:32:15 +0200 |
| commit | f7668334a81ea863b6c10dede53e94f1f4dbb93b (patch) | |
| tree | 282c53fa454d51a36afd2ef7b9144cf8ef231bd1 /target/linux/generic/pending-3.18/641-bridge_always_accept_eap.patch | |
| parent | d700eb187ba17fccce71df8123204e7183522f30 (diff) | |
| download | upstream-f7668334a81ea863b6c10dede53e94f1f4dbb93b.tar.gz upstream-f7668334a81ea863b6c10dede53e94f1f4dbb93b.tar.bz2 upstream-f7668334a81ea863b6c10dede53e94f1f4dbb93b.zip | |
Re-enable arbitrary IPv6 addresses as outer ip4-in-ip6 tunnel source address
The 666-Add-support-for-MAP-E-FMRs-mesh-mode.patch kernel patches
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)
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 the patch 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.
Signed-off-by: Axel Neumann <neumann@cgws.de>
Acked-by: Hans Dedecker <dedeckeh@gmail.com>
(cherry picked from 65c05301c2)
Diffstat (limited to 'target/linux/generic/pending-3.18/641-bridge_always_accept_eap.patch')
0 files changed, 0 insertions, 0 deletions