FS#3426 - vxlan uci setup: infinite looping netifd #8572
Labels
Comments
|
s-er-01: It's still happening with |
|
s-er-01: It's still happening with |
|
Hi, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bittorf:
tested with trunk r14825
when configuring a vxlan interface like described in the wiki:
https://openwrt.org/docs/guide-user/network/tunneling_interface_protocols#vxlan_example_configuration
the device will up/down our interface in a loop forever:
# logread ... Mon Nov 2 07:31:03 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:03 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:04 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:05 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is now down Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is setting up now Mon Nov 2 07:31:06 2020 daemon.notice netifd: Interface 'vx' is now down ...uci parameter:
config interface 'vx' option proto 'vxlan' option peeraddr '10.63.22.98' option port '4789' option vid '4'config interface 'l2vpn'
option ifname '@vx'
option proto 'static'
option ipaddr '192.168.22.4'
option netmask '255.255.255.0'
option layer '2'
when manually configuring this, it works without issues:
ip link add dev vx type vxlan id 4 remote 10.63.22.98 dstport 4789 ip link set dev vx up ip addr add 192.168.22.4/24 dev vxThe text was updated successfully, but these errors were encountered: