(this version requires you to upload this file two times) Download
1) Click the “Download” button in the Firmware box to download to your computer the latest available firmware for your router.
2) Disconnect your PC from the internet.
3) Using an Ethernet cable, connect your computer to the LAN port of the router, open a web browser and log into the web interface (type 192.168.11.1 into the URL field).
4) Navigate to Administration -> ‘Firmware Upgrade’ and click ‘Choose File’.
5) Navigate to the firmware file you downloaded in step 1 above and select it.
6) Click the ‘Upgrade’ button.
7) After the file is uploaded, the router will display a confirmation message.
8) Wait for the router to apply the firmware update.
9) Once the firmware file has uploaded, the router will reboot and be running the new firmware.
Do not remove power to the router while it is being flashed with new firmware or it may lock up the router and you will not be able to recover. If using your laptop, make sure there is sufficient battery or it is plugged into a power source.
A public WAN IP address is needed for port forwarding to work. If you are unsure if your WAN IP address is public or private, contact your Internet Service Provider. If the WAN IP is not a public IP, it, and all internal devices connected to the router, will not be available to the outside world. If it is a public WAN IP address, all devices will be available to the outside world. The following are some common private IP ranges:
192.168.0.0 – 192.168.255.255
172.16.0.0 – 172.31.255.255
10.0.0.0 – 10.255.255.255
100.64.0.0 – 100.127.255.255 [This range is used by HughesNet for Carrier Grade NAT]
Once in the user interface, navigate to the Network tab and then click the Port Forward tab. Enter values for Name, Protocol, External Port, Internal Address, and Internal Port. Then click Save & Apply. Any requests that come to the router’s WAN connection on the specified port will be forwarded to the IP address and port specified on the LAN side.
Application Port Forwarding for the WRT500, VWRT510, VWRT520, AC1200M and AC1200MS
Login to your router and navigate to Network > Port Forward and in the “Port Forward” section add one port forward rule for each port that you need opened. Note that you also have to enter the IP address of the device you want the port to be forwarded to.
Xbox Live requires the following ports to be open:
Port 88 (UDP)
Port 3074 (UDP and TCP)
Port 53 (UDP and TCP)
Port 80 (TCP)
Port 500 (UDP)
UDP Port 3544 (UDP)
UDP Port 4500 (UDP)
Server Port Forwarding for the WRT500, VWRT510, VWRT520, AC1200M and AC1200MS
If you’d like to run a server on your internal network and have it accessible for the outside, then you need to add a “Virtual Server” rule as in the image below. In this example we are running a server on the local IP of 192.168.11.100 which has a web server ‘listening’ on port 81. In order to expose this web server to devices on the WAN side of the router add this following rule.
After you click ‘Apply’ and reboot your router, you can access the internal web server from the WAN side with the URL, http://WAN_IP:8888/ where WAN_IP is replaced with the WAN IP of your router (Status > Network Status > IP Address).
Here are the instructions for setting up a guest network on the AC1200.
1. Login to the router with the username and password printed on the label on the bottom of the router.
2. Create a guest network on the 2.4Ghz radio by navigating to Wireless 2.4Ghz > Basic.
The screenshot below shows how a guest network named “Guest-2.4” is created. Check the “Isolated” box to prevent devices connected to this network from ’seeing’ devices connected to the other networks.
3. Setup security on the newly created guest network by navigating to Wireless 2.4Ghz > Security as in the screenshot named 2.4-Pass.
4. Similarly create a guest network on the 5Ghz radio by navigating to Wireless 5Ghz > Basic as in the screenshot named 5-SSID.
5 Setup security on the newly created guest network by navigating to Wireless 5Ghz > Security as in the screenshot named 5-Pass.
To correct for VoIP call disconnections, ghost calls and other similar issues, configure your VoIP router to communicate with only the VoIP proxy server as follows:
1) Log in to your router and make a note of the IP address in the field FXS1 > SIP Account > Proxy Server.
2) Set the field FXS1 > SIP Account > SIP Advanced Setup > Only Recv Request From Server to ‘Enable’.
3) Enter the IP address from Step 1 in the field FXS1 > SIP Account > SIP Advanced Setup > Server Address
4) At the bottom of the page, click on Save. Repeat these steps for FXS2 if it is in use.
5) Click on Reboot to apply the saved settings.
Here are the steps to configure a repeater over Ethernet.
Simple AP Setup:
– Log in as admin
– Administration > Operating Mode > Basic > Save
– Network > WAN > LAN Connection Mode > Bridge > Save
– Wireless 2.4 GHz > Basic > Multiple SSID > [change to the same as the Primary router] > Save
– Wireless 2.4 Ghz > Wireless Security > Pass Phrase > [change to the same as the Primary router] > Save
– Wireless 5 GHz > Basic > Multiple SSID > [change to the same as the Primary router] > Save
– Wireless 5 Ghz > Wireless Security > Pass Phrase > [change to the same as the Primary router] > Save
– On the Repeater, the Ethernet ports are now bridged so there is no ‘WAN’ or ‘LAN’. Use any port to connect to the primary router.
– You can have as many Repeaters as you want. You should also be able to connect serially (i.e. Primary Router <—> Repeater 1 <—> Repeater 2 <—> Repeater 3)
– Devices connected over Wi-Fi to the Repeater will show up on the primary router (Status > LAN Host) with ‘Interface Type’ corresponding to the Ethernet port on the primary router.
– As the repeater is a true bridge, there is no IP to access it. You will need to reset the repeater to access the web interface.
– Any ReadyNet router model can be configured as a repeater with the above steps.
1) Simple Setup, no IP Address Available
This method is good for testing, however, once the router is in Bridge Mode you will not be able to access the web interface of this router.
– Log into the router as admin and navigate to Administration > Operating Mode.
– Set mode to ‘Basic’ then click Save & Apply.
– Navigate to Network > WAN and set the field ‘LAN Connection Mode’ to ‘Bridge’ then click Save & Apply.
2) Simple Setup, with IP Address Available
The router is configured as a bridge and will have an IP Address allowing you to log into this router’s web interface.
– Log into the router as admin and navigate to Network > WAN. In ‘Connect Name’ choose ‘New Connection’. Make changes as indicated in the following image then click Save & Apply.
– Navigate to Administration > Management then:
On the Repeater:
A -Enable Remote administration (Administration > Management.
Change admin password
Enable remote administration
B -Navigate to Network > WAN and change
WAN IP mode to Bridge. Save
C -Create a new WAN interface.
In Network >WAN, click ‘Connect Name’ and choose ‘New Connection’. Click Save.
D -Set 5 Ghz and 2.4 Ghz SSID to the same as that of the Primary AP. Save
E – Set the 5Ghz to Repeater mode. Click Save.
F – Click the Wireless 5 Ghz Repeater tab and choose the primary APs and connect to it. Save and Reboot
1) Connect to the Repeater with an Ethernet cable and check the DHCP IP that you got. It should be from the primary AP. Check if you can surf.
2) Disconnect the Ethernet cable. Connect to 2.4 Wireless broadcast. The SSIDs are the same on the primary and repeater, _but_ the passphrases are different. Check if you can associate and can surf.
3) Similarly test the 5Ghz repeater connection.
If the above 3 tests are good, then you can;
1) Change the wireless passphrase in the Repeater (2.4 and 5 Ghz) to match the primary AP.
2) On the primary AP locate the IP of the Repeater (Status > LAN Host). Say for e.g. the IP of the Repeater in the Primary AP is listed as 192.168.11.111 then, from the WAN side you can access the web interface of the Repeater with 192.168.11.111:8080 *because we did step A.
In the repeater two WAN interfaces were created. The first default one was changed to a bridge (Step B) and bound to all the LAN interfaces. A second WAN interface for management only (step C) was then created.