Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[usalabs]

I recently purchased the dual band router from ebay, but can't find anywhere for details on if it supports NAT loopback, the manual says nothing, and nowhere else has anything.

I used to use a Netgear WGR614 v9 wireless G router, this one did support NAT loopback, but recently the wifi section of the router was slowly degrading and sometimes, even when about 5 feet away from the router I would get 1 bar on the laptop, so I changed routers.

The reason I wanted NAT loopback is because I run a virtual worlds development server at home and has been working great with the old router, and using my domain name to point to my WAN IP address with the necessary ports open, but I can't use my domain name with this new router even with the server on the DMZ.

If this router doesn't support NAT loopback, is there a way to enable telnet access so that I can write a few iptable rules?

[FurryNutz]

Link>Welcome Back!

• Link>What Firmware version is currently loaded? Found on the routers web page under status.
• What region are you located?

List of NAT Loopback Supporting Routers
LoopBack Work Around: http://forums.dlink.com/index.php?topic=16358.0

Also check out the use of Virtual Server on the 835. Not sure about accessing the router via telnet if that's an enabled feature or not. Maybe disabled as a security issue.

What happened with this post? http://forums.dlink.com/index.php?topic=64462.msg266059#msg266059

[usalabs]

Hardware version A1, Firmware 1.04, Region USA

Cannot use virtual server as it only allows single ports, I have to use a range of ports from 9000-9900 TCP and UDP.

The virtual worlds development server uses regions that utilize various ports in the range of 9000-9900 depending on which region is being enabled, and the client viewer reads the info from the server to determine what port is being accessed, but not using http, but there is a test page that shows OOPS! in large letters for testing the loopback, by entering http://domainname:port, and if the loopback is successful, the OOPS!!! page is shown, meaning that if I can access the test page from inside the LAN using a WAN domain name, then others with the client viewer can access the server too, but if I can't, I don't know if anyone else can without literally calling everyone in the white pages and asking them if they have internet to download the client and test the connection.

[FurryNutz]

Let us know if any of the other suggestions may help. If it doesn't, you could use your old router as the main host router since it worked for loopback, then disable the wifi radio on that router and install the 835 as a wired AP:
Turning a router into an AP.

Try the other suggestions first and see...

[usalabs]

Let us know if any of the other suggestions may help. If it doesn't, you could use your old router as the main host router since it worked for loopback, then disable the wifi radio on that router and install the 835 as a wired AP:
Turning a router into an AP.

Try the other suggestions first and see...

I didn't think of using the 835 as an AP,   I think that would be better.

The link for the work-a-round isn't a work-a-round, but using the virtual server, which as I stated earlier, I can't use the virtual server as I need to use a range of ports, and the virtual server only allows 1 port per server, so it looks like the wired AP would be the way to go,,,,I'll try it and get back here to let y'all know if it works.

[FurryNutz]

 

[usalabs]

Sorry for the late reply.

OK, using the 835 as an AP didn't work, as I already have a 625 as an AP, and I wanted to use the 835 as the main router, because it has removable antenna, and using the right antenna socket I can connect a WiFi booster, anyway, I found I can use iptables rules but first I had to install the openwrt firmware for the 835 (openwrt-ar71xx-generic-dir-835-a1-squashfs-factory) which allows me to write my own custom iptables rules such as these:-

iptables -t nat -I PREROUTING --dst <host name> -p tcp --dport 9000:9900 -j DNAT --to-destination <server LAN IP>
iptables -t nat -I PREROUTING --dst <host name> -p udp --dport 9000:9900 -j DNAT --to-destination <server LAN IP>
iptables -t nat -A POSTROUTING --dst <server LAN IP> -p tcp --dport 9000:9900 -j SNAT --to-source <gateway>
iptables -t nat -A POSTROUTING --dst <server LAN IP> -p udp --dport 9000:9900 -j SNAT --to-source <gateway>

This fools the router into thinking it has loopback.

[FurryNutz]

Glad you got it working. Actually OpenWRT FW isn't fooling the router. The issue is that Stock FW doesn't support or any loopback features, where OpenWRT does.

Enjoy.