topic Re: Unable to connect to SSID of R300 in Access Points - Indoor and Outdoor

Unable to connect to SSID of R300

gert_vossius — Sun, 26 Nov 2017 10:45:57 GMT

I bought a Ruckus Wireless R300 from a company who upgraded their wireless infrastructrue.
I'm using this AP to learn Ruckus Wireless so I can start selling Ruckus Wireless products (currently I have experience with Aruba en Cisco Meraki)
Initial setup:
Basic standalone setup with Packet Forward "Local Subnet NAT and Route to WAN", 1 defined local subnet
encyption method WPA2-PSK-AES, even without encryption I'm not able to connect to the SSID.

Ruckus support would/could not help me because this device is not covered under an active support contract (which is normal ... I first would like to learn/experience the Ruckus products before I would like to become a Ruckus Partner).

Does anyone has the same issue in the past? Is this a known bug/problem of is this hardware just faulty?

Re: Unable to connect to SSID of R300

stephan_de_meul — Sun, 26 Nov 2017 10:51:30 GMT

Maybe a firmware isue? I suggest to get an NFR kid from Ruckus trough a reseller. With the stand allone version you dont get a realistic view of the Ruckus product.

Re: Unable to connect to SSID of R300

monnat_systems — Sun, 26 Nov 2017 18:17:36 GMT

well Basic standalone setup with Packet Forward "Local Subnet NAT and Route to WAN", 1 defined local subnet --- under this option, you shall have a DHCP server running in the network.
do u have that ??

Re: Unable to connect to SSID of R300

gupta_pallapot1 — Mon, 27 Nov 2017 03:02:40 GMT

Configuration should be something like this.

Re: Unable to connect to SSID of R300

gert_vossius — Mon, 27 Nov 2017 20:35:16 GMT

Hi all,

thanks for the feedback. The problem was a VLAN id mismatch for the Local Subnet and the LAN interface. I thought that the AP could work in a state where the local subnet vlan ID remained on the AP (afaik like Meraki works).
I switch to bridge mode with all vlan ID on 1 and that worked.
I'm still not able to use the NAT mode (I guess because there's no dhcp running in the network?).