Dispel’s Wickets have built-in simplified management, to make managing your device easier!

sudo wicket debug is a built-in command that will automatically run tests on the wicket’s connection to the Dispel network and output an explanation of what’s happening, as well as remediation steps.

An example output may look like:

sudo wicket interface configure allows for a guided experience for configuring a wickets interfaces (statically setting IP addresses .vs. DHCP, and setting the default route).

You’ll first be prompted to select which interface to configure:

Next you will be prompted to enter the desired static IP in CIDR notation, or DHCP for this interface. In this example we will be setting the IP to 192.168.1.5 with a /24 subnet mask.

Next you will be prompted to determine the default route. Each wicket can only have 1 default route, and Generally the default route is used on the south facing interface. In this example we will not be configuring the default route.

Finally there will be two confirmation messages. The first applies your changes now, and the second applies your changes to persist on reboot.

Once confirmed, your full current configuration will print to the terminal

To view a wicket’s full routing table you can run ip r

To view routes that are managed by the wicket service (as opposed to the Ubuntu operating system) you can run sudo wicket route show

To add a route run sudo wicket route add

You will be prompted for a subnet, which must be entered in CIDR notation

Next, you will be prompted to enter the gateway for your route

Lastly you will be asked to choose which of the wicket’s interfaces to use for this route. In this example we choose enp0s8

To remove a route run sudo wicket route remove

All routes that are managed by the wicket service will be printed to the screen, and to remove one you simply need to select the number associated with your route.

After selecting, all remaining routes that are managed by the wicket service will be printed to the terminal.