Search results

LACP will not work for you in this setup, one Proxmox host LACP port plugged into an AP and the other plugged into a managed switch. LACP would require the 2 ports from the proxmox host to both be plugged into the managed switch AND the managed switch to be capable/setup with those receiving...

So if both of the cascaded routers are doing DHCP on the same 192.168.1.0/24 subnet and likely handing out differing DNS/gateways to DHCP clients on your local network, you will inevitably end up with issues. One or both of them may have already handed out 192.168.1.16 or .64 to another DHCP...

What network device (listed under Datacenter/ubuntu vm/hardware in the webgui) does the Ubuntu VM use? Is either or both of your routers (192.168.1.1 or .2) doing DHCP?

Agree @B.Otto, @TeenagedLime3 what is the output of cat /etc/hosts? This is the primary location the proxmox host expects to get WebGui traffic. Also, do you want proxmox always to use the VPN (change to gateway 192.168.1.2 under vmbr0) or not (change to gateway 192.168.1.1 under vmbr0)? As to...

Try auto lo iface lo inet loopback auto enp8s0 iface enp8s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.1.1/24 gateway 192.168.1.2 bridge-ports enp8s0 bridge-stp off bridge-fd 0 Then reboot or do a ifreload -a. You probably should...

On one of my nodes the upgrade/change to ifupdown2 from ifupdown left the networking service no longer enabled at boot. May not be the case with you, but sudo systemctl is-enabled networking should return enabled. If not, sudo systemctl enable networking fixed it for me.

could these 2 opnsense issues be similar? Post in thread 'OPNsense VM - BSD panic' https://forum.proxmox.com/threads/opnsense-vm-bsd-panic.123567/post-538441

@Brandon168 following this post. I have set up a couple 22.03 OpenWRT LXC to see if they might be a more efficient and performant option as my home network router/firewall. it’s early days, but can do you have resources on mwan3 for dual wan setup you can point me toward. I plan to try and...

Use the Proxmox VE No-Subscription Repository like the rest of us to keep up to date. You can disable the Enterprise and add/enable the No-Subscription repositories easily through the webGUI.

to be clear, do your host have networks interfaces above and beyond the 2 10G? will more than 1 proxmox guest will be utilizing the 10g ports per host? When utilizing Virtio and multi-qeue with or without jumbo frames some folks have basically saturated a 10g link with both basic Linux...

OPNsense 23.1 with q35 and efidisk boots fine for me.

@neoplayer Does your proxmox host match up with those discussed here? https://forums.servethehome.com/index.php?threads/jasper-lake-proxmox-kvm-qemu-vm-guest-stability.38824/

Looks good.

Well that tutorial is for hyper-v so a little bit different. What are the specs of your proxmox host? Obviously, many of us are running opnsense VMs and pfsense vms , I have been for a couple of years and just did a reinstall for 23.1 to confirm working before I updated my main opnsense router...

Does it boot with CPU host and removing all the other flags ... flags=+pcid;+spec-ctrl;+ssbd And without passthrough.

@tmbiv56 think of each Linux bridge as virtual managed switch with unlimited ports. The IP address and gateway directly assigned to it are for the Proxmox host connection to that virtual switch not the vm/LXC VM/LXC can all attach to that same virtual switch and comunicate with the Proxmox...

Yeah removing the linux bridges from proxmox altogether was not the right direction. try the below for your /etc/network/interfaces: auto lo iface lo inet loopback auto enp1s0 iface enp1s0 inet manual auto vmbr0 iface enp1s0 inet static address 192.168.999.20/24 gateway 192.168.999.1...

as long as the proxmox host default CIDR and gateway have been moved off of vmbr0 then yes it can be removed without causing issues. if not then proxmox internet access and your webgui access will likely be impacted.

So gigabit should be no problem and would not be worth any of the passthrough hassle for me. Even 10g I use virtual without issue and good throughput, your CPU starts to come into play there if marginal. Always use paravirtualized Virtio as the network device and not e1000.

Yes that is a good way to think about a dedicated linux bridge/Vlan. A separate virtual switch with basically unlimited ports. If you don't attach an egress (to either WAN or some other external physical/virtual network) or give the Proxmox host an IP on the bridge/vlan then the guest attached...