I use the captive portal for our wireless operation. We do not use the Unit
as an AP but the LAN ports to govern the other APs coming into a switch and
we set the DNS servers on the wan side to our outside servers and let the
Monowall do the DNS relay on the LAN side and it works very nicely for us.
The customers can get on the net and to the signup pages and to internal
portal stuff but not to the Internet.
It works so well in fact we finally decided on using the Wrap boards and are
installing them at all the places we have pay per use APs so we can give
custom signup screens and track the usage and signups to give commissions to
the locations. This way each location has it's own DHCP, DNS And signon
screen, even if the backend connection is down.
We are also hoping to get some kind of SNMP status page soon to tell if the
backend (WAN) connection is up. Hint Hint developers. We are working on it
and hope to get it soon.
Connect Data Inc.
From: Dinesh Nair [mailto:dinesh at alphaque dot com]
Sent: Tuesday, December 28, 2004 11:36 AM
To: Dave Warren
Cc: Keith Redfield; m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Captive Portal issue
On 27/12/2004 17:21 Dave Warren said the following:
> I don't suppose there would be any way to create a specific set of
> firewall rules to apply to unauthenticated portal clients, is there? --
not yet, but you could point the m0n0wall at those two DNS servers and then
use the m0n0wall as the DNS server on the LAN and/or captive portal
Regards, /\_/\ "All dogs go to heaven."
dinesh at alphaque dot com (0 0) http://www.alphaque.com/
| for a in past present future; do |
| for b in clients employers associates relatives neighbours pets; do |
| echo "The opinions here in no way reflect the opinions of my $a $b." |
| done; done |
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch