WLC gui/ssh inaccessible outside its subnet

[anon3776]

I can’t access the WLC through GUI or SSH from its configured IP from outside its subnet. It can only be accessed from the same subnet with WLC’s management/WLAN IP.

WLC IP:

10.1.1.1/24 Mgmt

Clients from 10.1.2.0/24 can ping 10.1.1.1 but cannot access GUI/SSH, only clients from 10.1.1.0/24 can access GUI/SSH.

Right now I use mgmt via dyn interface for temporary workaround for flexibility, but I wanna access the WLC from other subnets because we have VPNs to other sites.

[Scott Fella]

If you are trying to access the controller from a subnet defined as a dynamic interface, you need to issue the command.  If you are trying to access the controller from a subnet that is not defined on the controller, you should be able to without that command. 

-Scott 

*** Please rate helpful posts *** 

[anon3776]

Does it mean I need to disable the mgmt via dynamic interface first so that I'm able to access the controller from subnet that is not defined on the controller?

[Scott Fella]

If you are trying to connect to the controller from a subnet that isn't defined on the controller from a wired connection, you shouldn't need anything checked. Mgmt via wireless or dynamic states a wireless client able to get to the mgmt of the controller.  Has nothing to do with wired.  I don't know how mgmt via dynamic interface is helping if that subnet doesn't overlap any subnets defined on the controller.

-Scott 

*** Please rate helpful posts *** 

[anon3776]

Ok so this might be a bug or something as I'm not able to access the controller from another subnet. All of the controller's IP are pingable from other subnet, but to access the GUI/SSH I need to be in the same subnet as the controller's IP. Really weird.

[Scott Fella]

What code are you running and what controller?  If you have mgmt via dynamic interface enabled and that works, we know that there are no acls blocking, so it can be a bug. 

-Scott 

*** Please rate helpful posts ***