I have read the reply from Ruckus Support said “With revision 4.1 firmware, you can not manage 2925 wirelessly. You will have to manage it from WAN port side.”

Mine is ZF-2925-EU (S/N:ZF10000497) with software version gd6-5 4.1.0.29. Here is the environment, I plug my notebook UTP to 2925 LAN port #1 by using UTP cable (wireless on notebook is off). The IP of LAN interface on notebook is fixed at 192.168.0.31 (2925 is default – 192.168.0.1).

If I power on 2925, after the device started up, then I plug in the UTP cable. I will not be able to ping 2925’s IP. And yes, cannot open its web config page.

But if I plug the UTP in first, after that power on the 2925. Once startup finish, I will be able to ping and open web config page.

This is repeatable and never miss. Even now I still do confirm that I have 2925 web config page aside without my wireless turned on and my UTP cable is on 2925 LAN port 1. My notebook does not support any 802.1Q feature of VLAN tagging.

Does Ruckus Support confirm this habit ? Is it intentionally as is, or it has to be fixed ?

Sorry, my last dialog which I said the wireless was turned on. Actually, it was turned off.

I wonder that this is about what so called Profile ? I am not sure now about the condition to reach the 2925 web config page might conditionally depends on the loaded profile. Or it is by the common rule.

All Ethernet ports belong to the Management VLAN (51), so if the wired station you’re plugging into the AP has a static IP in the same subnet as the AP (or is assigned an IP address from an external DHCP server in the same subnet as the AP), then you will be able to ping the AP and/or manage it by opening the Web UI from that station.

I notice you are using an older software version on the AP. The currently supported version is 4.1.0.96. Connect your AP to the Internet (using port 5) and try to upgrade it using the Web UI. Or download the software from http://support.ruckuswireless.com/software/for_… and use your own FTP/TFTP server to upgrade the AP.

I accidentially plug the device to the LAN which has DHCP and internet connection running and I saw the device upgrading itself the new version of firmware (4.1.0.96). Then I started to discover more and I have found the following conditions.

- Once the 2925 turned on, it will keep looking for DHCP server by sending DHCP discover packet to all active LAN ports. - If DHCP is not found. Device will be using 192.168.0.1 - Once the DHCP server is found. 2925 IP address will be as assigned by DHCP server.

I hope this information would help to all those plug the 2925 to their LAN with DHCP server running and try to access the device by 192.168.0.1.