Chris Buechler wrote:

> Oh! I wasn't aware of the check was that tight. That check was changed
> long ago in pfSense (it won't let you enable CP on a bridged interface
> with no IP, but it will for any inside interface with an IP), I never
> realized it existed in its current fashion. I'm not sure how that will
> impact m0n0wall-specific things. After a cursory test, it works for me
> when setup in the manner you describe. I have OPT1 bridged to WAN, and
> CP on LAN. Try uploading this:
> http://cvs.pfsense.org/~cmb/m0n0services_captiveportal.php
> using exec.php, then run:
> 
> mv /tmp/m0n0services_captiveportal.php /usr/local/www/services_captiveportal.php
> chmod +x /usr/local/www/services_captiveportal.php
> 
> Enable CP on an internal interface with an IP, and see if/how it works.
> 
> That has no input validation at all, if it works for you, I'll port
> pfSense's input validation so you can enable CP on any inside
> interface with an IP and get it committed for 1.3.

I have no way to test right now, but will try when I get back from the 
weekend...  (I would say vacation, but 1) it is only 3 days. 2) It looks 
like I will have to work for part of one of them...)  <sigh>

			Lee