Moved to new house
-
at my previous house I had the network setup and operational.
I have a combination of DIY/open source devices:
AWOW mini pc 6GB DDR4 ram, 218gbSSD, Intel Celeron J3455 as the PfSense box
raspberry pi 4 (4GB) as the Unify Controller
3 of the unify mini switches to distribute lan through house
unify AP Pro - segmented into two different WiFi's on separate VLANSnetwork is setup as follows:
lan / admin - 10.27.27.1/24
iot - 10.27.20.1 /24
rapberry pi - 10.27.30.1/24
humans - 10.27.50.1 /24to access my pfsense instance I could go to 10.27.27.1 when I'm on lan or 10.27.50.1 when I'm on humans.
to access my unify controller I go to 10.27.27.57 only accessible from LAN/admin.
I have other raspberry pis and they're segmented to their own VLAN. I did the routing and rules for all of the devices, it was fully operational.Here is where my problems start. I was under the impression, that all I had to do was plug in a WAN cable into my pfsense box, and the network at the new house would work the same as it did at the old one. my how I was mistaken. :(
When I plug in the WAN cable from my ISP modem I can access the internet, but get quarter speed of what I'm paying, not worried about the speed atm. however if I plug in directly into the firewall I my ip address is on the 10.27.27.x subdomain. if I plug into certain ports on my mini unify switches I get the 10.27.30.x subnet, because that's how they were setup before, and one or two of the ports are on the 10.27.50.x subnet. something weird I noticed, some of the ports were on the 192.168.xxx.xx subdomain. see figure below
192.168.1.x (ISP Modem) --> 10.27.27.x (PfSense)--> when plugged into pfsense box
192.168.1.x (ISP Modem) --> 10.27.27.x (PfSense) -->10.27.30.x (mUnifySwitch)-->when plugged into certain mini switch ports
192.168.1.x (ISP Modem) --> 10.27.27.x (PfSense) -->10.27.30.x (mUnifySwitch) -->when plugged into certain mini switch ports
192.168.1.x (ISP Modem) --> 10.27.27.x (PfSense) -->192.168.2xx.x (mUnifySwitch) -->when plugged into certain m switch ports
192.168.1.x (ISP Modem) --> 10.27.27.x (PfSense) -->10.27.50.x (mUnifySwitch) -->169.x.x.x (UnifyAP)-->when connected to AP with no internet
I had the AP plugged into the 10.27.50.x port on the old network and everything worked fine. I tried doing the same today, and the IP address reads 169.x.x.x. and no internet access when connected to the AP.
Another issue, I cannot access the firewall, unify controller, or my raspberry pis, regardless of which VLAN I'm on.
I have tried plugging the AP into all the ports on the different switches and cannot get internet access when connected, when I try to connect a to the AP from a phone it fails saying "Fail to obtain IP."
When connected to the PfSense box or unify mini switch I was not able to get ping either from the PfSense box to my pc or from pc to pfsense box.
I'm open to any ideas on how I could regain access to my systems, I have command line access to the PfSense box, but I never figured out how to get the RasPi4 Unify Controller to output to display (I tried enabling the different hot plug and HDMI comments in the config file).
tldr;
Moved to new house and lost access to pfsense and unify controller. open to ideas on how to regain access -
Presumably you can still access pfSense if you are connected directly to it?
I would suggest that something in the network has lost it's config and reverted to some prior config or it's default config. If the 192.168.2xx.x subnet is not configured anywhere in pfSense then it's probably whatever device is now handing out IPs in the subnet unexpectedly.
Steve
-
@stephenw10 no I cannot. I have no access to it.
In the mean time pfsense is no longer getting a WAN IP -
Then it's probably not booting correctly. Connect to the console directly and see what's happening.
