Having no GUI means it's a bit harder to configure and not that easy to see the whole complete outcome, however it will teach you more about the actual networking than a GUI does and you have another reason to break something.
Table of Contents
How does the CLI work?
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:
- clear console: clears the console screen
- show ?: show information about x
- configure: enters privileged mode. In this mode you can make changes to configuration. You will know that you are in configuration mode if the path prefix changes from "~$" to "#".
- set: set/add option x.
- commit-confirm: activate the changes you have made. It will activate the changes and THEN ask you for confirmation. This means that if something breaks and you lose access it will automatically restart (by default in 10 minutes). So make sure you wait a minute before confirm so you can actually test if the system works. Perhaps open a new SSH connection to see if you can still access the console (an open connection is not the same as opening a new connection!). Must be run in privileged mode (aka configure).
- save: save the committed changes into the boot file. Running just commit is not enough, it will not be saved when the system reboots. Use this to permanently save it. Must be run in privileged mode (aka configure). Only run after commit-confirm!
Obviously you don't want to type everything in the VNC. To enable SSH simply enter
Please be aware that this will open the SSH server on all interfaces! If you want this edit the SSH port and only allow logins via an SSH Key. Otherwise the router could get compromised rather quickly!
Configuring your WAN-interface
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"
And to make it clear that it is WAN we will give it a description:
If you now type "show interfaces", you should get something like this:
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.
Double check everything and then write "commit-confirm". If anything went wrong wait 10 minutes. The system will restart to it's previous configuration.
- No labels