OpenWrt Forum Archive

Topic: portforward not working after playing multiplayer game

The content of this topic has been archived on 21 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

strange thing big_smile after 2 hours of playing batllefield2 port forwarding stops working
linksys wrt 54GL kamikaze with standard settings, qos-script
and
iptables -t nat -A prerouting_wan -p tcp --dport 11074 -j DNAT --to 172.18.18.18:11074
iptables        -A forwarding_wan -p tcp --dport 11074 -d 172.18.18.18 -j ACCEPT
iptables -t nat -A prerouting_wan -p udp --dport 11074 -j DNAT --to 172.18.18.18:11074
iptables        -A forwarding_wan -p udp --dport 11074 -d 172.18.18.18 -j ACCEPT

added to firewall.user
what is wrong?
/etc/init.d/qos restart no go sad
same with firewall
when i restart router everything goes back to normal

what can i check to debug this?

May be the port+x bug... try using --to ip instead of --to ip:port if the port doesn't change.

will try that thanx

(Last edited by fisz on 1 Jan 2008, 19:40)

fisz wrote:

strange thing big_smile after 2 hours of playing batllefield2 port forwarding stops working
linksys wrt 54GL kamikaze with standard settings, qos-script
and x360 key
iptables -t nat -A prerouting_wan -p tcp --dport 11074 -j DNAT --to 172.18.18.18:11074
iptables        -A forwarding_wan -p tcp --dport 11074 -d 172.18.18.18 -j ACCEPT
iptables -t nat -A prerouting_wan -p udp --dport 11074 -j DNAT --to 172.18.18.18:11074
iptables    x360key    -A forwarding_wan -p udp --dport 11074 -d 172.18.18.18 -j ACCEPT

added to firewall.userxk3y
what is wrong?
/etc/init.d/qos restart no go sad
same with firewall
when i restart router everything goes back to normal

what can i check to debug this?

try using --to ip instead of --to ip:port if the port doesn't change.

The discussion might have continued from here.