@m1s1u: Is it possible to display MAC address of the client machine on the portal login page? If so how to achieve this? Actually, its possible - to have it on the 'Logout' box…. Add this: LogoutWin.document.write('**Client MAC : {$clientmac}** '); To the file /usr/local/captiveportal/index.php on line 316 (search for the other LogoutWin.document.write…. code). Edit - save - Done

Hi again, No comments on this..? Can anyone running beta 3 check if they are able to successfully save changes to the captive portal gui page? Here a http error 404 is thrown immediately after clicking the Save button.  When reloading the page no values have changed. I cannot even use the captive portal /file manager to save my custom captive portal http pages. Everything else from the webgui seems to work ok. To help me out, in which folder can I manually save the custom http pages?  And where dio I assign their filenames? Secondly, if I make changes in config.xml, how do I apply the current config.xml to the pfsense config? Thanks a lot for comments best regards Tor

action accept proto: tcp source: LAN net port: any destination: RADIUS net port: 1812-1813 gateway: default

Well, seems like the newest firmware fixed my issue.  4-06-06 firmware Thanks, Andy Morris

Hi, User is still able to login to multiple pc's simultaneously with one username and password. Captive Portal setup as follows: Enabled Interface: LAN Idle timeout: 60 m Hard timeout 240 Logout popup: checked Disable concurrent login: tried both (checked and unchecked) Disable Mac filtering: unchecked Authentication: local user manager thanks

thanks sullrich that did it, ur great.

Just nmapped our captive portal here… And its not doing this. nmap -P0 10.0.0.80 Starting nmap 3.93 ( http://www.insecure.org/nmap/ ) at 2006-03-24 12:49 EST All 1668 scanned ports on 10.0.0.80 are: filtered MAC Address: 00:00:24:C1:F7:71 (Connect AS) Nmap finished: 1 IP address (1 host up) scanned in 36.169 seconds

actually I had to use Auth-Type== local, instead of system which is defult… in that case it will fall through all local modules installed

yep u are correct, everywjhere exept the part tha MAC addresses are sent during Accounting-Start…. all other junk thta I dont care about is sent when Accounting-Stop is sent :-(

ok, sounds good, but that is not going to ahppen any time soon :-(

Not at the moment.

Alright, good to know  :)

@Gertjan: @jeroen234: most browsers block the popups Why not explaining on your main Portal web page that users should/could use IE->Utils->Blocking popup windows->Parameters to block publicity-> [[b]add the opt1 IP : i.e. 192.168.2.1] so they would receive a 'disconnect' windows, from pFsense only. That wouldn't work, as depending on which page the user tried to access the captive portal popup page appears to be from that side and not the pfSense. Try going to google.com when not authenticated. you would have to allow popups from google. next time you hit it by going to myfavouritesite.org and you would have to enable popups from that site…doesn't work. I would rather like to see a single line small frame at the top of the next page after authentication to give the user the possibility to click "open logout popup" along with a note as most browsers allow the popup when the user clicked on it.

for what i typed you do not need vlans every accesspoint can do this for the access point is the data from normal clients and the vpn clients the same both are using opt1 but the data of the vpn users is protected in  a tunnel between the vpn server and the client and running on top of the normal opt1 ipadresses with this you have normal clients surfing  using the portal on interface opt1 and the protected clients are surfing with a vpn conection to the vpn server of pfsense on opt1 but the vpn server is also conectebol from the lan or the wan interface the data of normal clients on opt1 every one can read the data of the vpn clients on opt1 is only readebol for the vpn server an the vpn client

You could do something like that by using an external radius server and a frontend to create temporarily users in that one that get deleted after a given amount of time and let pfSense check against that. However you'll always need a user and password combination but to simplify things the user and pass could be the same pin.

:D  finally got it working…  created a firewall rule to permit dns traffic... seems to work ok now :)  Thanks to everyone for their sugestions  :-*

@jeroen234: i have this to but by me its not the fault of pfsense i use a wds link between 2 accesspoints and this is the problem the ip from the secend ap is sent wen you use the portal and not that of the client that usees it afther the login so 10.141.254.251 get access but the client 10.141.254.241 don''t get it and get the login page again this is a problem of the wds link mebe you have a problem simelur to this Yes, is this the problem. I use Pfsense back of AP in WDS mode. I see the log of captive portal and assign pass for the ip of the last WDS link. What is the metod for resolve this. One is use a wireless adapter card (not a ethernet card), other method is make my WRT54G AP in mode client Bridge ( if possible this?). I have another alternative?