Help with CP on OPT1
-
Merci pour votre réponse.
Sorry, my french is ...elementary at best.
@Gertjan said in Help with CP on OPT1:
I forgot to mention this one : Here : Status > System Logs > Settings
I will check in on this ^
@Gertjan said in Help with CP on OPT1:
You've checked if the portal's web server is running ?
I can access it via the LAN interface and the WAN (this FW is inside the network, just for testing purposes)
I have just gotten into the office. The test I have conducted this morning on the test box is to set up the same (effectively default) CP on both interfaces.
Still broken on OPT1. But then, at the console I reassign the interfaces, swapping the LAN and OPT1. The once dead OPT1, now LAN (ethernet) spings into life and vice versa for the old LAN, now OPT1 (fibre).
So I am still thinking I must have a firewall issue; These are the rules I set up.
-
@RobinWright said in Help with CP on OPT1:
Sorry, my french is ...elementary at best.
Mine also.
But the content of the portal html is not important.
Important is that it shows up.Firewall rules :
You don't need the lock out rule. When portal visitor try to acces the pfSEnse webGUI, or SSH, they might be getting locked out.
See that a a bonus. You don't want potential hacker on your networks.The third rule isn't needed.
The captive portal doesn't use IPv6 - it can't.So, rule 2 by itself is just fine. That is, if the portal network's name is "GUEST'.
@RobinWright said in Help with CP on OPT1:
now OPT1 (fibre).
You use local 'LAN' fibre connection ??
-
I can see in the log there is a 302 response, so I'd expect a redirect. I can also see the GET request for /index.php?zone=guest
10.254.0.10 is a Chromebook currently connected via OPT1. The browser will sit and wait, then timeout when trying to access PFS. See below for an example of attempting to view the GUI.
Interesingly, if I type in the IP for the GUI, or the CP Login page, there is no entry on the log.
The IP for OPT1 is definitely 10.254.0.1.
-
@Gertjan said in Help with CP on OPT1:
You use local 'LAN' fibre connection ??
Yes, 10Gb Fibre internet, so fibre into the main LAN switch.
-
Nice.
But do check and show : the DNS and gateway (see above, way earlier).
Just to be sure.This :
means that the captive portal web server received the request - and delivered (status = 200 = Ok) the request page /index.php&redire .... to the web browser = 10.254.0.10.And nothing shows up ?
-
@RobinWright said in Help with CP on OPT1:
Yes, 10Gb Fibre internet, so fibre into the main LAN switch.
Ah, ok. You mean your ISP connection is a 10 Gb fiber connection.
That connection doesn't get into a switch.
It goes into pfSense, the WAN interface, or in a device, your ISP modem/router/whatever, and this device's LAN is connected to the pfSense LAN - using a classic RJ45.
Right ?10 Gb fibre LAN is .... extremely rare, I never saw a SOHO local network using 10 Gb, fiber based ....
Do they even exist : 10 Gb fibre access points ?But (sorry
) you can't be that network crack as you are using ... Chrome 
-
Sorry, I assumed from the portal content that you were french!
@Gertjan said in Help with CP on OPT1:
And nothing shows up ?
Yeah, I was getting nothing.
I will make FW rule changes you suggested, I was just trying to replicate the automatically generated LAN rules.
I was typing this reply (below) but my MacBook just popped up with the portal randomly (I have a myriad of devices on this task at the moment)... I check my phone, also now loading the portal. Nothing on the chromebook still, so I renenewed it's IP Lease and now that is working..! Totally bizarre. What on earth happened? I was getting the same issue on prod, so I can hopefully find out what changed; but that seems unlikely.
@Gertjan said in Help with CP on OPT1:
But the content of the portal html is not important.
Important is that it shows up.Curl requests for both addresses return the same response. (on the PFS shell)
OPT1 address
LAN address
Edit: I failed to crop screenshots.
-
@RobinWright said in Help with CP on OPT1:
Sorry, I assumed from the portal content that you were french!
Noop, that's the language I use, because I live in France.
I'm dutch.@RobinWright said in Help with CP on OPT1:
Nothing on the chromebook still,
I don't trust these devices, as they do things like 'using their home DNS = 8.8.8.8' as we all know why and who build them.
Normally, this isn't an issue, but when you add a captive portal to the mix, everything has to play by the rules.@RobinWright said in Help with CP on OPT1:
Curl requests for both addresses return the same response. (on the PFS shell)
That's correct.
As said earlier : the portal web server listens to all (== all interfaces). The sockstat command told you.
It even listens on WAN ^^But who is going to ask on your LAN interface an index.php using port 8002 ?
Nobody.
Only on your GUEST interface this rquest, using port 80 using TCP, will get redirected to 10.254.0.1 port 8002.See here : this file /tmp/debug.rules and look for all the 'portal' firewall rules.
Looks like it's working now ?
-
@RobinWright
As pointed out by Gertjan the WAN connection is to the internet. Fiber is becoming common with the adoption of SFP+ in lieu of RJ45 ports. What is important is that the WAN/Internet connection go directly to the WAN interface on the system you have pfSense installed on.This is also true for LAN, it must connect to it's own interface, which is a different interface than the WAN, on the system you have pfSense installed on.
Now, for the OPT1 interface it too must have a separate or different RJ45/fiber connection to your device(s) you wish to capture. You indicated you plugged directly into OPT1 and could ping both LAN and I assume your OPT1 subnets, (i.e. 192.168.1.1 and 192.168.3.1 for example.) Each of those interfaces should have separate DHCP servers setup. As long as you plug directly into the OPT1 interface, you are getting your IP from the OPT1 DHCP server. That device should be able to ping itself and the gateway.
One possible concern is your mask for the LAN and OPT1, both should be /24, i.e. not overlap. They are separate networks after all.
Your configuration will require you plug your devices that use the captive portal (Normally a WiFi Access Point) into OPT1 either directly or through their own separate switch(s). It can NOT be plugged into the same network as LAN unless you have at least Level 2 switches and have setup VLans on it. If that is the case, you can ignore the next paragraph.
If using L2 for LAN and OPT1 with an L2 switch, you must setup a VLAN interface on the switch, then under Interfaces, Assignments, VLans. Next, add it as an interface under Interfaces, Interface Assignments. That interface will now show up as an option for Captive Portal, use it for the portal. Then go and setup DHCP on it. For example, if you choose VLan ID 10, use 192.168.10.1 as the IP for the interface DHCP. For the firewall setup a pass all rule. Make sure the Access Point enables the matching VLan ID on the Station ID you are connecting through.
-
@Gertjan said in Help with CP on OPT1:
Looks like it's working now ?
It seems so, just a mystery as to why? My test methodology is typically to change something, test and restore if it doesn't work.
Perhaps it was just the devices acting out of sorts. (We have a lot of Chromebooks come through here)
I will try and get the prod setup working...
