Guys I ma baffled how this doesn't work with such a powerful router. I am going to have to revert back to my time capsule which I really do not want to?!
Just about everything in my house uses the wan domain name to access all the port forwards?! There has to be a working decent solution here?
I believe this is exactly what I need to do on my router but the question is do I have to run commands for iptables before or is setting up port forwards essentially the same thing?!
Posted: Fri Apr 22, 2011 0:06 Post subject: Thanks so much!
Works for me on DD-WRT v24SP2-MULTI (12/17/10) std SVN revision 15940 which came with my Buffalo WZR-HP-AG300H.
I was about to pull my hair out trying to figure out why I could not access my FTP using the external IP / DDNS.
I cannot understand why the devs keep marking it "wontfix" cause it's like the only router firmware I've ever used that had no way to support this functionality (and always using port forwarding to do it)...
Anyways, I want to say thanks to you for sticking with this & finding a solution!
Don't work for me.
May be it doesn't work because i use pptp for internet connection and "nvram get wan_ipaddr" return WAN but not pptp/internet address?!
get_wanface return ppp0
UPD
I change "nvram get wan_ipaddr" to "nvram get pptp_get_ip" and now it work.
Posted: Mon May 09, 2011 7:36 Post subject: n00b question
To clarify: the bug being discussed here breaks port forwarding in newer releases, correct? Does this include UPnP based forwarding? If yes, does that mean that UPnP forwarding is broken even though the UPnP page says it is working?
I'm running mini - build 16403M NEWD-2 K2.6 Eko on an Asus RT-N12.
Joined: 18 Jun 2006 Posts: 4 Location: Grid Square FN43MG
Posted: Mon May 09, 2011 17:02 Post subject: Re: n00b question
MrCommunistGen wrote:
To clarify: the bug being discussed here breaks port forwarding in newer releases, correct? Does this include UPnP based forwarding? If yes, does that mean that UPnP forwarding is broken even though the UPnP page says it is working?
I'm running mini - build 16403M NEWD-2 K2.6 Eko on an Asus RT-N12.
It doesn't break Port forwarding what is broken is the Local Loop back other wise known as "WAN NAT Redirection".
The only affect that this fix has is on poorly written QoS Scripts.
I hope this answers your Question.
Last edited by Bronsen on Mon May 09, 2011 17:23; edited 1 time in total
Posted: Mon May 09, 2011 17:15 Post subject: Re: n00b question
MrCommunistGen wrote:
To clarify: the bug being discussed here breaks port forwarding in newer releases, correct? Does this include UPnP based forwarding? If yes, does that mean that UPnP forwarding is broken even though the UPnP page says it is working?
I'm running mini - build 16403M NEWD-2 K2.6 Eko on an Asus RT-N12.
It does not break port forwarding at all, it breaks NAT loopback which is when you access port forwards from within your local LAN instead of from the WAN. It does affect NAT loopback for all kinds of port forwards. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Posted: Fri May 13, 2011 13:30 Post subject: Wow! Webserver Stopped Working Local Machine Email Too
Updated my dd-wrt, sites hosted on webserver wouldn't show on local machines, seemed like a loopback problem, checked loopback and that didn't help. The above fix did though, thanks MisterP. I wasn't able to access my pop3 emails even, was in a slight panic _________________ Router Model: Buffalo WZR-HP-AG300H
Firmware Version: Firmware: DD-WRT v3.0-r46733 std (05/21/21)
Kernel Version: Linux 3.10.108-d11 #81419 Fri May 21 12:44:07 +07 2021 mips