[Chilli] Coova when no wan
Xabier Oneca -- xOneca
xoneca at gmail.com
Thu Mar 14 08:01:25 UTC 2013
For HTTPS redirections to work, you need a valid certificate for each
domain you want to be redirected. It would be a huge security hole, so you
cannot do a beautiful HTTPS redirect.
If you don't mind that the user gets a security warning in his browser, you
can use --redirssl with its --ssl* config options to allow CoovaChilli to
listen to HTTPS requests. Chilli does not do this by default. You will need
a (self signed) certificate.
El 14/03/2013 08:50, "Alexandre Rubert" <alexandre.rubert at gmail.com>
> Ok, thank for your answer. I tried with dnsmasq and now all DNS request
> return an IP which is unauthaurized by coova, in that way client is
> redirected to uamhomepage. That's what I want but when client try to access
> to https, he isn't redirected. Wireshark show that client try to access to
> https on the redirected IP but there is nothing matching it.
> Le 14/03/2013 03:39, David Bird a écrit :
>> The problem with there being no WAN is that DNS will not work. Without
>> DNS, you do not get a redirect since the browser times out before making
>> any HTTP request. However, what you can do is use option
>> --domaindnslocal to instruct CoovaChilli to return a 'local' IP for any
>> DNS request under the --domain (so, if you have domain=lan, then
>> hostname.lan would resolve in chilli to a local IP). Typically, DNS
>> systems will attempt the original hostname, then the hostname under the
>> DHCP domain, searching for a result.
>> On Wed, 2013-03-13 at 15:18 +0100, Alexandre Rubert wrote:
>>> I try to configure coovachilli to redirect all client to the uamhomepage
>>> when there is no internet connection. But actually, it doesn't work. Do
>>> you have an example of a kind of configuration ?
>>> Chilli mailing list
>>> Chilli at coova.org
> Chilli mailing list
> Chilli at coova.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Chilli