Posted: Sun Sep 23, 2012 8:27 Post subject: Not sure if this helps
Just wanted to share the simple fix I had to a similar problem. I still don't understand how this is connected but after restarting my dd-wrt box (which made it reset itself to factory defaults) I decided to upgrade it to last "stable 14929" release. I upgraded it and added the port forwards. They didnt work. Nothing else was changed on my network and I got all clueless. I finally figured out that upgrading the router made Win 2003 Server firewall starting to work as intended, hence i had to add the ports there too. Why the old routerfirmware bypassed this I have no clue too.
I had issues with port forwarding as well with my Buffalo WHR-HP-G300N ( DD-WRT v24SP2-MULTI (06/03/12) std - build 19154 ). It just would not work. With the command posted above, it solved everything! Thanks alot!
Same behaviour here on a Buffalo WZR-600DHP running the latest DD-WRT v24SP2-MULTI (11/04/12) std (SVN revision 20180).
Can somebody explain what the problem is and why the command above fixes it?
Is this a known bug?
Will it get fixed soon?
Glad that it worked but holy crap, I never had so much trouble setting port forwarding...
This is a terrible solution to be honest.
This makes all incoming connections look like they are coming from the router it self.
TS3 server running on ip 192.168.1.69 on port 9987
You add port 9987 to port forwarding towards ip 192.168.1.69.
By default this will not work for some reason port forwarding is not forwarding connections correctly
If you use the following command "iptables -t nat -A POSTROUTING -j MASQUERADE" the portforwarding will work.
But if you look on a client connected to the TS3 server they will list as client ip "192.168.1.1:xxxxx"
This means that you will not see the actual ip of the connected client.
There must be a better way to fix the port forwarding.
FW used is DD-WRT v24-sp2 (07/20/12) std
(SVN revision 19519)
Also experianced on DD-WRT v24SP2- (03/25/13) std
(SVN revision 21061)