[UPDATE #2} New firmware is available from Draytek Australia which enabled the port trigger link.
[UPDATE} After contacting local Draytek support in Australia they have provided me with a beta firmware that re ads the port trigger menu to the web interface. I have not installed this as the method below has been working solidly for the last month, but its worth trying if the instructions below look daunting. Updating your firmware on the draytek devices isn’t difficult at all and leaves less room for error then my instructions below.
This post outlines how to connect multiple Xboxes to Xbox live and achieve Open NAT. This post relates directly to achieving this with a Draytek Vigor2830 ADSL broadband router.
If you would like a general guide to opening the correct ports for Xbox live, I highly recommend this youtube video which covers everything you will need.
I have 2 Xbox consoles which I need to connect to Xbox Live. Both are hard wired to a Draytek Vigor2830 ADSL broadband router. Currently I can do this but I receive an error stating my NAT setting is moderate.
Viewing the video linked above, you will find the best practice for this is to use a combination of uPnP and port triggering.
The issue with this is that for some reason, port triggering has been removed from the Vigor2830 web interface, and such can’t be configured.
This guide will show you how to configure port triggering for the Draytek Vigor2830 via telnet.
Before you begin
- If you are not comfortable using command line interfaces and making changes to your router you should not proceed.
- This post assumes you know the IP address of your router and how to access this.
- Part of this configuration change includes changing the web management port for your router, this means in future you will need to specify the new port whenever logging into your routers management interface.
- DISCLAIMER: I will not be held liable for any issues you have by following this documentation. Any changes made to your equipment is done at your own risk.
- My Vigor2830 is using firmware 188.8.131.52db – if your firmware is different, your may encounter different results.
- Login to your routers management interface via a web browser
- Go to ‘Applications’ -> ‘UPnP’ and enable the service and also enable the control service and connection service and click OK.
- Stay logged into the management interface for the next step
Updating your Vigor’s web management interface port.
- Go to ‘System Maintenance’ -> ‘Management’
- Select ‘User defined ports’ under ‘Management Port Setup’ and change the HTTP Port to 90 (or another non conflicting port of your choice)
- Click OK and confirm. Your router will then reboot.
Connecting to your Vigor2830 via telnet and configuring port triggering
Once your router has finished rebooting you will need to connect via telnet. To do this you will need to use a telnet client.
- Open a telnet connection to your router.
- When prompted enter the same admin user name and password as you use to connect to the web interface
- First we need to confirm port triggering isn’t configured. The commands provided in this post assume this is the case. to confirm this type:
srv nat trigger -v
The output returned should show all available trigger spots as disabled and no labels/comments should be present. The output should look like:
%% Port Trigger Rule status: Index Status Comment TProto TPort IProto IPort ----------------------------------------------------- 1 Disable 2 Disable 3 Disable 4 Disable 5 Disable 6 Disable 7 Disable 8 Disable 9 Disable 10 Disable
- Once we have confirmed there are no configured port triggers, we can add the needed entries using the commands below. Enter each line once at a time followed by enter/return.
srv nat trigger 1 -c XBLA1 -e 1 -p 3 -t 53 -P 3 -i 53 srv nat trigger 2 -c XBLA2 -e 1 -p 3 -t 80 -P 3 -i 80 srv nat trigger 3 -c XBLA3 -e 1 -p 3 -t 88 -P 3 -i 88 srv nat trigger 4 -c XBLA4 -e 1 -p 3 -t 3074 -P 3 -i 3074 srv nat trigger 5 -c XBLA5 -e 1 -p 3 -t 1863 -P 3 -i 1863
- Once these have been entered, run the trigger query command again:
srv nat trigger -v
The output should now look like the following:
Index Status Comment TProto TPort IProto IPort ----------------------------------------------------- 1 Enable XBLA1 TCP/UDP 53 TCP/UDP 53 2 Enable XBLA2 TCP/UDP 80 TCP/UDP 80 3 Enable XBLA3 TCP/UDP 88 TCP/UDP 88 4 Enable XBLA4 TCP/UDP 3074 TCP/UDP 3074 5 Enable XBLA5 TCP/UDP 1863 TCP/UDP 1863 6Disable 7Disable 8Disable 9Disable 10Disable
If your output looks like the above the trigger ports have been configured. At this time I logged back into my router and rebooted it. Probably optional but doesn’t hurt.
- On your xbox, you will need to go into System Settings and then Network, and wired network and make sure this is set to configure automatically (don’t use manual addresses).
- Run a test connection to Xbox Live and you should find this is now working without a moderated NAT warning on both xboxes.
For those wondering here are the switches for srv nat trigger command:
srv nat trigger n [-<command> <parameter> | ... ] n: rule number -c: comment -e: enable/disable this emety [1/0] -p: trigger proto. [1-TCP, 2-UDP, 3-All ] -t: trigger port. -P: incomming proto. [1-TCP, 2-UDP, 3-All ] -i: incomming port. -d: delete -v: show port trigger setting
Feel free to leave any comments or queries (including alternate work arounds) for this issue.