[isf-wifidog] Coova + WifiDog - Need no internet page

Jason Potter jason at hugedigital.com
Mer 4 Aou 10:06:32 EDT 2010

Hi Geneviève,

Am I correct in saying that when a connected authenticated client makes a
request to a web page a dns lookup occurs, and the gateway through ip tables
could "catch" the request and redirect to the packets to the internal web
server of the gateway?

But in the case of a client that has a cached DNS entry, the web browser
tries to go to the ip directly, could this also be "caught".

In the case of the DNS "catch" would you have to actually return a DNS
response to the browser or could you just redirect?

Look forward to your response.


On Wed, Aug 4, 2010 at 11:58 PM, Genevieve Bastien <gbastien at versatic.net>wrote:

>  Hi Jason,
> Situation 1
> The auth server is down page is displayed as expected
> The page that is shown there is the green page saying "Uh ohhh  internet
> not available", right?  This page resides on the gateway and is the file
> /etc/wifidog-msg.html
> Situation 2
> The client connects to the hotspot and then tries to go to the browser
> default page,for example www.google.con.au.  The client gets a Server not
> found error in their browser.  I would like to have the Auth server is down
> page displayed.  I believe what I am seeing is due to the DNS lookup
> failure.  Is there away around this?  Since the user is not authenticated
> yet, i would of thought all requests would be redirected without doing a DNS
> lookup.  Have I miss-understood this?
> Situation 3
> The client is browsing the internet and the internet connection goes down.
> I would to show the internet down page when they request their next page.
>  Indeed, there is no internet is down page.  Actually, I think the gateway
> is not involved at all before the dns is resolved, so that it isn't caught
> by the rule that shows the internet unavailable page.
> But that would certainly be a nice feature to add.  I guess it would
> involve some iptables set by the gateway when internet is down.  If the
> gateway doesn't catch the request for dns lookup, at least the firewall will
> and will display the page...
> Or modify the gateway so that the dns lookup request is caught and the
> error page is shown.  Because the code to display the message in situation 2
> and 3 is there, it is just never called...
> Hope this helps,
> Geneviève
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listes.ilesansfil.org/pipermail/wifidog/attachments/20100805/5d4dbb54/attachment.htm>

More information about the WiFiDog mailing list