Captive Portal dont work in smartphones

mr.J

Hi guys!!
I have a captive portal working on computers when they connect to my network, but when smartphones connect in the same way, the captive portal does not work on them, but captive portal continues work on the computers. What is the problem? Another things is that in smartphones when they connect my network, they haven't internet, because dont't appear the captive portal (i think :D ). Someone know what is the problem?
Thanks.

Gertjan

Hi,
I’m running pfSense for a hotel for the last 10 (!?) years.
I don’t know what type devices my clients bring along. What I know is: there are smartphones.
It works for me ANF for them the last 10 years …
You have the same version as I have. The only difference is: your setup.

benpal

Hi mr.J,

How did you connect your Wireless Access Point to your pfSense router?

Your pfsense router should serve as the DHCP server to all your mobile device clients…

Kindly give more details to your network setup...

Derelict

It makes no difference what the DHCP server is. It can be pfSense or something else.

What matters is that the lease times given by that DHCP server are compatible with your captive portal timeouts and that the pool is large enough for your device churn.

You have to understand that what happens when a client connects to a CP-enabled network is 100% up to the client. All the CP does is redirect connections to port 80 to the portal page instead. If that doesn't trigger the device presenting that page it is a problem with the portal page content, the device, or both. Or the device is simply not making a connection attempt to port 80 after it connects at all.

mr.J

Thanks everyone,
First, my cell phone is communicating with pfsense because it receives an ip from my range of ips. I think the problem is my captive portal that does not work on the mobile because it is working on computers. Another suspicion is how Derived "said" the connections are not being redirected to a port 80. Regarding timeouts, this is compatible with timelease. Ahhh another thing, if you manually put the ip and then the port, for example 192.XXX.XXX.XXX:8002 it redirects to the captive portal. But this if you manually put ip, this does not happen automatically. Any suggestion?
With best Regards,
mr.J

Another thing, I was watching on the internet, and some people said that it is dns problem, that it was just enough to change to DNS Forwarder, but I changed and it did not work. Also if it was a DNS problem, it was not on the computer, right?

Gertjan

@mr.J:

First, my cell phone is communicating with pfsense because it receives an ip from my range of ips. ….
Ok, DHCP is working. But tell us more, because there is more.
What was the DNS and Ga

I think the problem is my captive portal that does not work on the mobile because it is working on computers. Another suspicion is how Derived "said" the connections are not being redirected to a port 80. Regarding timeouts, this is compatible with timelease. Ahhh another thing, if you manually put the ip and then the port, for example 192.XXX.XXX.XXX:8002 it redirects to the captive portal. But this if you manually put ip, this does not happen automatically. Any suggestion?
With best Regards,
mr.J

@mr.J:

Another thing, I was watching on the internet, and some people said that it is dns problem, that it was just enough to change to DNS Forwarder, but I changed and it did not work. Also if it was a DNS problem, it was not on the computer, right?

"on the Internet" doesn't exists. If you have a link, show the link. TRue is, "some people" say … well ... there is no limit.
I tend to propose : use the "DNS Resolver", not the "Forwarder" because, why should you handle stuff remotely (== takes longer) if you can do it "right here" (locally).
Btw : https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting

Gertjan

@mr.J:

First, my cell phone is communicating with pfsense because it receives an ip from my range of ips. ….

Ok, DHCP is working. But tell us more, because there is more.
What was the DNS received ? Gateway ?

@mr.J:

I think the problem is my captive portal that does not work on the mobile because it is working on computers.

??
A mobile == a computer. For pfSense there is NO difference. Except : a mobile device connects by Wifi so there is an intermediate AP. Meany newbies don't know how to setup an AP correctly (as seen on the forum)…..

@mr.J:

Ahhh another thing, if you manually put the ip and then the port, for example 192.XXX.XXX.XXX:8002 it redirects to the captive portal. But this if you manually put ip, this does not happen automatically. Any suggestion?

Entering a static IP (nad mask, and DNS, and gateway) or receiving them by DHCP is the same thing.
Check out what how it is different and you are close to a solution.

@mr.J:

Another thing, I was watching on the internet, and some people said that it is dns problem, that it was just enough to change to DNS Forwarder, but I changed and it did not work. Also if it was a DNS problem, it was not on the computer, right?

"watching on the Internet" isn't very clear. Much is said on the net. If you have a link, show the link.
I tend to propose : use the "DNS Resolver", not the "Forwarder" because, why should you handle stuff remotely (== takes longer) if you can do it "right here" (locally).
Btw : https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting