topic Re: DHCP problem with Ruckus 7363 in Access Points - Indoor and Outdoor

DHCP problem with Ruckus 7363

cesar_molina — Tue, 30 Jul 2013 11:55:51 GMT

Hi Everybody.

I have an 7363 and DHCP service doesn ́t assign IP addresses on wireless clients. I upgraded firmware to 9.6.0.0.267 but the problem remains.

Please help.

Re: DHCP problem with Ruckus 7363

ramprakash — Tue, 30 Jul 2013 12:35:22 GMT

Dear Cesar Molina,

Do you see this issue specific to certain type of devices? or all?
Is it something started to occur after you upgraded to 9.6.0.0.267? if yes, what was the last version?

regards

Ramprakash

Re: DHCP problem with Ruckus 7363

cesar_molina — Tue, 30 Jul 2013 13:48:52 GMT

Hi,

the last version was 9.5.1.0.50 with the same issue. I have reviewed quick reference and release 9.4 user guide.

I just have only this model ans it ́s new.

Best regards
César Molina Orihuela

Re: DHCP problem with Ruckus 7363

cesar_molina — Tue, 30 Jul 2013 18:09:03 GMT

Hi,

i found this log:

.info dnsmasq[2195]: set CAP2 ok
Jul 26 13:33:29 RuckusAP daemon.info dnsmasq[2195]: started, version 2.33 cachesize 150
Jul 26 13:33:29 RuckusAP daemon.info dnsmasq[2195]: compile time options: IPv6 GNU-getopt no-ISC-leasefile no-DBus no-I18N
Jul 26 13:33:29 RuckusAP daemon.info dnsmasq[2195]: DHCP, IP range 192.168.40.100 -- 192.168.40.120, lease time 1d
Jul 26 13:33:29 RuckusAP daemon.warn dnsmasq[2195]: no servers found in /etc/resolv.conf, will retry
Jul 26 13:33:29 RuckusAP daemon.info dnsmasq[2195]: read /etc/hosts - 1 addresses
Jul 26 13:33:29 RuckusAP daemon.info dnsmasq[2195]: exiting on receipt of SIGTERM

Re: DHCP problem with Ruckus 7363

keith_redfield — Tue, 30 Jul 2013 19:12:06 GMT

Hi Cesar,

Can you tell us - did it *ever* work - if so, what changed between the time it did and didnt?

If it never worked, it's more than likely configuration related. Can you post a screenshot of the AP configuration screen (showing the address range, etc) and also tell us a little about your network? That should help with progress.

You might try a hard-reset of the AP if you don't mind reconfiguring. That set of logs you posted is a little suspect.