VM network problems

kcallis

Active Member
Apr 5, 2018
48
2
28
57
I am running openvswitch on my Proxmox 6.1 server. I installed pfSense as a VM and for the most part it running well. Recently, I tried to install as a VM, OpenMediaVault, which seemed to have problems when it tried to connect repository mirrors. I assumed that there might have been a problem with the ISO image, so I switched to a lxc template Turnkey Linux Fileserver. When I create a VM or container, in the network section, I assign to a VLAN. When the VM or container spins up, it has a DHCP address and it able to connect to local hosts as well as external hosts.

The problem is that when I attempt to for instance do a *apt update* or *apt upgrade* then we have problems. As soon as there is connectivity to mirror, it would seem that the host cannot resolve the name, and it slows down significantly and fails to deal with the site regardless of whether it is a http, https, ftp, or rsync site. If I ping or traceroute the host name, there is no problems. If I am on my laptop or desktop machine, and try to do the same exercise, I have no problems. The machines are in the same VLAN as the VM, but work.

An associate of mine said something about promiscuous mode, which I don't know anything about. What do I know is that although I have VM and containers running, they are not very functional, and I need to understand why. For instance, I did try to spin up OpenMediaVault, but I was not able to update or even connect to the repositories. So that makes the VM useless. Any pointers would be greatly appreciated!
 
Hi,

Is there a reason why you use OpenVswitch?
I would use the Linux Network model it is more stable and for the most use case, it is enough.
 
Because at the work site, openvswitch is the daily driver. I have virtualized pfSense singing nicely on Proxmox 6, but there is some disconnect with the other VM/containers. I found out that I missed a option in pfSense that was causing all of this issue with the other VM/containers. As soon as I check the option and rebooted, all of my issues when away! So it was not an openvswitch nor Proxmox, but instead with a VM...