Search results

Is there a firewall blocking ping traffic? In my homelab the above example works, they can indeed "ping each other".

I was wondering why you did not create a fresh new Ubuntu container earlier. Is this "faulty" container so important for you? Does it run special software? - Perhaps your existing Ubuntu lxc template has an error in it. Delete this template and download a new fresh copy and re-deploy it.

Have you created a new Ubuntu container (on pve3, same Ubuntu version) to see if this has the same problem(s) ? Can pve3 host itself ping 1.1.1.1 without issues?

"try to change the ip address, before it was 10.73.42.18:8006 now it is 10.73.42.99:8006" - What was the reason you changed the IP address? - I think you locked yourself out because datacenters have firewall rules based on what they give you (10.73.42.18) - Unclear how you made the screenshots...

- is this a home lab setup, or are you running Proxmox at an ISP/datacenter? - To change the IP address you can simply edit and save the file # /etc/network/interfaces Reboot the server afterwards, or do a # sudo systemctl restart networking

- what is the purpose of the "iptables" line at the bottom of /etc/network/interfaces? You have a private ip network, not a public ip. - in the last screenshot your vmbr0 bridge is empty. There should be an ip address to access the PVE webgui.

- Can the two containers ping the DHCP server? - are you using DHCP reservation, in that case check if the MAC addresses are correct

What if you virtualise a router like pfSense/OPNsense and run it as a vm on your Proxmox host? Is that a few bottlenecks less in the networking chain for you?

Not sure configuring multiple gateways on Proxmox host is THE way to go. (I always hear people saying in this forum that only 1 gateway is allowed). You now have configured Proxmox as a "router" with net.ipv4.ip_forward=1 That solution is what you asked for in your startpost, so you solved your...

I think the website wrote that you can delete the original vmbr0 Linux Bridge and create the new OVS Bridge. My personal PVE host #1 (I have 3) has an OVS Bridge with several VLANs (IntPorts). You can set the IP address for management on the OVS Bridge, or....... you can give an IntPort (VLAN)...

https://www.networkshinobi.com/proxmox-ve-with-open-vswitch/ This website helped me a lot with OVS.

Did you do a "systemctl restart networking" ? Or via the webgui "Apply Configuration" ?

Remove the quotes '10.10.0.0/24' Should be 10.10.0.0/24

Maybe clear the ARP cache in the FritzBox. DNS name with old MAC address is probably still in his table.

Makes sense because only vmbr0 has a Gateway. I think you need to install a virtual router, like pfSense/OPNsense/IPFire on your PVE host. Sorry, I totally missed the last two NAT rules....

Again, remove the line dns-nameservers in /etc/network/interfaces. Your /etc/resolv.conf can look something like this (max 3 DNS servers): search whateverdomainyouhave nameserver 192.168.1.99 nameserver 192.168.1.101 nameserver 9.9.9.9

I would remove "dns-nameservers" in your /etc/network/interfaces file. And add a valid DNS server in "/etc/resolv.conf". I notice two DNS servers in your screenshots, 192.168.1.99 and 192.168.1.101. Is that correct?

Please share your output of : # pveversion -v # cat /etc/network/interfaces

100% packet loss when pinging google.com and proxmox.com is not what I would define as "DNS resolution works fine"....... From the PVE host what is the result of: # dig google.com # dig proxmox.com

Do you really need jumbo frames (mtu 9216) ? What is the result when you use standard MTU size, or delete the mtu lines in your config?