07-14-2014 03:57 AM
I'm experiencing a strange issue with an Ubiquiti client used as a client (station) to connect 2 wired devices to the wireless network.
My Aruba network setup is composed by ad Aruba Controller 3400 with 126.96.36.199_44205 firmware on it, and a mix of 92 and 175 CAP APs, all of them configured to use 2.4GHz radio.
My Ubiquiti Wireless client is statically associated to a 175 CAP.
On the Ubiquiti side, I have the Ubiquiti wireless client linked to a little switch, and on the same switch I have 2 IP Phones connected.
My problem is that if I enable "WDS Transparent mode", that is the option to tell at the client station to let pass wired device's mac addresses untouched, I can talk with the Ubiquiti wireless client, but I can't contact wired devices behind the wireless client.
As opposite, if I disable this feature, my wired devices seems to be reacheable, but I notice that on the controller they're all presented with the same mac address (the mac address of the ubiquiti wireless client) and I need to avoid this condition.
Now, I know that is possible that the problem is on the Ubiquiti side, but, using this setup with another type of AP, it seems to work fine without any problem, so I want to tell You if there are any options on the controller's configuration that maybe block or interfere with the Ubiquiti client normal operation.
Thanx a lot in advance for support!
07-14-2014 04:29 AM
In the Virtual AP profile on the controller for that SSID, please consider disabling "Convert Broadcast ARP requests to Unicast"
"Starting with ArubaOS 188.8.131.52, the Convert Broadcast ARP requests to unicast setting includes the additional functionality of broadcast-filter all parameter, where DHCP response frames are sent as unicast to the corresponding client. This can impact DHCP discover/requested packets for clients behind a wireless bridge and virtual clients on VMware devices. Disable this option to resolve this issue and allow clients behind a wireless bridge or VMware devices to receive an IP address."
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
07-14-2014 05:32 AM
Thanx a lot for quick reply. :smileywink:
Unfortunately I already tried this trick but the situation did not change.
I also tried to enable "FDB Update on Assoc" feature and also tried to disable HT mode for this SSID in order to force Wireless Client to operate in legacy G mode.
Sadly, none of those modifications did the trick!
07-15-2014 05:18 AM
As suggested by Aruba, I'm trying to configure an iAP as wireless client, but I can't find the correct procedure to accomplish this task.
I tried to configure WiFi uplink, as shown in the manual, and enforced wifi uplink, but the WiFi uplink status remains as
And show uplink status says that wifi uplink is in "INIT" or in "LOAD" state...
Anyone has some suggestions?