Setting Up Anonabox as Guest Network

Using the Anonabox to create a guest network is an easy way to share Internet access to visiting guests without giving them access to your local network. This could be implemented at home or in a business where Wifi is desirable like a cafe.

The first thing we should do is to reconfigure the admin interface to be accessible only from the WAN side, so there is no way customers can access the device from the part of the network they connect to. This assumes that you have already set an admin password for the device itself, and are running the latest firmware.

In order to access the interface from the WAN side, you will need to make configuration changes in two places. First , you will need to get the WAN ip address of the Anonabox. You can do this by logging into the interface and then clicking on the status dropdown menu and then selecting 'Overview' from the list of links. The WAN ip address will be listed next to WAN status like so:

In our testing setup here, the WAN ip address is

Write that down or copy/paste it into a text file for later.

Next thing we will need to do is open up ports on the WAN side of the firewall in order to allow the traffic to the admin interface from the WAN side through. To do this click the 'Network' dropdown menu, then select 'Firewall' , then on that page click the tab named 'Traffic Rules'. On that page, scroll down to where it says 'Open Ports on router:“ The name will be wanuhttpd1776, Protocol is TCP, external port is 1776. After you type in that info click the button to the right of that that says 'Add' , then scroll all the way down to the bottom of the page and click the blue button named 'Save and Apply'.

Now that you have a port open on the device for 1776, you need to change uhttpd to listen on the WAN port. To do that, go to the “Services” dropdown menu at the top, then from the dropdown menu select “uHTTPd”.

On that page you will see a few different settings. You will need the ip address that you got for the WAN in the first step, in our case here ours is but yours will probably be something different. What you need to do is change every instance where you see the old listening address: to the new one. If you are running the most recent firmware on the Pro model, there are three places to change it. You may notice there is a number after the ip address, in the first one for example the default setting is You will want to keep the colon and the number 1776.

In our test case here we changes the first HTTP listener field from to

And made the same changes to the other two places where the original ip address appeared.

After that, we scroll down to the bottom of the page and click the blue 'Save and Apply' button. It takes a few seconds for the changes to be allpied, but afterwards we are able to access the admin interface from the WAN by going to the IP address

Here is a pic of the uHTTPd page we used for reference:

After you make these changes you will need to restart the device for the changes to take effect. Or, if you are handy at the command line you can just manually restart the uhttpd daemon with this command: /etc/init.d/uhttpd restart

Once that has taken place, you will be able to access the device's admin interface only from the WAN side, which should be the portion of the network your other devices are using.