I just ran a status.php and in the output I search for '80' until I found a rule that looks like it
might be related to the captive portal.
19900 17 1576 fwd 127.0.0.1,8000 tcp from any to any dst-port 80 in
Is this the rule that forwards requests to tcp port 80 to the captive portal authentication page?
If so, can I add other rules like
fwd 127.0.0.1,8000 tcp from any to any dst-port 8080 in
fwd 127.0.0.1,8000 tcp from any to any dst-port 443 in
From: Jonathan De Graeve [mailto:Jonathan dot De dot Graeve at imelda dot be]
Sent: Mon 2/13/2006 10:08 AM
To: Wesley K. Joyce; m0n0wall at lists dot m0n0 dot ch; m0n0wall dash dev at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] Can CP Catch more than just port 80?
> Van: Wesley K. Joyce [mailto:wjoyce at uvi dot edu]
> Verzonden: zondag 12 februari 2006 23:07
> Aan: m0n0wall at lists dot m0n0 dot ch
> Onderwerp: [m0n0wall] Can CP Catch more than just port 80?
> I have users who may have their web browser configured to use a proxy
> server on port 8080. The Captive Portal doesn't appear to see http
> requests to port 8080. Is it possible to make the CP see ports other
Currently it isn't
> Or is my approach wrong and they should have an exclusion (that
> proxy) to some web server that allows the CP to see traffic to port
If anybody can think of a good solution for this, I will be happy to
What I do plan to integrate is to have an option to redirect DNS traffic
to our own local dns forwarder. This fixes a problem with people having
DHCP ip but static DNS
Jonathan De Graeve
jonathan dot de dot graeve at imelda dot be
Always read the manual for the correct way to do things because the
number of incorrect ways to do things is almost infinite