PFSENSE receiving connection but unable to share over LAN
-
@stephenw10 I've just changed the IP on LAN to 192.168.2.1 (from 192.168.1.1) and as a result the subnet changed to 255.255.0.0.
IPConfig /all is now showing only IPv6 is available and I'm unable to access the interface so it looks like I'm back to square one in factory resetting it again ha.
Can't confirm about the outbound NAT rule as I haven't touched anything to do with that - the R7800 is on 255.255.255.0 and has wireless enabled although I'm not sure how the wifi being enabled can impact this as it'd be the only access point/router in the house that has it
-
It could affect it if the client you are testing from is connected both by Ethernet to pfSense and by wifi to the other router.
The subnet should still be 255.255.255.0 (/24).
255.255.0.0 (/16) contains both 192.168.2.1 and 192.168.1.1 so a conflict could still happen.If you changed the pfSense LAN IP/subnet did you also change the DHCP server range to match?
Steve
-
@stephenw10 I had only changed the IP on LAN to 192.168.2.1 and that's all - I presumed doing that changes the subnet automatically to 255.255.0.0 for whatever reason and that's probably where it's all gone wrong.
I hadn't touched the DHCP server range - not entirely sure what I'm looking for in that regard!
The only time I had it semi-functional was when it was backwards, and PFSENSE sat behind the router in LAN 1 which also supplied an internet connection through LAN. I may be attempting a lot of needless troubleshooting as I don't do networking much.
Will factory reset it again when I get the chance, 7th time's the charm!
-
If you change the LAN IP in pfSense the subnet should remain the same at /24.
So there IP will be 192.168.2.1/24. That will not conflict with an existing 192.168.1.0/24 subnet.But after changing that the DHCP lease would have to change to match it.
Go to Services > DHCP Server > LAN and set a lease range inside the new subnet like 192.168.2.100 to 192.168.2.245.Steve
-
@stephenw10 Hi Steve, still appreciating the replies!
I've kept it simple, removed the R7800 completely out of the equation and currently have PFSENSE as the router now with connectivity on LAN.
I'm trying to now get connectivity on OPT1/2/3 which doesn't seem to be happening currently, as I would like to use OPT1 for an access point, and OPT2/3 for switches.
I could also use R7800 in LAN as an access point but I'm reluctant as I can't be sure that'll work straight off the bat.
WAN is set to 192.168.1.2/24
LAN is 192.168.1.1/24
OP1/2/3 haven't been given an IP, do I have to do this manually in order for it to work? -
@tommyp1894 said in PFSENSE receiving connection but unable to share over LAN:
WAN is set to 192.168.1.2/24
LAN is 192.168.1.1/24Those are conflicting is that a typo?
Both those interfaces are using the same subnet, 192.168.1.0/24. If the WAN must use a private IP like that the LAN needs to be something different like 192.168.2.1/24.Yes, to use other interfaces you must enable them and set a static IP in a different subnet. And enable the dhcp service on them if you need it.
https://docs.netgate.com/pfsense/en/latest/interfaces/configure.htmlSteve
-
@stephenw10 No typo! Seems to be working though and I've created a backup just in case - I've also connected LAN 1 to an access point and it looks like it's in business which is great, a lot more progress than I had before.
Just as I'm about to submit this, I've reset the PFSENSE and have been given a WAN IP by my ISP as it's PPPoE, so should there be any need to amend that part now it's changed?
I'll enable OPT1/2/3 and give them a go now!
EDIT: Enabled OPT1 and gave it an IP, set the range from 192.168.1.100 to 192.168.1.254. Didn't revert to HTTP after a quick Google, and there's no physical connection when I connect it to a laptop. Any idea why this may be?
-
Ah, great if you have a public IP on WAN that solves that issue.
You need to use a different subnet on the OPT interfaces. You are already using 192.168.1.0/24 on LAN so you need to set something on OPT1. For example: 192.168.100.1/24. Then use range 192.168.100.100 to 192.168.100.254
Steve
-
@stephenw10 I've done just (?) that and stuck each OPT1/2/3 as 192.168.2.1, 192.168.3.1, 192.168.4.1, respectively so I hope that works as I'm unfamiliar with subnets!
I can ping 8.8.8.8 through the GUI when using any OPT, but it's not providing anything through the physical cable. My PC and Laptop are both physically connected to the T730 right now and have detected a network but aren't receiving a connection.
If I can resolve this then I believe this is the final hurdle in terms of basic setup!
-
Those IPs are good assuming the subnet size is /24 on each.
So a client connected to each is not receiving an IP via DHCP?
You have enabled dhcp on each of those interfaces though? For example in Services > DHCP Server > OPT1?
Check the dhcp logs for any errors trying to start the service. Check it is running in Status > Services.
-
@stephenw10 They're each running a static IP instead of DHCP, is this where it's all going wrong do you reckon? I hadn't checked if devices are receiving an IP via physical connection.
I'll change one tomorrow morning to DHCP and see how that fairs.
-
The interfaces themselves must be set as static. You would only set them to DHCP there if you want them to pull an IP from some other DHCP server, like you would for a WAN interface.
You to enable a DHCP server instance on those interfaces in Services > DHCP Server.
Doing that will allow a client connected to them to pull a lease in the correct subnet.Steve
