D-Link Forums

D-Link DSL Modem/Routers => Other DSL modem/routers => Topic started by: rodji on March 14, 2013, 04:01:47 AM

Title: Bug in last firmware for DSL-2640U C2 (NAT for PPTP)
Post by: rodji on March 14, 2013, 04:01:47 AM

Advanced setup -> NAT -> Virtual server options works only for
 nas_*_* interface and not for ppp0.

F/W: DSL-2640U_BRU_C2_RU_2.05_20101129.zip (lastest)

WAN:
 Port/VPI/VCI: 0/0/33
 VLAN Mux:Off
 Con. ID: 1
 Category: UBR
 Service: mer_0_0_33
 Interface: nas_0_0_33
 Protocol: MER
 IGMP: Disabled
 QoS: Disabled
 State: Enabled

PPTP: Auth method: AUTO, No compression, Default route, Always On.

for example (adding RDP port forwarding from web interface; DSL eth:
 192.168.1.1, target eth: 192.168.1.4:3389, listen: :3390), in telnet:
 # iptables -L PREROUTING -t nat -v
 Chain PREROUTING (policy ACCEPT 1925 packets, 156K bytes)
 pkts bytes target     prot opt in     out     source               destination
 8   529 DNAT       udp  –  br0    any     anywhere  192.168.1.1         udp dpt:domain to:11.35.32.34
 0     0 DNAT       tcp  –  nas_0_0_33 any     anywhere  anywhere            tcp dpt:3390 to:192.168.1.4:3389

By adding this rule all works fine:
 iptables -t nat -A PREROUTING -p tcp –-dport 3390 -j DNAT -–to-destination 192.168.1.4:3389 -i ppp0

# iptables -L PREROUTING -t nat -v
 Chain PREROUTING (policy ACCEPT 1944 packets, 158K bytes)
 pkts bytes target     prot opt in     out     source               destination
 8   529 DNAT       udp  –  br0    any     anywhere  192.168.1.1         udp dpt:domain to:11.35.32.34
 0     0 DNAT       tcp  –  nas_0_0_33 any     anywhere  anywhere            tcp dpt:3390 to:192.168.1.4:3389
 0     0 DNAT       tcp  –  ppp0   any     anywhere  anywhere            tcp dpt:3390 to:192.168.1.4:3389

Fastest solution can be for d-link developers:
 - add for every web-rule two iptables rules for ppp0 and nas_*
 interfaces. iptables process good not existing interfaces.

Title: Re: Bug in last firmware for DSL-2640U C2 (NAT for PPTP)
Post by: FurryNutz on March 14, 2013, 07:10:06 AM

Please phone contact your local regional DLink support office an ask for level 2 or higher support regarding this and let them know about this.

Good Luck.