[SOLVED] Network ok, but all VM with no access

[life.tripod]

I have Proxmox installed on a SuperMicro H12SSL-i and a Epyc 7542 without problems. I can reach the internet and connect to the WebGui without any issues.

However, when I create a VM, for example, Truen Nas Scale, or Ubuntu Server, the VM cannot access the internet.
In TrueNas Scale i get this error message: The Web interface could not be accessed. Please check your network configuration, while in Ubuntu there is simply no internet.

The motherboard has 2 rj45 1Gb, and i installed 1x10Gb PCIe NIC

Below is what shows in Proxmox



What changes do I need to make to allow VMs to access the internet?

 

[Dunuin]

You shouldn't use the same IP on two interfaces and not two IPs of the same subnet on the same host.

 

[life.tripod]

I have tried to change the IP of vmbr0 to a different one (ex 192.168.1.250), but i am still not able to get the VMs to access the internet

 

[Dunuin]

192.168.1.250

Still the same subnet which should be avoided as it might confuse the routing. Try something else like 192.168.2.2/24 or just leave it empty.

I would also check if your bond is working. For example for a LACP you need to configure your managed switch properly or it won't work.

 

[life.tripod]

no link aggregator.

Also, I left the vmbr empty and it is still not working.

any ideas why?

 

[bobmc]

I would advise that you simplify things to begin with and move onto more involved setups later. Forget about bonded and/or multiple interfaces for now - there's very little advantage in a simple home lab setup anyway.

It looks like you're on a regulation home lan with an ISP modem/router on 192.168.1.1 - probably acting as internet gateway and providing DHCP and DNS services?

That being the case and seeing as you have established that enp134s0 is functioning with an ip address of 192.168.1.241, I would recommend that you delete vmbr0 and recreate it using enp134s0, move the 192.168.1.241/24 IP onto vmbr0 and also the 192.168.1.1 gateway as well. Apply configuration and confirm you a) still have web access and b) the host can reach the internet. Once you have done that, create a VM with a network adapter on vmbr0, if using DHCP it should get a lease, if manual give it a 192.168.1.x IP and use 192.168.1.1 for gateway and dns.

 

[life.tripod]

thanks

I tried, and i got this errors:

I would advise that you simplify things to begin with and move onto more involved setups later. Forget about bonded and/or multiple interfaces for now - there's very little advantage in a simple home lab setup anyway.

It looks like you're on a regulation home lan with an ISP modem/router on 192.168.1.1 - probably acting as internet gateway and providing DHCP and DNS services?

That being the case and seeing as you have established that enp134s0 is functioning with an ip address of 192.168.1.241, I would recommend that you delete vmbr0 and recreate it using enp134s0, move the 192.168.1.241/24 IP onto vmbr0 and also the 192.168.1.1 gateway as well. Apply configuration and confirm you a) still have web access and b) the host can reach the internet. Once you have done that, create a VM with a network adapter on vmbr0, if using DHCP it should get a lease, if manual give it a 192.168.1.x IP and use 192.168.1.1 for gateway and dns.

thanks, I tried, but i got this error:

iface enp134s0 - ip address can't be set on interface if bridged in vmbr0 (500)

Update: I understood the error and corrected it. With your guidance, I was able to get everything working, thank you!

 

[Dunuin]

iface enp134s0 - ip address can't be set on interface if bridged in vmbr0 (500)

Bobmc meant the IP and gateway should be on your vmbr0 with no IP and gateway on enp134s0. And enp134s0 as port/slave of vmbr0.

 

[life.tripod]

Bobmc meant the IP and gateway should be on your vmbr0 with no IP and gateway on enp134s0. And enp134s0 as port/slave of vmbr0.

Yeah, thanks Dunuin for your patience, everything is now working!