@Herman Robers wrote:
I don't think so. Also, I would prevent such network requirements and put the IAPs on a subnet with just that IAPs and your router so everything is reachable through the default gateway. Having static routes on systems is something I would avoid at all cost as it is likely to introduce unpredictable things like asymetric routing. I would change your network and routing design instead.
Also, I think there is a typo in your example as both the route and the gateway are in the same subnet; but if the route is for another subnet, having it just in your .254 default gateway may be enough (if it is not a stateful firewall).
Hi Herman,
We have already been able to configure the routes in an IAP successfully, if it is possible to configure the IAP, the design had to be changed. However, if we try to configure the route on the gateway, only this did not work as expected.
The solution was to configure the routes directly in the IAPs from ArubaCentral. The reason for doing it this way is because the solution had to adapt without making changes to the current network. A very particular case.