Search results

Why reserve 3 nics for OPNsense? Or are you planning to use an interface for DMZ?

Well.....for starters you could do from your PVE host shell : # pveupdate # pveupgrade # reboot

Hi, I just ran into this error when doing a "pveupdate" and "pveupgrade" on my PVE host. I'm running kernel 6.2 for a few weeks now, before that I had kernel 5.15. No problems no errors, until now. What is the solution, I tried apt autoremove, apt full-upgrade, apt dist-upgrade. Still these...

... not sure what you mean?

(in your internal network) what device is your DNS server? I thought the Sophos vm? Anyway, put your DNS device ip address in /etc/resolv.conf You can also put 1.1.1.1 in there, but if Sophos handles all DNS resolving it makes no sense Why can vm's do a successfull DNS query, and the PVE host...

Bad UTP cables? Have you checked/replaced those already?

What kernel version do you run. I read somewhere in this forum that older kernel version have support for specific nics.

Maybe try kernel 6.2 instead of 5.x. Or vice versa.

In /etc/resolv.conf : If 172.16.16.11 is your PVE host and it does not have Unbound or other DNS services running, replace it with Sophos ip address (if that has DNS service running). Don't know if your Sophos vm is handling ALL network traffic from inside to the internet, in that case you can...

(on PVE host) what is the output of : ip route (on PVE host) what is the output of : cat /etc/resolv.conf

Oh and by the way..... Why use 2 nics? If you use the onboard nic as vmbr0 like you have already, then create some VLANs on vmbr0 and that's it. Your unifi machine will handle trunk ports and VLAN traffic.

https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_vlan

Much too complicated. With VLANs he will isolate the subnets. His unifi machine also has VLAN capability.

You have to create a VLAN(4) in PVE, check the wiki for howto. My config is a bit different with OVS. You can also install OVS in your PVE host, makes life a bit more easier to manage.

I use OpenVSwitch (OVS) in PVE. But I think you have to create a VLAN4 in PVE.

PVE host can only have 1 Gateway indeed. Where is your DMZ VLAN4 configured, in a switch, in your router?

vmbr4 bridge has no Gateway. 192.168.4.1 does not exist as Gateway.

- (from the Sophos vm) can you do: # dig debian.org - (from PVE host): # dig debian.org

Have you tried this: After Proxmox has finished installing, add these lines to '/etc/modules': vfio vfio_iommu_type1 vfio_pci vfio_virqfd - After changing anything modules related, you need to refresh your initramfs. On Proxmox VE this can be done by executing: # update-initramfs -u -k all...

Okay, I see. But what is his current config now, because he has posted several screenshots with different configs... The most recent is pfSense with 10.0.0.0 subnet on vmbr0.