Ruckus 7363 cannot get DHCP lease

  • 1
  • Question
  • Updated 4 years ago
  • Answered
Bought a Ruckus 7363 for use as a standalone WAP. I can connect to the 7363 via wireless, but the unit does not connect to my LAN. It is plugged into a WatchGuard hardware firewall with IP address 192.168.16.1. The firewall is also my DHCP server. There is a server on the network with IP address 192.168.16.2 (that is also the DNS server address). Do I need to change the default internet configuration on the 7363? I checked the DHCP leases on the hardware firewall and the 7363's MAC address was not listed, so I assume it has no lease. Thanks.
Photo of Geb Blum

Geb Blum

  • 6 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
Did you configure the AP or was it somehow pre-configured? As-shipped, the APs are not set for standalone operation and you have to configure them. Log into the AP via an ethernet cable as outlined here: https://support.ruckuswireless.com/do...
Photo of Geb Blum

Geb Blum

  • 6 Posts
  • 0 Reply Likes
I configured it as per Ruckus instructions with a 192.168.0.1 connection on a laptop and followed the instructions. Everything on the configuration seemed to work fine. I suspect I need to enter some default gateway information (192.168.16.1 on my system) or a preferred DNS server (192.168.16.2 on my system). I can't figure out if I need to assign a static IP address to the AP to do that. I'm sure the Ruckus is working on wireless connections- just not to the network.
Photo of Jelle Alten

Jelle Alten

  • 60 Posts
  • 12 Reply Likes
Can you use ssh to go into the device?

If you do that, you can enter:
set ipaddr wan dynamic
and
reboot

After that you will lose connection to the device, and it will reboot and ask your dhcp server for an address. Check the logs of the dhcp server to see what address it got.

Of course, this could also be done using the web ui, but this way was easier to explain.

Hope it helps.
Photo of Geb Blum

Geb Blum

  • 6 Posts
  • 0 Reply Likes
Thanks, but I'm not familiar with secure shell. The only access I can get to the configuration page is via the setup instructions for the 7363 on a laptop. Once it is connected to my LAN, I can't ping it at 192.168.0.1 nor does the device appear in my DHCP server's lease logs (I searched by MAC address), so I assume it may not be able to locate the DHCP server.
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
The only way that would occur is if you don't actually have L2 connectivity. Are you using VLANs?
Photo of Jelle Alten

Jelle Alten

  • 60 Posts
  • 12 Reply Likes
Perhaps you can try to see what happens when you connect the AP to a different network with a different dhcp server? Like the network at the neighbor? Or to a stand-alone router? It it gets an IP address there, your AP is fine and your network setup might require some tweaking, as Keith suggested...
Photo of Geb Blum

Geb Blum

  • 6 Posts
  • 0 Reply Likes
Not using VLANs.
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
We are missing some vital piece of information. This is the easiest possible configuration and should "just work" if you followed the install guide. All of the possible errors I can think of would be outside the AP (such as..duplicate IP, overlapping DHCP scopes, bad port negotiation, etc)
Photo of Geb Blum

Geb Blum

  • 6 Posts
  • 0 Reply Likes
I did follow the guide. As I described before, my hardware firewall is the LAN's DHCP server. I have an SBS 2011 server running on the network that is the DNS server (not the DHCP server). The hardware firewall is 192.168.16.1 and the DNS server is 192.168.2. The 7363 is plugged into an available Ethernet port on the hardware firewall. The 7363 detects wireless signals from client sources fine.
Photo of Jelle Alten

Jelle Alten

  • 60 Posts
  • 12 Reply Likes
I'm curious to see what happens in a different LAN. I agree with Keith that this looks like something outside the AP, even a DHCP running out of leases or IP addresses could cause this problem.
So if you can, see if you have access to a different LAN somewhere (home/work/neighbor/lab/friend/school) that has DHCP as well, and see if you experience the same symptoms. At least that will give a hint if it is the AP or the network.

Good luck and keep us posted.
Photo of Geb Blum

Geb Blum

  • 6 Posts
  • 0 Reply Likes
I found the problem. The Ethernet ports on the WatchGuard firewall are enabled/disabled on the unit's configuration page. When the firewall was installed, the unused ports were disabled. I switched the 7363 to another port and it worked fine. Sorry to waste your time on this. I had to get an IT guy to configure the firewall, and the thing has been a bit of a mystery to me. I found the disabled ports by checking the WatchGuard configuration files.
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 51 Reply Likes
I love a great mystery! (when it's over...) :)