Web page just shows up on some Devices devices but not others on Captive int
-
Hi my friends,
I set my captive portal on OPT interface , and i set my DHCP server on the same interface .
Captive prortal works well on Devices with win7 , but when i try to access internet using devices with (win8 , linux , android ,….) these devices get ip address from DHCP server and you see that the browser has started to redirect you to captive portal , but captive portal web page does nt show up , and consequently no internet access by these devices !!!!!any body faced the same problem , how it was sloved ?????? , any further sugesstion????
thanks for your feedback
Note : i am using 2.2.5-RELEASE (amd64)
-
I set my captive portal on OPT interface , and i set my DHCP server on the same interface .
Captive prortal works well on Devices with win7 , but when i try to access internet using devices with (win8 , linux , android ,….) these devices get ip address from DHCP server and you see that the browser has started to redirect you to captive portal , but captive portal web page does nt show up , and consequently no internet access by these devices !!!!!
...Think about this: pfsense doesn't know upon IP connection what the OS is on the device.
It won't be difficult to understand next that nothing can be done with pfsense to solve this issue.Another hint : on my captive portal, interface OPT1, androids, iphones, win7 and win8, even win10 connects just fine. I do not recall seeing linux devices on my portal network, because as an admin using pfsense I can't know, because, yes ! : pfsense can't tell (what the clients are using) ).
If the OS (or client, by human action) doesn't launch a browser, then no login page will be showed.
The initial http (not https, right !!) will get the browser be directed to the login page.any body faced the same problem , how it was sloved ?????? , any further suggestion????
Check the forum …. I didn't find anything mentioning this behavoiour.
-
Thanks for your reply , as i am thinking it is some how web server problem
would you please tell me which version of Pfsense do you currently use ? -
Thanks for your reply , as i am thinking it is some how web server problem
@yaman.amin:pfsense uses a web server - the one that hands over the portal login page.
Again, this web server doesn't minds (it doesn't even know) what the OS of the client is ….would you please tell me which version of Pfsense do you currently use ?
The latest 2.2.5 - or even later then that : 2.2.6 which is somewhat beta.
Clients can always connect to a captive portal. The very moment the device is (nearly) new, it just works.
I's possible that it "doesn't work"" anymore after that. There is a 99,99 % explanation reason for that. The owner modified devices network settings.
They always find a reason to :
-> Put in static IP for network and DNS => Captive portal connecting won't work anymore.
-> They use a default home page that uses htpps. => Probably, the captive portal connecting won't work anymore.
=> The pfsense captive portal web server listen (by default) to port 80 - and https requests goto port 443 ….. no ones is listening there (on pfsense) .... )
=> That's why I activated also https mode in the captive portal https part, which needs a valid (not a self made one) certificate. Site like startssl.com can make you one for free.-> I also saw : firewall application that refuses any gateway accept the one the user has validated (and of course, he hasn't validated our pfsense captive portal gateway).
-> Browsers with nice plugins that are not 'portal minded'.
-> Etc.Btw : just booted from a Debian (may I say 'Linux' ?!) portable. It found the wifi network, it got an IP (and DNS) from DHCP, and fired a browser so I could connect just fine using the portal login page. Works as advertised.
-
I deaktivate Captive Portal totally , and i noticed , i could only access facebook from Linux and android , but other web sites not .
and i got the same status by using different devices . so it is not end devices problem . -
I could solve the problem by adjusting the MTU on the wanted Interface to be around 1400 Bytes . thanks for your trying to help
