Re: [pfSense Support] Captive portal update
On 8/26/05, Chris Buechler <[EMAIL PROTECTED]> wrote: > yeah, if that's the controls you want applied to authenticated > clients. Sounds like that's a bug though. Scott or someone will have > to comment there. Chris is absolutely correct. I'll drag all the equipment back out tomorrow and retest this. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Captive portal update
On 8/26/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > At 07:23 PM 8/26/2005, Chris Buechler wrote: > >On 8/26/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > > > > > > Running latest 80.4. Part of my problem was a basic > > > misunderstanding. I had assumed that the portal would block access > > > until you authenticated, so I left the default OPT1 => Any rule in I > > > had before. > > > >Not a misunderstanding, that is how it's *supposed* to work. This is > >a bug. Should be able to get nowhere other than the interface's IP > >itself (for DNS purposes) before authenticating, and after > >authenticating, your defined rules should apply as normal. > > hmmm, so i should have left the OPT1 -> Any rule enabled? > yeah, if that's the controls you want applied to authenticated clients. Sounds like that's a bug though. Scott or someone will have to comment there. -cmb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Captive portal update
At 07:23 PM 8/26/2005, Chris Buechler wrote: On 8/26/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > > Running latest 80.4. Part of my problem was a basic > misunderstanding. I had assumed that the portal would block access > until you authenticated, so I left the default OPT1 => Any rule in I > had before. Not a misunderstanding, that is how it's *supposed* to work. This is a bug. Should be able to get nowhere other than the interface's IP itself (for DNS purposes) before authenticating, and after authenticating, your defined rules should apply as normal. hmmm, so i should have left the OPT1 -> Any rule enabled? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Captive portal update
On 8/26/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > > Running latest 80.4. Part of my problem was a basic > misunderstanding. I had assumed that the portal would block access > until you authenticated, so I left the default OPT1 => Any rule in I > had before. Not a misunderstanding, that is how it's *supposed* to work. This is a bug. Should be able to get nowhere other than the interface's IP itself (for DNS purposes) before authenticating, and after authenticating, your defined rules should apply as normal. -cmb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Captive portal update
Running latest 80.4. Part of my problem was a basic misunderstanding. I had assumed that the portal would block access until you authenticated, so I left the default OPT1 => Any rule in I had before. So... I removed it and now access is not allowed until I go through the portal page. Still some issues though: 1. Even if I disconnect the session in the webGUI, pings can still get out. 2. Default portal page allows any username/password with no errors and allows access. 3. Once I disconnected the session, bringing up another browser window did not get me back into the portal page, and I was hosed... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
