Problem whith captive portal
-
I have a problem with my captive portal, Telegram apk does not work for me, however, through a VPN it does connect me... someone who knows what the problem is and can help me, my version of pfsense is 2.6.0 release
-
This post is deleted! -
@Alejo2000 said in Problem whith captive portal:
I have a problem with my captive portal, Telegram apk does not work for me,
For a captive portal user ? Ones he is connected ?
@Alejo2000 said in Problem whith captive portal:
my version of pfsense is 2.6.0 release
I've used 2.6.0 for a long time, and all the version after it, no issue what so ever with any of them.
(edit : although, somewhere in the past, there was that "TCP only" bug)
Not that I'm using the portal myself that often, but my 60+ hotel clients do, and I don't know what they use, it could be anything.
And guess what : everything works, because, and repeat after me : ones the portal user is connected, the firewall is opened up for all protocols, all ports, all destinations. So no limit. If there is a limit, you've put it in there = GUI portal firewall rules. So, you remove it ^^ How, I don't know. nobody knows anything anymore about your ancient version. Why would we ?
Remember : if you keep an old version, your support becomes 'auto support', and only experts could try something like that. Guess what : they don't ... ;) -
@Gertjan ok, thank you very much for your explanation, I will try to take it to version 2.7.0 to see how it goes.
-
Make that 2.7.2 while you're at it.
Get your info from Netgate, as they know a lot about pfSense : Netgate Releases pfSense Plus Software Version 23.09.1 and pfSense CE Software Version 2.7.2 and here : https://www.pfsense.org/download/.
Upgrading from 2.6.0 to a current version : .... imho, don't do that.
-
@Gertjan But I was reading in a forum a few months ago about how to open other ports before authenticating the user in the captive portal, it said something about going to the initial configuration file of the captive portal, that is /etc/inc/captiveportal.inc and modifying the line 452 but in my version of pfsense the command lines are different and it didn't work for me
-
@Gertjan Ok thanks for the information
-
@Alejo2000 said in Problem whith captive portal:
@Gertjan But I was reading in a forum a few months ago about how to open other ports before authenticating the user in the captive portal, it said something about going to the initial configuration file of the captive portal, that is /etc/inc/captiveportal.inc and modifying the line 452 but in my version of pfsense the command lines are different and it didn't work for me
That was valid for 2.6.0, when 'ipfw' was used as the captive portal firewall.
pfSense now uses pf also for the firewall.
It's probably still possible to do "what ever you want" by modifying, you got that right, "/etc/inc/captiveportal.inc". -
@Gertjan Yes but it didn't work, the problem was still there
