diff options
author | Johannes Kimmel <fff@bareminimum.eu> | 2020-12-15 00:31:52 +0100 |
---|---|---|
committer | Hans Dedecker <dedeckeh@gmail.com> | 2020-12-31 11:53:21 +0100 |
commit | 3f5619f259de42af4404e0e36d11df4adcef9f5e (patch) | |
tree | 2efb3a449cf27b81ea281f53408c855a2ee3af63 /scripts/dl_cleanup.py | |
parent | 31554e50d2c3d0707a40f9ed08b0d6999f584ba2 (diff) | |
download | upstream-3f5619f259de42af4404e0e36d11df4adcef9f5e.tar.gz upstream-3f5619f259de42af4404e0e36d11df4adcef9f5e.tar.bz2 upstream-3f5619f259de42af4404e0e36d11df4adcef9f5e.zip |
vxlan: allow for dynamic source ip selection (FS#3426)
By setting 'auto', the zero address or the empty string as source
address (option ipaddr, option ip6addr), vxlan will choose one
dynamically. This helps in setups where a wan ip or prefix changes.
This corresponse to setting up an vxlan tunnel with:
proto vxlan6:
# ip link add vx0 type vxlan id ID local :: ...
proto vxlan:
# ip link add vx0 type vxlan id ID local 0.0.0.0 ...
While it is possible to not specify a source ip at all, the kernel will
default to setting up a ipv4 tunnel. The kernel will take any hint from
source and peer ips to figure out, what tunnel type to use. To make sure
we setup an ipv6 tunnel for proto vxlan6, this workaround is needed.
This will not change the behaviour of currently working configurations.
However this will allow former broken configurations, namely those not
specifying both a source address and tunnel interface, to setup a
tunnel interface. Previously those configurations weren't reporting an
error and were stueck in a setup loop like in Bug FS#3426.
This change lifts the currently very strict behaviour and should fix the
following bug:
Fixes: FS#3426
Ref: https://bugs.openwrt.org/index.php?do=details&task_id=3426
Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>
Diffstat (limited to 'scripts/dl_cleanup.py')
0 files changed, 0 insertions, 0 deletions