LAN2 Cannot Connect to main LAN
-
I checked for a device getting a DHCP address, rather than static mappings - and it's the same - LAN2 DHCP gives a 255.0.0.0 subnet mask but simply plugging the cable from LAN2 back to LAN the assignments are normal - i.e. 255.255.255.0
There doesn't seem to be anywhere in pfSense where this could be going wrong - the DHCP settings pick up the correct range of possible IPs based on the interface settings so it appears to have the correct picture of what LAN2 looks like.
Other than deleting the LAN2 interface completely and re-creating it, does anybody have any other suggestions ?
Thanks
-
Hi NogBTB,
Smart thought - bizarre result!
I cable connected my PC directly to the LAN2 interface and it gives me:
-
a LAN address of 192.168.1.20 NOT the expected LAN2 address of 192.168.2.20
-
Subnet mask 255.255.255.0
I originally had the static mappings on the LAN DHCP, and duplicated them to LAN2 (changing x.x1.x to x.x.2.x) so these devices (MACs) are defined in static mappings on both LAN and LAN2.
I am guessing this is the root cause, and in a steady state I could remove them from LAN once LAN2 is actually working, but should a PC connected to LAN2 be served an LAN IP and/or is there a way to stop it happening while keeping the fallback mappings on the LAN DHCP ?
Thanks
-
-
Post a copy of the following:-
-
An ipconfig /all when directly connected to LAN2
-
An arp -a when directly connected to LAN2
-
Status-> Interfaces LAN & LAN2.
-
-
Will do, thanks. Just need a moment to let things settle....
-
Current status:
-
I removed the "duplicate" static mappings so now LAN only has static IPs defined for the wired devices, and LAN2 only has static mappings for the WiFi devices.
-
For my workstation, I removed all static mappings so it is just picku\ing up DHCP settings.
-
LAN2 is defined as 192.168.2.0/25 - I only did this to force a change to be saved to see if it would solve the 255.0.0.0 issue
-
I rebooted pfSense
-
I double-checked the workstation is using DCHP - when the pfSense box / AP went wonky last night I had a fixed IP which may have caused the situation earlier today, not sure of anything anymore!
Now, with workstation connected directly to LAN2, I am seeing an x.x.2.x DHCP assigned IP - as expected - but the subnet mask is STILL 255.0.0.0
Attached items as requested:
- ipconfig /all
- arp -a
- pfSense Status > Interfaces
-
-
192.168.2.1 00-0d-b9-50-e9-82 dynamic
hmmm your getting DHCP from the pfSense LAN2 interface, thats why I asked for the arp -a, to tie in the DHCP server IP and the MAC address.
The subnet mask is now /25 rather than /24.
Can you post a screenshot from the LAN2 config and the DHCP settings for LAN2.
-
Thanks - here you go...
-
https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.txt
https://tools.ietf.org/html/rfc2132
Remove DHCP option 1 and try again.
No need to go anywhere near the options config for standard users.
-
You've got to be kidding! That just looked like a default panel with nothing saved - pfSense usually adds rows of saved items in a table underneath.
Anyway, I needed to add another row to get a delete option but when i did, the DHCP assigned mask is immediately the expected 255.255.255.0 and from my x.x.2.x workstation I can access the NAS webgui on x.x.1.x
So grateful - many, many thanks.
-
You can just blank the entry :)
-
@IanHK said in LAN2 Cannot Connect to main LAN:
You've got to be kidding! That just looked like a default panel with nothing saved - pfSense usually adds rows of saved items in a table underneath.
Anyway, I needed to add another row to get a delete option but when i did, the DHCP assigned mask is immediately the expected 255.255.255.0 and from my x.x.2.x workstation I can access the NAS webgui on x.x.1.x
So grateful - many, many thanks.
You should be getting a mask of 255.255.255.128 if you have a /25 mask set.
-
Yes, that's what I get with the /25 setting. Thanks again.
