Navigation
Cisco WLAN controller 4400 and dhcp relay
Hello everyone!! I hope you are fine!!
I have a problem with coova-chilli 1.0.13 and i will be so gratefull for anyone find a solution.
I use a cisco WLAN controller 4400 with vlans configured. in order to transmit dhcp requests in that vlan, cisco has a dhcp relay.
the problem is that before transmit dhcp requests to chilli, the cisco controller does an ARP request to chilli.
Chilli reply, but the cisco controller doesn't like this answer.
In fact, when chilli reply, in the ARP target address field, chilli put 0.0.0.0 instead of the cisco controller ip address. It send the ARP reply in broadcast mode.
So, the cisco controller send an ARP request again and again...
here is the cisco request:
here is the reply
chilli arp reply
Anyone has an idea to correct this in chilli or in the cisco controller.
thank you to all of you!!
- Login to post comments
Refurbished Cisco equipment
I just bought a used Cisco equipment. I think it's the same WLAN version. I hope I don't encounter any problems. My techie friends recommend Cisco since it's a trusted brand.
I would like to be able to do
I would like to be able to do this too.
Please post if you have gotten an answer to this.
Cisco WLAN Controller 4400 and dhcp relay
Hi everyone,
so, I have resolved my problem with my cisco WLAN controller 4400 and his famous dhcp relay.
In order to my cisco understand where chilli is, I had a command in the chilli crontab which is executed every minutes.
In fact, Instead of my cisco controller ask me who chilli is, Chilli ask him before who cisco is.
the command is: arping -b -c 2 -I eth1 -s 192.168.172.1(chilli) 192.168.172.2(cisco)
then, cisco controller had chilli mac adress and ip in his arp table. then, he answers chilli who he is.
When it is done, cisco transmit dhcp requests.
the chilli arp entry in the cisco table is available during 300 seconds.
So, I hope that the problem will be resolved in the future chilli 1.0.14, but now we have a solution.
I would like to seek some
I would like to seek some clarification :-
the command : arping -b -c 2 -I eth1 -s 192.168.172.1(chilli) 192.168.172.2(cisco)
in there the in 192.168.172.1 is the uamlisten address and hence
the tun IP address ? ( Usually the dhcp interface IP address is cleared when
running chilli, or is it that you are keeping the IP address of the DHCP interface
when running chilli ) ?
chilli configuration
HI,
192.168.172.1 is both the uamlisten address and the tun address.
here is my /etc/chilli/default.conf file:
HS_WANIF=eth0 # WAN Interface toward the Internet
HS_LANIF=eth1 # Subscriber Interface for client devices
HS_NETWORK=192.168.172.0 # HotSpot Network (must include HS_UAMLISTEN)
HS_NETMASK=255.255.255.0 # HotSpot Network Netmask
HS_UAMLISTEN=192.168.172.1 # HotSpot IP Address (on subscriber network)
HS_UAMPORT=3990 # HotSpot Port (on subscriber network)
HS_DYNIP=192.168.172.128/25
HS_DYNIP_MASK=255.255.255.128
HS_STATIP=192.168.172.0/25
HS_STATIP_MASK=255.255.255.128
HS_DNS_DOMAIN=chillispot
HS_DNS1=10.181.208.74
HS_DNS2=10.181.208.44
HS_NASID=sls-gwwifi01
HS_UAMSECRET=XXXXXXXX
HS_RADIUS=127.0.0.1
HS_RADSECRET=XXXXXXX
HS_UAMSERVER=192.168.172.1
HS_UAMFORMAT=https://\$HS_UAMSERVER/cgi-bin/hotspotlogin.cgi
HS_UAMHOMEPAGE=http://\$HS_UAMLISTEN:\$HS_UAMPORT/www/coova.html
HS_UAMSERVICE=https://coova.org/app/uam/auth
HS_ANYIP=on
HS_DEFIDLETIMEOUT=30
HS_MODE=hotspot
HS_TYPE=chillispot
HS_POSTAUTH_PROXY=192.168.172.1
HS_POSTAUTH_PROXYPORT=3128
HS_WWWDIR=//etc/chilli/www
HS_WWWBIN=//etc/chilli/wwwsh
HS_PROVIDER=Coova
HS_PROVIDER_LINK=http://www.coova.org/
HS_LOC_NAME="Hot Spot SLS" # WISPr Location Name and used in portal
HS_LOC_NETWORK="Hot_Spot_SLS" # Network name
HS_LOC_ISOCC=FR # ISO Country code
HS_COAPORT=3799
I hope that I answer good to your question.