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

Genevieve Bastien gbastien at versatic.net
Mer 4 Aou 11:23:24 EDT 2010

Hi Jason,

> 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?
Yes it should, it the rule to redirect when internet is not answering is 

> 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 that case, it is as if the dns lookup returned true and the request 
is done, so I guess it should be caught by the gateway.

> In the case of the DNS "catch" would you have to actually return a DNS 
> response to the browser or could you just redirect?
I don't know how feasible it would be to have the router act as a 
catch-all DNS server, so that if any DNS lookup returns unknown, then it 
returns its own address, so that the request can get one step further 
and then be caught by the gateway.

sorry I can't help you very much on this.


> Look forward to your response.
> Regards
> Jason
> On Wed, Aug 4, 2010 at 11:58 PM, Genevieve Bastien 
> <gbastien at versatic.net <mailto: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
>>     <http://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 <mailto:WiFiDog at listes.ilesansfil.org>
>     http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
-------------- section suivante --------------
Une pièce jointe HTML a été nettoyée...
URL: <http://listes.ilesansfil.org/pipermail/wifidog/attachments/20100804/973c0dcb/attachment.htm>

More information about the WiFiDog mailing list