Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Wifi client unable to ping it's default gateway

This thread has been viewed 5 times
  • 1.  Wifi client unable to ping it's default gateway

    Posted Mar 08, 2016 07:02 PM

    I have a 7210 controller configured with 3 VLANs.  VLAN 1 for AP's and infrastructure, VLANs 2 and 3 for wireless clients. 

    Client device successfully authenticates, receives "authenticated" role, and gets an IP address, however I cannot ping the default GW from the client device, nor can I ping the client device from the controller; either with a default ping or sourcing the vlan.  IP routing is enabled on the vlan interface.

     

    Any ideas?/



  • 2.  RE: Wifi client unable to ping it's default gateway

    Posted Mar 08, 2016 07:39 PM
    Can you ping that default gateway from the controller ?



    Sent from Outlook for iPhone


  • 3.  RE: Wifi client unable to ping it's default gateway

    Posted Mar 09, 2016 10:32 AM

    Yes I am able to ping the default gatewasy from the controller.  It is really strange, it just seems that the controller is not properly switching the traffic.  Because my client device is within the same VLAN the traffic should never leave the controller.  I even tried connecting a second client device and pinging between to two clients; that was unsuccessful also.

     

    Thoughts?



  • 4.  RE: Wifi client unable to ping it's default gateway

    EMPLOYEE
    Posted Mar 09, 2016 10:46 AM

    What is the output of "show rights authenticated"?

    In your Virtual AP settings, are you blocking communication between users?