[ previous ] [ next ] [ threads ]
 From:  Fred Weston <Fred at daytonawan dot com>
 To:  Josh McCormack <joshmccormack at travelersdiary dot com>
 Cc:  dick at dickmorrell dot com, Manuel Kasper <mk at neon1 dot net>, M0N0Wall firewall <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] captive portal support
 Date:  Tue, 20 Jan 2004 07:39:34 -0500
Josh McCormack wrote:

> My friend Bruno does something for a captive portal that I thought 
> might be interesting. Here's what he told me he does:
> "I do captive portal by redirecting trafic to local port 80 and
> using an modified http server (busybox http) to print a error
> page (with a redirect) to any page not found locally
> as the http server don't have any pages, all will be redirect
> to my main server (access to it is granted through the portal)."
> I asked him if I could share this with the m0n0wall list and he said:
> " you can share my idea freely but I don't think it will be "the"
>  solution for everyones cases... remember I force ppl to load
>  PPTP on top of their systems, and my "captive portal" only tells
>  the user to do so (for space constrainghts, redirecting to an
>  external server)
>  I feel ppl would like to include some sort of logging in capabilities
>  on the router itself, which is more like nocat and less more my
>  "solution" (unless "mpd" is installed on monowall)
>  but tell, anyway. perhaps ppl can make suggestions/improve the idea,
>  who knows?! :-)"
> Josh
> ---------------------------------------------------------------------
> 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
I'm not sure I understand why he is forwarding port 80 to the local 
server, and then in turn redirecting to the portal on another server.  
Why not simply forward the user directly to the portal on the second server?