Topic: db commands for CoovaChilli

[jumba]

Hello everybody!
 
 I need some help on this one:
 
 I'm setting up a test server using http://wiki.contribs.org/CoovaChilli where I want to change the uamhomepage to 10.1.0.1
 
 Executing the commands
 
 

Code: [Select]

db configuration setprop chilli uamhomepage 10.1.0.1
 results in the error message "URL must start with http:// ......."

Trying with

Code: [Select]

db configuration setprop chilli uamhomepage http://10.1.0.1 give the same error message...

(BTW, 10.1.0.1 is an allowed URL from the hot-spot-interface, and it is accessible....)
 
 Please someone:
 
 What is the correct syntax to change that parameter so that it changes to 10.1.0.1 ???????????
 
 I really urgently need to sort this out........
 
 Thanks in advance!!!
 
 //Lasse

[cactus]

Executing the commands
 
 

Code: [Select]

db configuration setprop chilli uamhomepage 10.1.0.1
 results in the error message "URL must start with http:// ......."

I find that hard to believe, db commands do no checks like that, they only check if the syntax of the command is correct. You must have observed that error somewhere else. Please be complete when describing your situation, this seems like cutting corners.

[jumba]

No of course not, sorry for trying to cutting corners 

Here is the complete session:

Code: [Select]

[root@server ~]# db configuration setprop chilli uamhomepage http://10.1.0.1
[root@goodnet ~]# signal-event chilli-update
This should actually be enough, but now cchilli doesn't seem to work properly (dhcp doesn't lend out any IP to clients for example) so I close the service and start it up again:

Code: [Select]

[root@server ~]# service chilli stop
Stopping chilli:                                        [FAILED]
[root@server ~]# service chilli start
Starting chilli: coova-chilli[5208]: options.c: 142: URL must start with http:// or https:// +2dT5bhJGxTZLPfvCEpX/GpT+J9w1Q/566yLVTCzG2QB40VS6emmAF5bioKmGYsymc9fFjxBLaGZY776!
coova-chilli[5208]: options.c: 414: Failed to parse uamhomepage: +2dT5bhJGxTZLPfvCEpX/GpT+J9w1Q/566yLVTCzG2QB40VS6emmAF5bioKmGYsymc9fFjxBLaGZY776!
                                                           [FAILED]

In that moment, the db for chilli looks like this:

Code: [Select]

[root@server ~]# db configuration show chilli
chilli=service
    AllowedOutgoing=tcp:any:443
    TCPPort=3990
    WebRequests=direct
    access=private
    defidletimeout=900
    defsessiontimeout=60
    dhcpend=254
    dhcpif=eth2
    dhcpstart=10
    dns1=212.73.209.226
    dns2=194.206.120.1
    guestAccess=enabled
    guestDownLink=64
    guestUpLink=64
    net=10.1.0.0/255.255.255.0
    noc2c=enabled
    status=enabled
    tundev=tun0
    uamallowed=tcp:www.something.com:80
    uamhomepage=http://10.1.0.1
    uamsecret=+2dT5bhJGxTZLPfvCEpX/GpT+J9w1Q/566yLVTCzG2QB40VS6emmAF5bioKmGYsymc9fFjxBLaGZY776
Well, for the time being, I would be just happy to hardcode the default startpage to 10.1.0.1 instead of the default 10.1.0.1/chilli but I haven't even found where that value is set.....

[jumba]

Update. I have been in touch with Daniel (VIP-ire) who confirmed that this indeed is a bug.

He will release a fix for this soon....