Problem Captive Portal pfSense 2.7 with allowed ip addresses

[TbW]

@Gertjan Thanks, let me know how your test with 2.7 goes.

[TbW]

@Gertjan
hello, have you tested pfSense 2.7 ?

[Gertjan]

@TheBigWizard said in Problem Captive Portal pfSense 2.7 with allowed ip addresses:

@Gertjan
hello, have you tested pfSense 2.7 ?

Noop.
Haven't been able to go home yet (working for a hotel, it's high season and all that).

But : follow also this : Captive Portal NOT working in 2.7.0 thread.
It was resolved (The portal works after all) and asked a favor back : check "allowed IP addresses" please, as the test take a minute or two.

I've compared the 'code' between 2.7.0 and my 23.05.1 as I'm using it right now.
It's identical**, so I'll motivate you : Only our "local settings differ".

** not the kernel - I presume the embedded name is different.

[TbW]

@Gertjan Thanks!

[Gertjan]

@TbW

It has been tested : see here, the last two posts Captive Portal NOT working in 2.7.0

Allowed IP working and does not show up under Captive Portal since it's a bypass.

[sanrzn]

same problem
Install version 2.7.0: new disk + import config from 2.5.2
Enabled services: DNS Resolver, Captive Portal, OpenVPN server, ntpd
Installed Packages: pfBlockerNG-devel (3.2.0_6), haproxy (0.63_1)
Others: DHCP, DNS (with forward to firewall) on domain controller

IPs from Captive portal’s Allowed IP Address List not have access with no authentication, but if add MAC of IP to "MAC Address Control" pass without requiring authentication.

PS: This configuration worked fine on version 2.5.2.

[TbW]

I reinstalled pfsense 2.6 and configured ldap gsuite. Everything works perfectly. Also "allowed IP addresses" of the captive portal.

[susobaco]

Same problem:

[Gertjan]

@susobaco

As showed in the other thread I linked above, the "2.7.0" portal works just fine.

Some thoughts though :
if this gets involved :

@sanrzn said in Problem Captive Portal pfSense 2.7 with allowed ip addresses:

haproxy (0.63_1)
Others: DHCP, DNS (with forward to firewall) on domain controller

then the setup will need more attention.

I'm pretty sure that if the classic setup was used : pfSense is the DNS, and handles the DHCP, the portal works.
Now, step by step : remove DHCP, have it being handled by another DHCP server : and test (!) : it can be done. It's a question of the correct 'settings' and all devices/systems involved.
Next step : pfSense isn't handling the DNS anymore on the portal : that can be arranged also.
Another step "domain controller" : ok, why not. Things are getting way more complicated as even more things have to be checked. I never did this myself, but I presume it is possible.

[wtasin]

Hi,
I had the same problem.

I found out that switching the Webconfigurator back to english language helps.

pfSense expects to get as direction value either "both", "from" or "to".
login-to-view 

After switching back to english, you have to edit and save the wrongly saved "Allowed IP address" entries.

Even if I export the configuration (with the german translated WebConfigurator) I found the translated string as value in the config.xml.

HTH

[TbW]

@wtasin HI,

so using the English language, does it work?

[wtasin]

@TbW yes, the arrows are showing up and the bypass of the allowed ips also works

[TbW]

@wtasin OK thank you. I will try.

[serginho]

realmente funcionou fazendo da forma que você explicou, mas o controle de banda não funciona.

[TbW]

@wtasin yes, it actually works in English language.
@serginho bandwidth control does not work. Seems limited to 100 Mbit/s per user.

[Gertjan]

@TbW said in Problem Captive Portal pfSense 2.7 with allowed ip addresses:

Seems limited to 100 Mbit/s per user.

Do I need to show an example like this :

login-to-view

or like this :

login-to-view

Btw : I'm using 23.09, and I presume that 2.7.1 and 23.09 share the same kernel, kernel modules and and GUI.

[TbW]

@Gertjan If you allow navigation by entering the mac address, the device is set up to 100 Mbit/s DW/UP.