Well that doesn’t really indicate any problems with the default gateway. My last bit of troubleshooting advice is to traceroute and see if packets get stuck at the router. And check the firewall logs in pfsense to see if you can find anything there.
Hopefully it ends up being a relatively painless problem to fix!
ok, if you’re fine with doing a little more troubleshooting, I have a few more things to try.
You said before that the systems are able to communicate with each other on the LAN network, just not connect out via WAN. Does this include the pfsense box? That is to say are you able to ping 10.10.10.1 (assuming that’s the IP of the Infra interface on pfsense) from one of you Ubuntu VM’s when it is on the Infra network? Also what is the output of both commands ip -br a and ip route? What I’m am curious about here is maybe the default gateway is not being correctly set when new devices connect to the pfsense. If this ends up being the case, it might be an issue with DHCP (or if you aren’t using DHCP then just the configuration on each Ubuntu VM). I suspect that Windows may be doing some fancy things to figure out on its own some network settings without them being explicitly set.
ok, so to recap just to make sure I have your setup correctly: You Have a Proxmox node with 3 VMs on it: Pfsense, an Ubuntu VM, and another Ubuntu VM. The Proxmox Node has a WAN network (likely a Linux Bridge type interface called vmbr0 or something similar), and a LAN network (another bridge, but with no associated physical interface on the Proxmox host). The last step can differ depending on how exactly you set it up, but the basic idea of having two “networks” is the same. EDIT: You will have two LAN networks as per your original post Your pfsense VM has three Network Devices under the hardware tab, one connected to your WAN network, and the other two connected to your LAN networks.
In Pfsense, you have the appropriate interfaces configured and firewall rules allowing devices on the LAN interface to connect out of the WAN interface (this step in particular has a lot of moving parts)
On each of your Ubuntu VMs, there is just a single Network Device under their hardware tabs, connected to the LAN network. (although right now you say they are connected to the WAN network so you can connect to them from other computers on your home network). Once this is set up correctly, move them back to the LAN network, and maybe set up a rule that allows connections from a single device on your home network. If allowing any device on your home network to connect to your homelab is what you want, then it doesn’t make too much sense having a firewall if you aren’t going to use it ;).
Does this match with your current setup?
Its hard to determine exactly where the issue is coming from, so some more information about the setup would be helpful.
In my experience, networking is very prone to small configuration errors, and setting up a homelab is going to force you to learn some great networking skills one way or another :)
Happy to hear it! Address conflicts are always a pain, I recently ran into an issue with my VPN to my home network, where my home network and the network I was on shared the same subnet and mask, so I had to specify some custom routes to make it work. Good network design is a must to try and mitigate these things!