Author Topic: "Filter WAN NAT Redirection" option does not work on WZR-HP-G450H  (Read 3048 times)

ddv2005

  • Calf
  • *
  • Posts: 3
"Filter WAN NAT Redirection" option does not work on WZR-HP-G450H
« on: September 18, 2011, 03:47:12 pm »

Hi,

 

I have problem with " Filter WAN NAT Redirection?" option. It does not work at all and I can't reach port forward from LAN.

I found that it because you miss the MASQUERADE? rule for LAN.

iptables -t nat -A POSTROUTING -j MASQUERADE -s 192.168.11.0/24 -d 192.168.11.0/24 -o br0?

 

Could you fix the problem?

 

Dmitry


thor

  • Calf
  • *
  • Posts: 13
Re: "Filter WAN NAT Redirection" option does not work on WZR-HP-G450H
« Reply #1 on: September 19, 2011, 12:16:19 pm »

What exactly are you trying to achieve ?


ddv2005

  • Calf
  • *
  • Posts: 3
Re: "Filter WAN NAT Redirection" option does not work on WZR-HP-G450H
« Reply #2 on: September 19, 2011, 04:35:11 pm »

Hi,

I have some server in LAN network and I have port forward on router to this server (port 82 to 192.168.0.10). I can reach this server from internet by 82 port. I use some application on my android phone to use this server (DVR) and from internet it work fine. But it does not work when at home (phone connected as wireless client to the router) because
router prohibited to use WAN address port forwarding from LAN. On my previous router with older version DD-WRT it work fine with disabled Filter WAN NAT Redirection option.
But with new router it does not work.
?


Yogi76

  • Calf
  • *
  • Posts: 2
Re: "Filter WAN NAT Redirection" option does not work on WZR-HP-G450H
« Reply #3 on: April 16, 2012, 10:32:32 pm »

This is true for all DD-WRT firmware after r15760. Here is a link to the trouble ticket with an explanation and the fix, which is the same as the one you mentioned in Dmitry's original post:

 

http://svn.dd-wrt.com:8000/ticket/1868

 

Unfortunately, the trouble ticket is in "closed: wontfix" status, so everytime you do a firmware update on your WZR-HP-G450H, you will need to re-enter the fix. What's really bad is that, before I found the fix, I called Buffalo support and they were completely clueless about both the problem and any way to fix it.