Search results

Are you using vmbr0 or vmbr0.4 with the VM’s/lxc?

I have been unsuccessful getting ipv4 multicast to cross my linux bridges to my ruckus icx7150 switch, I can get ipv6 multicast. Some folks have no issue ... others no luck with multicast. Not sure what the magic combination is.

Out of curiousity where or how exactly are you changing things in the VM? AS you figured out Virtio should almost always be used instead of e1000

@arminanton not sure that pi setup is the way to go with ifupdown2 and proxmox. Not part of your question, but Proxmox should have a static address somewhere so that can reliably get to it from the network. you may already have this if not all of /etc/network/interfaces is copied over. Couple...

I can't help further on OVS as I have only used it briefly, sorry. Let me preface this next question by saying that I understand the innate desire to optimize and squeeze out every bit of speed possible. I subconsciously feel the same way. Specifically on VXLAN: What are you transferring...

You consider using the RSTP Loop Setup or Broadcast Setup from that page and creating vlans on top of that? also consider @spirit vxlan ring network recommendation as well as a Batman ring networking from the thread below...

It's not yet implemented from the gui, but is doable today and can be automated with pbs-client for your disaster-recovery. https://forum.proxmox.com/threads/backup-pve-using-pbs.80045/post-355138

Do you really need a crossover lan cable? Which of the 2 is connected to the internet? Do you also have an ISP router between the internet and either Pop OS and/or Proxmox node? You can set up a router/firewall VM on proxmox and connect that to WAN and put both Pop OS and proxmox behind that...

https://forum.proxmox.com/threads/backup-the-proxmox-ve-host.115485/#post-499365

I 100% agree.

Glad it’s working. Not the first time I’ve heard a reboot of either Proxmox or the managed switch getting things working as expected when changes correctly made do not work on the fly.

I See nothing wrong in the Proxmox setup or in the parts of the pfSense setup shown. can you ping the pfSense gateway address for either vlans 20 or 30 from the switch? Have you double checked that the switch is allowing connected devices in via untagged ports as appropriate for vlan 20 & 30?

Show us your /etc/network/interfaces from the the proxmox host?

Sorry Also meant to ask about meant to about the physical Windows PC and what it connects to. plugs into the switch? - what is this switch port config - tagged/untagged vlans? Is the dell server the proxmox node or the window PC? Switch Port 5 is tagged 50 - also tagged 75? - untagged or...

Sometimes it is that secure boot needs to be disabled in the proxmox VM uefi bios. At least that was the issue for me and others, if everything else checks out. https://forum.proxmox.com/threads/failing-to-boot-home-assistant-qcow2-image-disk-uefi-access-denied.99892/#post-431382...

More likely the port configuration on your switch is the real issue. What is the physical switch vlan config on the following ports: 1. connected to your physical Windows VM 2. connected to your proxmox host eno2 3. connected to your internet router

Since you made vmbr1 vlan-aware you can now think of vmbr1 as a separate virtual managed switch with unlimited ports. You control the port your windows VM connects to on vmbr1 by adding or removing that vlan-tag at the proxmox host-Windows VM-network device-vlan_tag level. Putting nothing there...

How is the physical Windows PC connected ... Wired to the internet router, wired to switch, or wired to proxmox? From the proxmox host what is eno2 physically wired/connected to? You could try starting the Windows VM with those setting I recommended in place and see if pulls an IP from pfsense.

Did you reboot the desktop (this is a windows VM right?) instead of just waiting? Something seems off with connectivity in pfsense LAN which you stated was on vmbr1. what do the network devices look like in the proxmox host for the pfsense VM? What device is 192.168.1.1 is that your internet...

So what does your /etc/network/interfaces look like? First I would make vmbr1 vlan-aware (check box when you edit vmbr1). After that, you should be able to edit the windows VM-hardware--network device and use vmbr1 as bridge with vlan tag 50 to connect to pfsense vlan50. You may need to restart...