@SmartCodar: Facebook keeps on adding URL's and when ever there is new URL in backgroud Facebook will try to open URL and since there is no Internet Connectivity facebook page will keep trying opening URL unless timeout. Upon timeout Login page is shown. and finally, the FB server detected that 'you' (your users) have aceBook access problems and the 'blacklist' you (your IP) altogether for a while. @SmartCodar: It seems that the list is not complete. and they keep doing so - this list http://bgp.he.net/search?search[search]=facebook&commit=Search never ends, and is still growing. Which is under stable: a 'good - final' solution after years of doing so will give the impression that 'it is always the same' and FB will LOOSE clients. CLienst/users want NEW things every day …. Their is only ONE solution : sign up with FB, some kind of contract that YOU, as a third party person, will use THEIR authenticity system that fires a signal (call-back) to your server (== Captive Portal). Go to one of their offices. Bring along a coding specialist (the public API won't lett you do what you need - you will have aces to another API (which also is evolving) Bring along a lawyer Bring along a huge amount of cash (Hey, you thought FB was free like 0 $ ? - they DO make money) You'll be having your FB authenticate pint with fixed URL's and IP's (never ever tell somebody about them, because if they become public, a simple ddoss will blackout these points, having big clients (who paid FB) leaving in the dark ..... and they will yell, because they paid for it) Etc etc. The secret of why FB works for everybody (well, they do go down, globally) is that works VERY distributed. If one FB host isn't available, another one. If one is overloaded, another one pops up. Capture this behavior with a what a Btw : tis question has been asked many times. It will be asked again next day, or tomorrow. To answer it, you should know what a "Captive Portal" is. How FB works (API). Mix up the to together and your have a real "Misssion Impossible 8" (the exception might be : be friends with the owner or your bank). I will NOT exclude the fact that a solution MIGHT exist. Maybe something like this: redirect the visitor to a local page that EXPLAINS: That the visitor should authenticate with FB in ONE minute. You open up your pfSEnse Captive portal for ONE minute for every new IP/MAC. After that, if it had NO FB call-back that says : Ok, this user (IP/MAC) logged in, your shut down the connection for X hours.

Asking for help with 2.0.1 is going to receive little feedback other than "upgrade then ask again." Nobody has a test environment for 2.0.1 to try things to help you. If you want to pay me US$2500 to setup and US$500/yr to maintain a 2.0.1 test environment plus US$100 per ticket, for which the accepted, billable answer might very well be "that's broken in 2.0.1. Upgrade."  PM me.

Sorted, here is the solution for future users looking to do the same….sorry to differ by the rest, but i find no pleasure in putting more misery into other people struggles, much better to write nothing at all than follow their truly horrible attitude....

@SmartCodar: @Gertjan: Thanks Gertjan this worked very well Thanks, Can you please let me know which config file I need to use? Also does Write_Config can be called using a Cron? I mean without doing login or Authentication. @SmartCodar: Basically I need to Upload the Captive Portal Page pro-grammatically. ….. For example when PFSense System is rebooted. is there any way where I need to copy my Captive Portal Page Content file? I have tried to copy in \var\etc but it wont worked. Is there any additional step I need to do From how I understand it, when pfSense reboots, using PHP a script, use wget/ftp/curl/what-ever to 'import' a new html file, and write_config() it. See here https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/services_captiveportal.php#L447 The other way around: create a script (it can be on any device that can access pfSense**)  that accepts a $POST, so you can send ove new file - put it in the config,  write_config() and restart the captive portal service. ** if needed, you can decide to skip the entire GUI login protection. Remember, its PHP, your free to do what you want ;)

Hi! First, I would like to say that this is a very beta version. All basic features are working fine, exept expiration date. This field will be used by bash or PHP script that will run daily (hourly?) and delete expired vouchers. Also, software are made in portuguese, but there's a file named 'pfvmanager.po' located in 'locale/en/LC_MESSAGES' ready for translation. If you wish, you can translate this file to your language and send to me :) And for the last: this is a free software, but you must keep credits in source code and footer page :) Instructions how to install are in my blog: https://www.jonis.com.br/2015/10/15/pfvmanager-vouchers/ Feel free to post bugs and feature requests in my projects page: http://projetos.jonis.com.br/projects/pfsense-voucher-manager

It seems there's no way to intercept that behaviour. The browser start an https connection and wait for a valid certificate. So you can only send an invalid certificate and receive a cert error by enabling https login in captive portal. Without  https login the client browser will be stuck waiting for cert. It's an https design I see. But I still think that making an unexpensive or free project like captive portals with no authentication sould be possible. Instead with https you need a more complex infrastructure and management. You can't no more do that and forget it as you can expect from a free project. I wonder why no one ever put things that way. I love https but I think we should have a workaround maybe browser side. After all we want something legit. Just allow navigation with proper https after a splash page was shown. Not a real man in the middle workaround. Sorry for this question but I tought that it's too strange  that https don't allow redirect in any case. Never saw things that way before.

Yeah, should be msftncsi.com

No idea, the only thing i can be sure of, is that i didn't touch a single thing after the problem manifested itself, apart from switching off(yesterday) and on again(today) the machine, as i was looking for an answer before to possibly make things even worse by doing something wrong  :D

@doktornotor: That's a version you should NOT be using at all due to numerou vulnerabilities and severe bugs. Let alone keep customizing it. Absurd. I understand, thanks. But this build has a lot of customization and I'm on the process of migrating them gradually.

Thank you very much muswellhillbilly, after enabling the option in the portal worked perfectly.  ;D Really thank you for the help, ALL the information I need are stored in radacct table. =D Again thanks for the help, saved many hours of work debugging to find that little detail configuration. Sincerely Tácio Andrade.

Going back to basics first, with the captive portal disabled, can the VLAN access the internet? Without a connection to the internet behind the captive portal, the page will never load. (DNS)

Nope. Code is on github.

@jp_redbeam: We actually found the solution to the issue in: https://forum.pfsense.org/index.php?topic=62173.0 Be careful, that thread is talking about an issue that existed with a very old pfSense version. Most of the code has changed by now. (never ever use an old version - even experts don't)

Even better, you could get rid of Wordpress altogether…  :P

You need a small transit network between the 1941 and pfSense WAN.  Then you put your LAN users behind pfSense LAN.  You don't need an interface on LAN on the 1941. The captive portal has to be between the edge router and the clients. It can't just be some server sitting on LAN.

This is something I had to look at for a customer last year, in the end I ended up using my website, and using a cURL command in PHP to log e-mail address into a MySQL database.

the answer is YES. im actually doing it. and also i use a wireless router after my pfsense and my devices redirects to captive portal (just not a dd-wrt tho) but still, i think pfsense will sill redirect devices to its captive portal. but to be sure, just turn off DHCP on your router then plug your pfsnse to one of your router's LAN ( again LAN not WAN) ports and you'll be good to go.