The easy question next ... and maybe I am just unclear in reading. Will you be
able to use say a optional port for your captive portal and another port for
the lan? I guess I am curious wether you can assign the port the captive
portal functions on or whether it has to be the default lan port?
I wasn't really kean on this at first but I think it could have some rather
On Thursday 13 May 2004 11:52, Dinesh Nair wrote:
> On Thu, 13 May 2004, David Rodgers wrote:
> > How about an authentication option that can be enabled for the portal to
> > allow you to controls users via a radius server? Just a click box that
> > adds a userid and password field to the aup form and uses radius
> > authentication.
> since manuel's release of the captive portal functionality in 1.1b7, i've
> submitted patches to manuel for the addition of pass thru macs and allowed
> destination ip addresses for the captive portal.
> pass thru macs are a table of mac addresses which are always allowed
> access without being taken to the portal page or being authenticated.
> allowed ip addresses are hosts which clients behind the m0n0wall are
> allowed to access without being taken to the portal page.
> i'm now looking at implementing exactly what you say above, to allow the
> user to authenticate against a radius server using the radius protocol. i
> doubt i could finish this by this weekend, but rest assured that once i am
> done, i'll submit the patches to manuel and he can then place it in his
> next release.
> 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