Wireless Access

last person joined: an hour ago 

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

RAP wired port Trunking issue

  • 1.  RAP wired port Trunking issue

    Posted May 08, 2019 04:10 PM

    So I am working on a RAP155 and I have my port configuration profile all set up. I am trunking six VLANs across it for testing and it works. The trunked port on the RAP155 is connected to a trunked port on an old Cisco 3750 and and I can break out the VLANs onto different access ports and can ping back to the controller and even have Internet access through the tunnel. Happy happy joy joy!


    The problem is that there is cross VLAN communication and I don't want that. So I go into each VLAN IP INTERFACE configuration on the controller and DISABLE Inter-VLAN Routing (you know, UN-check the little box) and yet I can still ping across VLANs. Not cool.


    Side note, all of the VLANs in question "live" on the controller


    Anyone have any insight?





  • 2.  RE: RAP wired port Trunking issue

    Posted May 08, 2019 11:16 PM

    No Inter VLAN Routing, means that that client cannot use the ip interface of the controller to route traffic to other subnets.  If the client's default gateway is not the controller, that enforcement will not take place.


    This was designed to protect against clients changing their default gateway to a controller ip interface in order to circumvent traditional routing.

  • 3.  RE: RAP wired port Trunking issue

    Posted May 09, 2019 08:06 AM

    Hey CJ, to clarify, I am using the controller IPs of these vlans for the gateways for the test clients. There is no DHCP, everything has to be set statically.


    That's why I thought disabling inter vlan routing would stop the cross vlan communication. Yet, it is still happening. See my confusion?