Search results

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...

Does pfsense have vlan50 set up, using vtnet# was created, with vmbr0 as parent? If so does pfsense have a DHCP server for the proposed 192.168.75.0/24 set up for vlan50?

From the one full example I can find of using broadcast in the proxmox Docs: https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Command-Line looks like you might want to try just slaves and not bond-slaves; auto bond0 iface bond0 inet manual slaves enp2s0 enp3s0 enp4s0 enp5s0...

Definitely have seen, and personally experienced, some inconsistencies for ifupdown to ifupdown2 upgrades for those coming from older versions of PVE. New PVE 7.* installs not so much. Glad you have it sorted.

So, if you edit /etc/network/interfaces directly and delete whole vmbr2 section, then change vmbr1.2 section to the below followed by a reboot, does that allow you to ping 10.0.1.7 from the switch or 10.0.1.1 gateway? auto vmbr1.2 iface vmbr1.2 inet static address 10.0.1.7/24...

Assuming enp2s0f* is the new correct nic names and enp1s0f* is the old no longer valid Nic names, edit /etc/network/interfaces and erase sections using the old name. example of what to look for to delete below: auto enp1s0f1 iface enp1s0f1 inet manual To be sure you might want to post can post...

What does the /etc/network/interfaces file look like? I suspect you might inadvertently be mixing the 2 examples below from this link (VLAN 802.1Q), but I can't tell from the GUI pic- Example: Use VLAN 5 for the Proxmox VE management IP with traditional Linux bridge Example: Use VLAN 5 for the...

In your final state do you intend to use both eno1 and enp10s0 ports or only enp10s0 for both internet (wan) and internal networks (lan)? specifically, to put the proxmox Management IP on vlan2, using a VLAN aware linux bridge (vmbr1), you would move the CIDR 10.0.1.7/24 and gateway 10.0.1.1...

Did you try: pre-up ethtool -G <interface> tx 4096 rx 4096?