665
edits
Changes
Jump to navigation
Jump to search
Line 193:
Line 193: + + + + + + + + + + + + + + + + + + + + +
no edit summary
(This will change in futur release, firewall customizations for chilli will be done through db commands)
(This will change in futur release, firewall customizations for chilli will be done through db commands)
== Troubleshoot ==
If the contrib doesn't work, check in the order:
*Be sure eth2 is detected
ifconfig -a
If eth2 is not shown, you may need to load the appropriate module
*Check if chilli daemon is running
ps aux | grep chilli
If chilli daemon is not running, try
signal-event chilli-update
If still nothing
/etc/init.d/chilli start
If you get an error, check the log /var/log/messages
*Check tun0 (or what you have configured as tundev) is up, with a valid ip
ifconfig
*Check the client gets a ip in the range 10.1.0.0/24 (or what ever you have configured as net)
If it's not the case, check that the AP is working properly (tcpdump on tun0 to check that your server sees dhcp requests). You can try to connect your client directly to eth2 with a crossed cable to eliminate an AP or wifi-level issue
*Check your client can use DNS. If you get a timeout when you try to open a web page from the client, it's possible that the problem comes from some DNS issue. Try to enter an ip in your browser, even a fake on (http://11.12.13.4/ for example), if you see the login page, then, you should try to configure the DNS of your ISP in the db
db configuration setprop chilli dns1 <ip> dns2 <ip>