Wireless Access

Reply
New Contributor

VIA client subnet access issue

I have little experience setting Controller (Aruba 620 with 6.0.1 firmware) but I could get VIA client authenticate with the controller. However I had an issue where the LAN subnet is not advertise and not reachable from VIA. Attached is the simple network sketch showing you that the controller is placed in DMZ network.

 

Once VIA authenticated with controller, it received 172.16.100.50 from the DHCP pool. It can never reach the web server in LAN port 4 subnet (which is 172.16.1.50). When I check VIA client route table, the subnet 172.16.1.0/24 is not injected into OS so I manually add it myself but not working either.

 

Does anyone have clue with this issue?

 

Thanks in advance.

 

 

 

Guru Elite

Re: VIA client subnet access issue

Your infrastructure would need a route for 172.16.100.0 pointing to the management interface of the controller.   Optionally, the controller would need a VLAN interface in the 172.16.100.0 subnet, as well.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: