Let us first take a look at the CLI. You'll find that it looks just like a Debian based server.
Let's cover some basic commands first. First it is important to know how to get help in de CLI. You can type ? and a list of all possible commands will show up. It is also possible to write that in command you are currently typing which will show all possible completions. (Please note that the ? is not shown in the console).
Now lets list some basic commands:
Instead of writing the command in full you can always write a shorter version of it that is specific enough to know what it means. For example, instead of writing "show interfaces" you can write "sh int" or "sho interf". Both commands are unique enough to link them with the full command. |
You have two methods for configuring the WAN side. Either via DHCP or manually, however since we do not have DHCP on our subnet you will need to configure it manually.
The first thing you will need to do for both is to identify your WAN-interface. You can see al interfaces by typing "show interfaces"
set interface ethernet ethX address '?.?.?.?/CIDR' # For example: set interface ethernet eth0 address '193.191.187.104/28' |
And to make it clear that it is WAN we will give it a description:
set interfaces ethernet eth0 description 'WAN' |
If you now type "show interfaces", you should get something like this:
+ethernet eth0 { + address 10.0.0.239/24 + description WAN +} loopback lo { } |
That is done, however we are missing one big important thing. If our router receives a request from outside our network, it will have no idea where to send the response. Obviously we need to set our default route to our gateway.
set protocols static route 0.0.0.0/0 next-hop 193.191.187.110 |
Double check everything and then write "commit-confirm". If anything went wrong wait 10 minutes. The system will restart to it's previous configuration.