Loosing network connection/settings after initial Pfsense configuration/setup
-
@stephenw10 yeah I mean, I literally had the same setup on Hyper v and it worked perfectly fine. And yes, I even turned off DHCP and install server 2022 as my dhcp server. Clients get IPs from the Server, I can see them in the pool but as soon I as go to LAN IP to for initial Pfsense configuration, everything breaks after saving.
I've also noticed, before even making any changes in the Pfsense, I can't ping the LAN network. So as I mentioned, I see the clients getting IP from the server, however, I can't ping them or I can ping the server from the clients. However, I can ping WAN IP from any device. Creating a rule to disable this also doesn't work either lol
-
To confirm though you are talking about the LAN setup screen in the setup wizard?
What happens if you don't use the wizard? You can just go to any other screen to escape it.
-
@stephenw10 yeah, the initial configuration when you log into pfSense for the first time.
So if I don't do the initial configuration, clients get the right IP address and all but I can't ping any of my devices in the lan network. Also creating rules and stuff doesn't work either. -
@greywolf81 said in Loosing network connection/settings after initial Pfsense configuration/setup:
So if I don't do the initial configuration, clients get the right IP address and all but I can't ping any of my devices in the lan network.
From other devices or from pfSense?
-
@stephenw10 so let me give an example:
WAN is on 192.168.1.1/24
LAN is on 10.0.0.1/24All the LAN devices get ip from 10.x network which is awesome, but none of them can ping each other (even the dhcp server itself). They can however ping 192.x network lol
As I mentioned earlier, creating rules to block traffic to WAN doesn't work either. I'm literally lost -
Mmm, this feels like a problem outside pfSense. Traffic between clients in the 10.0.0.0/24 subnet would not go through pfSense at all. So if those pings are failing it pretty much has to be some other issue.
-
@stephenw10 yeah most likely proxmox. Because I had this same computer, same NICs and same router with Hyper V and it worked perfectly fine.
-
How is it connected physically? Are there other VMs on the LAN bridge? Only other VMs?
-
@stephenw10 yeah how its connected and not other VMs.
-
If there's an external switch on the LAN side with the clients connected to that they should always be able to ping each other. If they cannot it's probably a bad subnet set somewhere. Or they aren't receiving an IP/subnet at all.
