Hey all ! I have noticed the same with my pfsense, and here's the bit of the CP that I'm using: <captiveportal><page></page> <timeout>120</timeout> <interface>opt1</interface> <idletimeout>30</idletimeout> <freelogins_count><freelogins_resettimeout><auth_method>radius</auth_method> <reauthenticateacct>stopstart</reauthenticateacct> <httpsname><preauthurl><peruserbw>I read on the following post a report of a problem ( http://forum.pfsense.org/index.php?action=profile;u=113943;sa=showPosts ), and I realised I had set the CP to use "start/stop accounting", so I set it as "no accounting updates". And everything seems to be working now, but I'm not sure whether it is because a change the radius settings, or because I have rebooted the server. Well, hope it helps identify where we could have a problem. Regards Iwashima</peruserbw></preauthurl></httpsname></freelogins_resettimeout></freelogins_count></captiveportal>

@powerguy42: http://www.dmasoftlab.com/cont/home I've tested this with pfsense and it works great, has anyone else used this software? pfSense is listed as a supported product on there site. Pretty cheap too. Can this run directly on my pfsense box or does it require a separate server?

@ermal: Can you show your system log? Yes, of course, but there is nothing interesting in there as fas as I can tell: Sep 3 23:06:19 kernel: arp: 10.100.79.13 moved from 00:26:4a:08:07:96 to 2481:b9:56:c6 on rl0 Sep 3 21:06:08 check_reload_status: Reloading filter Sep 3 23:06:01 kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled Sep 3 21:06:00 check_reload_status: Syncing firewall Sep 3 23:04:26 kernel: arp: 10.100.79.12 moved from 58:b0:35:b3:d0:8e to 00:16:cb:c3:60:99 on rl0 Sep 3 23:04:12 php[32837]: /index.php: Successful webConfigurator login for user 'admin' from 10.100.78.254 Sep 3 23:04:12 php[32837]: /index.php: Successful webConfigurator login for user 'admin' from 10.100.78.254 Sep 3 23:02:45 kernel: arp: 10.100.79.42 moved from 00:17:f2:c9:3b:f1 to 2481:b7:b6:06 on rl0 Sep 3 22:52:09 kernel: arp: 10.100.79.149 moved from 00:26:08:0e:b6:00 to 2481:b9:57:9f on rl0 Sep 3 22:51:03 kernel: arp: 10.100.79.155 moved from 00:26:08:0e:b6:66 to 2481:b7:b6:06 on rl0 Sep 3 22:46:00 kernel: arp: 10.100.79.16 moved from 00:22:41:3b:e0:16 to 2481:b9:58:15 on rl0 Sep 3 22:45:24 kernel: arp: 10.100.79.63 moved from 00:1b:63:a2:df:29 to 00:16:cb:c3:60:99 on rl0 Sep 3 22:44:51 kernel: arp: 10.100.79.63 moved from 2481:b9:57:8c to 00:1b:63:a2:df:29 on rl0 Sep 3 22:43:23 kernel: arp: 10.100.79.23 moved from 00:26:4a:08:0c:fa to 00:16:cb:c3:60:99 on rl0 Sep 3 22:42:59 kernel: arp: 10.100.79.15 moved from 58:b0:35:b3:27:d2 to 00:16:cb:c3:60:99 on rl0

asura, have you tried the setting? Will it sync back between portals when vouchers are used up or can one use each voucher on every CP?

ok ive figured it out, i had a couple of server ip addresses in "allowed ip addresses" which had the subnet /24 bits and it should have been 32 for one ip only- changing it to /32 and captive portal working again. :) Thanks

CP and system logs.

as you say. I can do it with Sarg.

If you know where all those apps are, yes.  You allow the app server IP in captive portal.  I alwayse stick the popular update servers in mine…  (windows Update, Symantic and McAfee)  Problem is they keep moving them.

Since your family will not be changing hardware often, use the DHCP server to statically assign them IP addresses in a range you allow to access the LAN.  Place them in Allowed IPs if you wish and they will not need to log in.  Other users will use standard DHCP and leave that scop with no access to you lan.  They would need to log in…

I have lots of login pages with css.  Not that the file names change when you upload them and the base page html must reflect that…

Just a quick update. Connecting this Zyxell to an external antenna it's a waste of time, not sure if the signal get dispersed on the 4 meters RG6 or just it doesn't pull out enough Watts…

It worked! It's funny! All of this trouble just because of a single 'ñ'. Thank you!! thank you very much , seriosly!!! It's upgraded now, but I can't enter webconfiguration. Why?, it doesn't even respond to ping, even though the IP address for LAN is assigned perfectly, and it connects the WAN perfectly, too

@ermal: There was an issue with IE 8/9 and some type of url redirection which made IE block. That should be solved on the coming 2.0.2 release. I see. IE9 is my current browser, so, it's much worse of what i thought. Good to knows anyway, at least i will not try to test other options. Any ideas of when (approximately) this new release with the "fix" will be available? Thanks!

I submitted a fix for this last year some time where it wouldn't delete the fields if you configured and then unconfigured it. Glad your browser cache fixed it.

Thanks GeertJan, i also aggree, that is a useful scenario, for hotels too most guest have multible devices, for eg. a laptop, an ipad, or a smartphone. i suggest an option: max concurrent connection per voucher/session/whatever: <number>so you can open a time window for a limited range of devices and doesn't loose all the security…</number>

I see you are using a "Beta" release, wouldn't be better to go for a "Stable" version which are supposedly free from bugs/errors ???

http://forum.pfsense.org/index.php/topic,34148.0.html

@electric34: I dont know htlml coding, and this url pre-auth redirect is throwing me off. What do i redirect to for users to sign in? For each user i have to setup a account for? if i do local user authentication. I have a terms and conditions policy i need to upload. You don't need the "pre-auth redirect", as the words say, that can be a page that users can see before they reach the login's page. The problem with this option, is that any page you want to use, will need some code on it to send back the user to the login's page, i hope the developers will find a more user's friendly option at some point, as the "After authentication Redirection URL" option. Here is a usefull link to read:    http://forum.pfsense.org/index.php/topic,34148.0.html