also, if you are at ovh, can you check that you don't have files in
I known 1user having a /etc/network/interfaces.d/50-cloud-init files installed by default by ovh giving some reload error too
do you use ifupdown2 ?
if yes, maybe it's ifupdown2 bug (but I don't have seen this before), or a kernel change.
but I'm unable to reproduce it on my side, it's working fine.
do you have only this at boot ? or does a "ifup vmbr1" is working ?
what is the ouput of #ip addr &&...
if you use vlan aware bridge, tag directly the bridge, like
iface lo inet loopback
iface eno1 inet manual
iface eno2 inet manual
iface bond0 inet manual
bond-slaves eno1 eno2
This is an expected behavior as tcpdump tool on Linux because the checksum is offloading on your NIC but tcpdump reads IP packets from the Linux kernel right before the actual checksum takes place in the NIC chipset.
I was looking how vmware nsx implemented it, but traffic is also redirected to central firewall(s) pair somewhere in the network (with some kind of transparent routing), but I'm not sure that it's possible across vm in same lan/vxlan, only when traffic is routed across vxlan.
I don't known...
currently it's not possible with sdn, maybe later (as we already have the proxmox firewall).
It's not so easy, as with multiple pfsense, you'll need to sync conntrack table, if you don't want to break connection on live migration .(it's possible with carp, but I don't known how many pfsense...
all seem to be fine at host level.
are you sure that's it's not a physical switch configuration problem where jumbo frame is not enable ?
are you are to do a "ping -Mdo -s 8950 192.168.0.2" from 192.168.0.1
you can do a "brctl show" on the node where the lxc ct does not start ? Do you have same problem with a vm ? (This look like the vnet bridge is not created on the host, but you should have an error when applying sdn configuration).
do you use proxmox 6.4 with last update ?
" ovs-appctl fdb/show vmbrX" should display the mac address table
I think the only usefull feature could be port mirroring, it's a little bit difficult to implement with linux bridge. but if you don"t need it, just keep linux bridge.
seem related to "allow-xxx", I don't known when it's...
The main problem with mode other than 802.3ad or active-backup, is that you can have for 1 tcp connection, packets balanced on 2 differents interfacces, and you can have out of order packets at the switch side, so retransmit.
almost any swich vendor support lacp, some vendor support other mode...
it's work with mtu 9000 without problem, but you still need 50 lower bytes on the vnet than the physical interface.
I'm running vxlan in production with mtu=9200 on my switchs + mtu=9200 on my ethX on hypervisor + mtu=9000 on vnet
but it should works with 9000 on physical interface + 8950 on...
your config seem to be correct.
I don't see why it's not working with gateway...(are you sure that config was correctly reloaded ?)
if 192.168.0.1 can connect to 192.168.0.2, the vxlan tunnel should works out of the box.
(with the gateway defined, are you able to ping from 192.168.0.1 to...