/sbin/iptables -t nat -A PREROUTING -i [EXTERNAL_IP] -p tcp --dport 6112 -j DNAT --to-destination [CLIENT_IP]]:6112
/sbin/iptables -t nat -A POSTROUTING -p tcp -d [CLIENT_IP] --dport 6112 -j SNAT --to-source [SERVER_IP]
/ip firewall nat
add action=dst-nat chain=dstnat dst-address=[EXTERNAL_IP] dst-port=6112 protocol=tcp to-addresses=[CLIENT_IP] to-ports=6112
add action=src-nat chain=srcnat dst-address=[CLIENT_IP] dst-port=6112 protocol=tcp to-addresses=[SERVER_IP]
Yep, you probably right!This is kind of problematic with PPTP and L2TP, because game/hostdiscovery in warcraft 3 works by using broadcast packets,
which usually does not work over any PPP based connection. You are better off using an alternative solution like Hamachi (which I can confirm as working) or Tunngle.
Your best shot is enabling proxy-arp (which is required for PPTP/L2TP clients sharing the same subnet with your main LAN) on your LAN interface, and assigning the dial-in client a free address from your local subnet, and then trying again. I am however pretty confident it won't be able to see the game session, maybe the game session will show up in WC3, but will fail to connect. I would really recommend using Hamachi instead.
Should enable proxy-arp on WAN(public) port????This is kind of problematic with PPTP and L2TP, because game/hostdiscovery in warcraft 3 works by using broadcast packets,
which usually does not work over any PPP based connection. You are better off using an alternative solution like Hamachi (which I can confirm as working) or Tunngle.
Your best shot is enabling proxy-arp (which is required for PPTP/L2TP clients sharing the same subnet with your main LAN) on your LAN interface, and assigning the dial-in client a free address from your local subnet, and then trying again. I am however pretty confident it won't be able to see the game session, maybe the game session will show up in WC3, but will fail to connect. I would really recommend using Hamachi instead.