Allow ping in firewall for both VMs, and add an interface to the same VLAN to both VMs.
Attempt to ping one VM from the other (observe timeouts).
There is some weirdness with the 40Gbit link:
1. Create a VM on pve and a VM on pve2.
2. Allow ping in firewall for both VMs, and add an interface to the same VLAN to both VMs.
3. Attempt to ping one VM from the other (observe timeouts).
Switched to linux bridges and this connection should begin working once the 40Gbit link & bridge is set up. Adding a VLAN via web interface didn't work for some reason (not even an entry in ip a).
Switched to linux bridges and this connection should begin working once the 40Gbit link & bridge is set up. Adding a VLAN via web interface didn't work for some reason (not even an entry in `ip a`).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There is some weirdness with the 40Gbit link:
pve <--> pve2 link issuesto pve <---> pve2 link issuesSwitched to linux bridges and this connection should begin working once the 40Gbit link & bridge is set up. Adding a VLAN via web interface didn't work for some reason (not even an entry in
ip a).Closing since OVS is no longer used and as a result this is no longer an issue.