Static Route & Console Access

Routers
1

I understand ability to add static route is in the roadmap! but is it possible to add via console access temporarily? I have another network device connected to Route 10 interface i would like to add static route to particular subnet managed behind that device! Essentially anything coming from 192.168.1.1 VLAN1 to 192.168.10.0/24 use eth3 port or IP assigned to ETH3 port? Does it make sense?

Also is the procedure for connecting Route 10 via SSH same as connecting to APs? in this KB article:

Thank you!

2

bump!

3

You should be able to do this via CLI with UCI, if it works you can get this into /cfg/post-cfg.sh to survive reboots or control initiated pushes.

Example command set to add static route for 192.168.50.0/24 via 192.168.1.254; change interface lan to what ever interface the other router/device is connected to. YMMW, I haven’t used post-cfg.sh for this use case.

uci add network route
uci set network.@route[-1].target=‘192.168.50.0’
uci set network.@route[-1].netmask=‘255.255.255.0’
uci set network.@route[-1].gateway=‘192.168.1.254’
uci set network.@route[-1].interface=‘lan’
uci commit network
/etc/init.d/network restart

2 Likes
4

thank you I will test it out!
Dummy question how do you SSH route 10 to get access to CLI? Thank you!

5

The KB you posted should do the trick, if you already have SSH keys added under settings->system in control likely those keys are already pushed to your route10. Need someone from Alta to confirm if that is a fair assumption.

1 Like