Wireless Access

Hello,

i usually access the webadmin of the ARUBA IAP from a wired PC in Vlan 10

but when i want to access webadmin from a wifi client PC which is in the same Vlan (10) (same IP subnet)

there is no way i can reach the page, i can simply PING, this is it.

i'm pretty sure there is no problem in IPV4 policy on the firewall till it work on a wired PC on the same vlan/subnet.

any clue of what's going on ?

thanks

What is the admin vlan of the IAP?

the IAP on itself is not vlan aware.

when the ap try to communicate on the network its getting assigned to vlan 99 by a switch.

Can you put  a wifi client on vlan 99 (1 on the iap) and try to access to gui?

i created a new ssid with vlan setting = default.

i puted a static ip on the PC in the same subnet of the management IP of the IAP.

and i succesfully connected to webadmin wirelessly.

when i look on my firewall. i can see packets that being send by a wired PC and wireless PC and being treated the same way when trying to reach the IP of the controller. for the wireless PC there is "timeout" writen. looks like the AP just don't want to answer.

my switch won't carry VLAN 99 upon the trunk, and i can't mess with that now.

alright, i found a way to solve the issue,

i activated NAT between vlan 10 and management Vlan.

so when the client try to reach the web admin, the traffic flow inside the vlan 10 and then the packets are sent throught the management vlan to catch the AP, packets are nated with the ip adress of the management vlan 's gateway.

And now it works,

the explanation might be this :

till the source ip of the host client is known inside the aruba AP.

client send frame through the AP to the firewall to reach the gateway.

then the packets goes into the management vlan to the AP.

the Ap match an ARP entry coresponding to the client PC and send the packet directly to the PC, Which mess up totally the TCP session and connection does not occur.

that could explain why this is now working thanks to NAT.

thank you for your help :)