Setup guide

[admin@Wandy] >
Instead of typing ip route path before each command, the path can be typed only once to move into
this particular branch of menu hierarchy. Thus, the example above could also be executed like this:
[admin@Wandy] > ip route
[admin@Wandy] ip route> print
Flags: X - disabled, I - invalid, D - dynamic, J - rejected,
C - connect, S - static, r - rip, o - ospf, b - bgp
# DST-ADDRESS G GATEWAY DISTANCE INTERFACE
0 S 0.0.0.0/0 r 192.168.2.1 1 WAN
1 DC 192.168.124.0/24 r 0.0.0.0 0 LAN
2 DC 192.168.2.0/24 r 0.0.0.0 0 WAN
3 DC 192.168.0.0/24 r 0.0.0.0 0 LAN
[admin@Wandy] ip route>
Notice that the prompt changes in order to reflect where you are located in the menu hierarchy at
the moment . To move to the top level again, type /:
[admin@Wandy] > /ip route
[admin@Wandy] ip route> /
[admin@Wandy] >
To move up one command level, type ..:
[admin@Wandy] ip route> ..
[admin@Wandy] ip>
You can also use / and .. to execute commands from other menu levels without changing the current
level:
[admin@Wandy] ip route> /ping 10.0.0.1
10.0.0.1 ping timeout
2 packets transmitted, 0 packets received, 100% packet loss
[admin@Wandy] ip route> .. firewall print
# NAME POLICY
0 input accept
1 forward accept
2 output accept
3 ;;; Limit unauthorized HS clients
hs-temp none
4 ;;; account auth HS clients
hotspot none
[admin@Wandy] ip route>
Lists and Item Names
Description
Lists
Many of the command levels operate with arrays of items: interfaces, routes, users etc. Such arrays
are displayed in similarly looking lists. All items in the list have an item number followed by its
parameter values.
To change parameters of an item, you have to specify it's number to the set command.
Item Names
Some lists have items that have specific names assigned to each. Examples are interface or user
levels. There you can use item names instead of item numbers.
You do not have to use the print command before accessing items by name. As opposed to