Search results

You could try pass through to pfsense that way only one OS needs to recognise it.

The GUI should be available on any bridge with a IP address set and NIC/VLAN connected Set via Proxmox -> Datacenter -> <pve> -> Network -> vmbr2 -> Edit -> Set IPv4/CIDR & Bridge ports To access the GUI you then need to Connect to the specified NIC/Vlan At the specified Hypervisor IP...

Some NIC hardware offloading is best disabled but not all. I did not say it could not be done with a virtual NIC in Proxmox, I said it was simpler if Proxmox is not involved at all. With a virtual NIC the configuration must be correct in both pfsense and Proxmox. Indeed there are multiple ways...

Did some more debugging, and found a better solution systemctl restart networking The system must have been left in a weird state after the update from Proxmox 7.0 to 7.1 In more detail Having a fixed DHCP mapping in pfsense masked the problem and achieve apparently normal function. Removing...

Connect a physical screen to your Proxmox server Login to the console then run these two commands ip a && ip r cat /etc/network/interfaces If the issue is not clear you may have to post a photo of the screen until you have remote console access

The best set up probably depends on other details of your application. I don't have a network of Proxmox servers so live migration is not an option in my use case. I pass through all the NIC pfsense uses. The advantages of doing so are: Minimize the attack surface of my router Allow use of all...

Does your router run as a VM on Proxmox or is it sometimes not accessible when Proxmox boots.

Agree The VM's like 3cx & pfsense have the option to readily backup / restore their configuration. Proxmox can easily be used to take a snapshot or clone a VM Both options minimize the risks / decreasing the cost of doing and possibly reverting updates. Proxmox host has neither of these and...

When did it stop working? If on upgrade what was the last version which worked for you? Have you tried any other versions? Can you ping your gateway from Proxmox? Is your router running as a VM on this Proxmox hypervisor?

Does pfsense run in a VM on Proxmox? Is pfsense running when that Proxmox starts? That configuration did not work for me with Proxmox v7.1. See https://forum.proxmox.com/threads/host-network-access-lost-after-proxmox-upgrade-7-0-to-7-1-router-vm-with-pass-through-nic.100091/

I suspect you have encountered the same bug / limitation as me. Proxmox v7.1 behaves very badly if started without external network services (in my case a Proxmox VM runs the router providing DHCP, DNS, route to Internet). For some reason adding a manual DHCP entry for Proxmox in the VM router...

Updated to current no subscription 7.1 version Kernel Linux 5.13.19-2-pve #1 SMP PVE 5.13.19-4 Manager pve-manager/7.1-8 Summary -> no change that I could detect. with DHCP server entry setting IPv4 address based on vmbr0 / enp2s0 mac address (as well as the fixed IPv4 specified in Proxmox)...

ZFS using 50% of available ram?? If you have ZFS storage, what does arc_summary show?

Against my better judgment I tried it too. The brief summary: Proxmox hypervisor still needs the same work around to get outgoing network access but behaves subtlety different to other fix attempts. In more detail. With the work around in place I updated to the current no subscription version...

Yep, that's what I thought I had done too until I discovered the mac address was for the NIC not the bridge. No, access to the Proxmox GUI was not lost. What did happen is Proxmox lost access to the network (as a result ping, chrony, program update all failed). Sounds reasonable, the fix is...

Where your router is a VM running on a Proxmox hypervisor, so when Proxmox boots there is not route to the Internet, no DHCP server, and no DNS. In Proxmox 7.0 Set the IP address of Proxmox in Proxmox. Nothing else needs to by done. In Proxmox 7.1 Leave the IP address of Proxmox set in...

Agree Pass through complicated tracking the bug but I believe turned out not to be the cause (as did the current complexity in rolling back the kernel). The root cause is how 7.1 behaves when no DHCP / DNS /external route is available when Proxmox boots. The work around is to add a second...

To update / answer my own questions The following were tried but did not help Restart Proxmox with only single dedicated NIC connected (LAN5) then adding other Ethernet connections after Host & all VM finished starting up. Renewing the network connections in Proxmox by pve -> Network -> edit...

Should be disabled virtIO (paravirtualised) works fine for me I assume you have created a bridge to connect your NIC to the virtual machines virtIO How many physical NIC to you have? A separate one for Wan and Lan? Are you using Vlans at the moment? What version of pfsense and Proxmox are you...

Statically excluding NICs the Proxmox hypervisor will not have access to must be possible because that is what appears to happen dynamically in Kernel Version: Linux 5.13.19-1-pve #1 SMP PVE 5.13.19-3 PVE Manager Version: pve-manager/7.1-6 Although it is not really a solution to the current...