[PVE-User] Problem With Bond & VLANs - Help Please

proxmox at selund.se proxmox at selund.se
Fri Aug 16 13:32:05 CEST 2024


On 16/08/2024 12:42, duluxoz wrote:
> Hi Stephan,
>
> My apologises, I should have been more precise.
>
> What doesn't work? Most of the ifaces are down (won't come up 
> automatically as I expect (not even NIC3)), and so I have no 
> connectivity to the LAN, let alone the rest of the outside world.
>
> Yes, each VLAN should have its own gateway - each VLAN is its own 
> subnet, of course.
>
> Results of `ip r`:
>
> ~~~
> default via 10.0.200.1 dev vmbr0 proto kernal onlink linkdown
> 10.0.100.0/24 dev bond0.100 proto kernal scope link src 10.0.100.0 
> linkdown
> 10.0.200.0/24 dev bond0.200 proto kernal scope link src 10.0.200.0 
> linkdown
> 10.0.200.0/24 dev vmbr0 proto kernal scope link src 10.0.200.100 linkdown
> ~~~
>

I believe your problem is in your definition of bond0
~~~
auto bond0
iface bond0 inet manual
    bond-members eno1 eno2
~~~

Bond members here should be eno1 and eno2, and not nic1 nic2
Looking at the eno3 nic, you have done the same problem nic3 should be eno3

~~~
auto eno3
iface eno3 inet static
    address 10.0.300.100/24
~~~

Another problem I see with your configuration is that you define 
gateways on each vlan interface. Linux only have one routing domain.
Remember that you don't need either gateway nor ip address on the bridge 
you use for vm's.




More information about the pve-user mailing list