Posted: Wed Jul 23, 2014 21:32 Post subject: WNDR3700V4 not Forwarding, Triggering, Range
WNDR 3700v4 build 23919
Stock Netgear firmware: all types of port forwarding works.
DD-WRD 16785, 23202, 23919: Some ports will work using port forwarding. No port range or triggering will work.
Ports that will forward: 20, 21, 1723, 3389, 8767.
Ports that will not work: 1716-1722, 2716-2722, any random port I try on either TCP or UDP
I didn't include the first thing in the OP but those work as well. I havent tried 27016 and 27016 but I have tried 27900 and 20046 and 20047 for UDP and a no go.
Can't upgrade firmware just yet as I am not on site. Just thought I would include that info. Again, it happens on all previous builds. Also, did you have to do anything extra, such as commands, like what was stated in those links I provided?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Jul 24, 2014 4:01 Post subject:
try reset to defaults, said option in gui under administration -> factory defaults tab, or telnet "erase nvram", "reboot" _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I will do that. Hate to sound like a noob but where is the timeline? I searched the forums but didnt see anything called that.
Also I ended up entering these commands in at once and got a somewhat result:
insmod ipt_mark
insmod xt_mark
iptables -t mangle -A PREROUTING -i ! `get_wanface` -d `nvram get wan_ipaddr` -j MARK --set-mark 0xd001
iptables -t nat -A POSTROUTING -m mark --mark 0xd001 -j MASQUERADE
LAN=`nvram get lan_ipaddr`/`nvram get lan_netmask`
iptables -t nat -I POSTROUTING -o br0 -s $LAN -d $LAN -j MASQUERADE
With that in place my FTP ports stopped working but the ports I was wanting to open work...wtf?
Maybe I'm just doing something wrong? Here are some snip-it's of my routing. I know the boxes are not checked in the pics but I do have them checked when trying to see if they work. And I know some of the PF and PRF overlap so I make sure they are not checked at the same time.
also try delete everything from the port range tab, & use the standard port forwarding tab instead, as that too, has "port from" & "port to" meaning it should accept ranges as well which would mean theres sort of a double negative having port range fwrding there _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
