[SOLVED] Proxmox Virtual Environment GUI in all NIC

[argumentum]

Installed Proxmox in the slow nick. Then realized that and added a bridge for the fast NIC. When I unplug the slow NICs cable I have no access to the other NIC, With the slow NIC cable plugged in I can access both IPs but without it I can not access the GUI. The VMs work fine. Is the GUI that I can not get into. Help

 

[argumentum]

..and you're gonna need the interfaces file to help me:

auto lo
iface lo inet loopback

iface enp196s0 inet manual

iface eno1 inet manual

iface enx00e04c3602bc inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.0.198/24
        bridge-ports enp196s0
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.0.98/24
        gateway 192.168.0.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

 

[BobhWasatch]

Both bridges are in the same network, so the kernel will pick one at random for reply packets. Remove the IP from the "slow" one and it should use the "fast" one.

 

[argumentum]

that shouldn't be that way but, I'll try it.
I did and applied config but nothing changed. I'll reboot. brb

 

[BobhWasatch]

What shouldn't be what way? Don't know what you mean by that. What I stated is how the kernel has always worked and it is why having multiple IP's on the same subnet can result in confusing behavior.

The other thing, of course, is that the PVE gui may bind to specific interfaces on startup instead of "any". I can't look at my server right now to tell.

 

[argumentum]

All good. That did it
Am not familiar with Linux but in Windows I'd say listen to 0.0.0.0:8006 and it'd listen to anything on that port from any IP and I can have more than one nic on the same network ( x.x.x.n )
I believe it took effect after I unplugged the cable, so maybe the reboot wasn't needed.

Thanks a million !, it was diving me crazy

 

[BobhWasatch]

Having more than one NIC on the same network isn't a good idea for Windows either, although they do have differences in the way they handle that.

Even listening to 0.0.0:8006 won't really solve the problem because it is a bridge. Unplugging the cable doesn't make the bridge go away, and usually there are other things connected to the bridge (i.e. your VM's), so the kernel won't necessarily consider that address to be "down". Since both interfaces are on the same subnet they are "the same" to the kernel and it might choose to send packets out the "wrong" one.

Please mark the thread as "solved" by editing your first post.