Search results

Happy new year. you do not have to designate the subnet on vmbr1 with the address 10.0.5.0/24 line. Unless you want to have the Proxmox node web gui available to your proxmox guest using vmbr1, I would remove that line, change iface vmbr1 inet static to iface vmbr1 inet manual, and then do a...

@alexskysilk nailed it up above then crossed it out from their second post. Happy new year and glad it is working now.

No real reason to hide internal private addresses unless those are public IPs. Seeing your /etc/network/interfaces files would help garner better specific suggestions. can be done differently, dependent on your gateway/router...

1. https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_network_configuration good place to start. 2. Either by proxmox node firewall rules dropping traffic to port 8006 on 192.168.3.1 or maybe just removing the 192.168.3.1 address from that Linux bridge all-together as 2 options 3...

Some context for anyone else seeing this for the first time. https://forum.proxmox.com/threads/set-proxmox-cluster-on-seperate-nic.120334/

Nothing looks off with your proxmox node interfaces file. I assume the 10.10.1.10 interfaces file shown and the 10.10.1.30 file are exactly the same? So on the juniper switch does the LACP bond you created there for the VM network also use the default vlan? I see you have set the mtu to 9192...

Just trying to understand your network topology. so you have 2 same computers both using eno4 for this cluster network (10.10.1.10 and 10.10.1.30) and a third computer using enp65s0f1np1 (10.10.1.20). All 3 of these nics plug into your juniper - how are these 3 juniper switch ports configured...

Any vlans or a Managed switch used here?

As stated above you need change your /etc/apt/sources.list file. yoi can do that from the CLI as linked above or since pve 7 you can also disable the enterprise repository and add the non-enterprise repository from the web-gui...

You seem to be on Proxmox 7.2 not the latest 7.3, maybe update your base install first then try for the new kernel. try a apt update && apt full-upgrade first before apt install pve-kernel-6.1 .

Edit your original First post. Click the "No Prefix" adjacent the thread title and select "solved from the drop-down menu/popup. Save the edit.

How about the other direction? Can the default gateway or anything in the 192.168.0.0 subnet ping 192.168.100.16? What are you using as a router? Does that router know, sometimes requires static routes, where and what interface to use to send data, DNS/web, back to the 192.168.0.0 subnet?

What does your full /etc/network/interfaces file look like? Will help answer questions such as what is the gateway, how many other IP's assigned to proxmox and does proxmox have more than 1 IP on the 10.10.10.0/24 subnet.

By default you can only have one gateway for the proxmox host. You should consider one of the below for each different Linux bridge/subnet you create that you would like to have internet access for the guest VM/LXC. Routed Configuration Masquerading (NAT) with iptables

many ways to go about this, BTW it appears you want redundancy so if your switch can handle it consider creating an LACP bond at switch port 3/4 and on proxmox host ports enp1s0/enp2s0 then use that bond# in vmbr0 making your /etc/network/interfaces file simpler (no need for any vmbr1 then). But...

Mainly wanted the option to do PCI-e passthrough.

OPNsense 22.7 vm working well for me. Uses FreeBSD 13.1 as a base and can use q35.

Jumbo frames are typically more trouble than they are worth particularly at 10g or less. Typically only bother with them for storage only networks. jumbo frames intermittently and seemingly randomly can screw up some normal background network traffic, from mDNS to ssh and others. Switches and...

seems to be working as I would expect, might be a misunderstanding on your part on how tagged and untagged traffic should work from the perspective of your switch port. Current setup on switch port 4: PVID 100, tagged 1, 101 plugged into Proxmox. All untagged network packets from proxmox and a...

This may not be the only issue but could be causing other problems at some time, on the switch, unless I am mistaken you should not have ant most 1 untagged vlan per switch port. You can have multiple tagged vlans per switchport though. 1. when a network Packet arrives at the switch port...