Draytek Vigor 120 + Linksys WRT320N : Port Forwarding Issue

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Draytek Vigor 120 + Linksys WRT320N : Port Forwarding Issue

nzskater

93 posts

Master Geek
+1 received by user: 4

#83344 14-May-2011 13:36

After following some advice on these and other forums, I grabbed these 2 routers, and they're all but working well. Have only 2 issues that I'd like to get resolved, and am hoping to call upon the wealth of knowledge here to get it sorted. Any help would be much appreciated; if you're based in Wellington I'll buy you a coffee/beer to say thanks!

My setup; Linksys WRT320N + Draytek Vigor 120.

Draytek is configured for PPPoE/PPPoA mode, and WRT320N is set to PPPoE.

All internal routing (DHCP, NAT, firewall etc) on the Draytek is switched off (but my assumption is that due to the PPPoE/PPPoA pass through/bridge it's irrelevant?).

WRT is configured to manage all routing internally, so DHCP etc etc.

Now, Internet is working for the most part. What ISN'T working is my ability to access the Draytek indirectly and port forwarding.

Tried setting both the Draytek & WRT to a /16 subnet, gave the WRT 192.168.1.1 and the Draytek 192.168.2.1 but no dice. Tried on a /24 with different IP's. Giving up on that! Not a big issue but would be a nice thing to have...

Port forwarding is my major problem. If an app uses UPNP it seems to work fine, but if I configure a manual port forward on the WRT it doesn't seem to work.

Have tried multiple resets of both routers, firmware upgrades and different configs. My networking skills are VERY lite, and I've exhausted my knowledge. Even went as far as putting DD-WRT on the WRT so I could see the UPNP info, and I can confirm it's setting up routes properly, but I have no idea why manual forwards aren't working.

Does anyone have any ideas? I'd really like to be able to get access back to my home PC while out and about for work, and I'd much rather get this working than replace both routers with an all-in-1 solution.

durq

9 posts

Wannabe Geek

#469099 14-May-2011 16:52

With the draytek in bridge mode the DHCP server is downstream of it, so it does not get assigned an IP address. To configure it you then need to run an ethernet cable from it directly to your computer then it should be visible on 192.168.1.1 or 192.168.2.1 i forget which

Not sure about your portforwarding issues, but I don't think its the draytek causing it.
I use a one with a airport extreme, which replaced a linksys wag310g, because like you i had problems getting manual portfowards to work on the linksys. Specifically skype would ALWAYS report 'UDP Status: Bad' not matter what i did

Now the linksys is gone and so are the portforward problems

froob

698 posts

Ultimate Geek
+1 received by user: 233

Lifetime subscriber

#469354 15-May-2011 17:28

I have quite a similar setup to yours- a Vigor 120 paired with a Linksys e2000- which is the same hardware as your WRT320N. I'm running Tomato firmware from www.tomatousb.org which I highly recommend. It has been really solid, no issues with manual port forwarding or UPnP. In order to get access to the Vigor 120 I used these instructions http://www.geekzone.co.nz/forums.asp?forumid=66&topicid=57953 off the Geekzone forums. The only change to the instructions needed to get it to work on my Linksys e2000 were to use vlan2 instead of vlan1, which would probably also apply to the WRT320N.

Guide: Installing Network Cabling in New Zealand Homes

nzskater

93 posts

Master Geek
+1 received by user: 4

#474041 25-May-2011 16:50

Thanks guys, info was helpful. Will look at setting up the config to allow modem access when I get a chance.

As far as the port forwards go, turns out it was just bad luck, combined with crap standard firmware. I can confirm that the Linksys firmware did NOT work, no matter what I tried. In the end putting dd-wrt on it did the trick, and gave me exactly what I needed (along with a ridiculous amount of options I didn't, though not complaining). The first nightly I had tried turned out to be a bit flaky, changing versions fixed all of my issues.

Highly recommend this setup to anyone else looking to move away from the crappy all in one solutions you tend to get from your ISP.