Posted: Thu Feb 04, 2016 13:18 Post subject: Chillispot not assigning IP address on WAN
I am using the Firmware: DD-WRT v3.0-r28882 std (01/19/16) on TpLink 841n V 10.
The internet and IP Address on the WAN port is provided by a DSL Router at the back and the DDWRT router is successfully able to lease the IP Address.
I am using the following NVRAM commands to set up an internal private network and subnet on the LAN.
nvram set wan_proto=dhcp
nvram set wan_hostname=My_Host
nvram set router_name=My_Router
nvram set lan_ipaddr=192.168.40.1
nvram set lan_netmask=255.255.255.0
nvram set lan_proto=dhcp
nvram set dhcp_start=100
nvram set dhcp_lease=1440
nvram set ath0_ssid=My_SSID
nvram set ath0_key=1
nvram set ath0_crypto=aes
nvram set ath0_security_mode=psk
nvram set ath0_akm=psk
nvram set ath0_wpa_psk=mypassword
nvram set ath0_radio=1
After this I am able to broadcast my SSID successfully and the internet works without any problem. The clients of the router are able to lease the IP address in the range of 192.168.40.x.
The snapshot of the running processes looks like:
PID USER VSZ STAT COMMAND
684 root 1120 S dnsmasq -u root -g root --conf-file=/tmp/dnsmasq.conf --cache-size=1500
759 root 1332 S ttraff
764 root 2064 S startstop_f run_rc_startup
810 root 1532 S resetbutton
839 root 1756 S httpd -p 80
968 root 1332 S process_monitor
972 root 1556 S wland
973 root 1128 S udhcpc -i eth0 -p /var/run/udhcpc.pid -s /tmp/udhcpc -O routes -O msstaticroutes -O staticroutes -H My_Host
987 root 900 S cron
1005 root 1132 S -sh
1007 root 1128 R ps
WAN IP: 192.168.1.30
The problem starts as soon as I enable chilli spot on the LAN interface.
I disable dnsmasq, localdns and DHCP running on the DDWRT router as:
nvram set dhcp_dnsmasq=0
nvram set dns_dnsmasq=0
nvram set auth_dnsmasq=0
nvram set dnsmasq_no_dns_rebind=0
nvram set dnsmasq_strict=0
nvram set dnsmasq_add_mac=0
nvram set local_dns=0
nvram set dnsmasq_enable=0
Then I add the following commands to enable chilli spot:
nvram set chilli_interface=lan
nvram set chilli_enable=1
nvram set chilli_backup=xx.xx.xx.xx
nvram set chilli_uamanydns=0
nvram set chilli_radius=xx.xx.xx.xx
nvram set chilli_macauth=0
nvram set chilli_radiusnasid=my_nasid
nvram set chilli_url=xx.xx.xx.xx
nvram set chilli_pass=5qwx6eFYcx
nvram set chilli_802.1Xauth=0
nvram set chilli_net=192.168.182.0/24
nvram set chilli_uamsecret=TcuqTRmbm5
nvram set chilli_macpasswd=password
nvram set chilli_dns1=220.127.116.11
The masked addresses are actual addresses and urls so ignore that please.
Aft enabling chllispot the clients are not able to lease IP address in the range of 192.168.182.X as I can see the IP address in the 192.168.40.x range.
The running processes are:
188 root 0 SW< [deferwq]
436 root 924 S /sbin/hotplug2 --set-rules-file /etc/hotplug2.rules --persistent
477 root 1576 S watchdog
522 root 0 SW< [cfg80211]
579 root 1532 S resetbutton
637 root 1664 S hostapd -B -P /var/run/ath0_hostapd.pid /tmp/ath0_hostap.conf
676 root 1136 D telnetd
680 root 900 S cron
686 root 1556 S wland
688 root 904 S udhcpd /tmp/udhcpd.conf
690 root 2060 S startservice wan_boot -f
775 root 1028 S chilli --statedir=/var/run/chilli1 --pidfile=/var/run/chilli1/chilli.pid -c /tmp/chilli/chilli.conf
779 root 2176 S httpd -p 80
808 root 1028 S chilli_opt --statedir=/var/run/chilli1 --pidfile=/var/run/chilli1/chilli.pid -c /tmp/chilli/chilli.conf -b /var/run/chilli1/chilli.775.cfg.bi
I can also see that after enabling chilli spot the WAN interface does not get an IP address. I think this is happening because udhcpc is not running.
This is quite weird as all the setup guides for chilli spot and ddwrt claim that this should work with just a few commands. I am really keen to find the resolution for this as I am unable to proceed because of this issue.
Joined: 24 Feb 2013 Posts: 1504 Location: Belgrade
Posted: Sun Feb 28, 2016 20:12 Post subject:
I don't know. I didn't found any workaround anyware. This bothers me a lot because I am not sure if this is a bug or misconfiguration... And this has been for a year almost... last working build 22188 or similar...
Yea, weird thing is i have two of these routers, one v9 and one v10, same issue on both. Do you have any idea in which build does chillispot work as it should? doesnt matter if its for v9 or v10, just need to get it working.