[Chilli] Does chilli keep a cached configuration somewhere?

[Eric Chaves]

Hi folks,

I'm running Chilli server and it has an ip address of 10.1.0.1 (10.1.0.0 is
my subscriber network) and my WAN interface has an ip address of
192.168.1.39. Routes are ok and I can use the internal captive portal fine.

Now, I'd like to move the captive portal to another server at 192.168.1.36
and use the JSON interface to authenticate users. I also would like to
avoid the splash screen and just send user to the logon page.

After reading some docs and digging around, I came to the understanding
that I could it with the following steps:

1) comment HS_UAMSERVER, UAMHOMEPAGE and UAMFORMAT in /etc/chilli/defaults
2) in /etc/chilli/config set the following values:
- HS_UAMUIPORT=80
- HS_UAMSERVER=192.168.1.36
- HS_UAMFORMAT=http://\$HS_UAMSERVER:\$HS_UAMUIPORT/index.html
- Comment HS_UAMHOMEPAGE

After doing those changes in config, I'm manually running chilli (chilli
--debug --fg) but Chilli still serving the portal from it's internal web
server instead of sending users to my external portal. Also the splash page
still being used.

Am I missing something here? Why could this configuration be failing?

Thanks for the help,

Eric.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20140116/9d3431d4/attachment.html>