Problems Forwarding ports to use Steam

RouterOS Beginner Basics
1

Steam’s page says the following:

Steam Client

UDP 27000 to 27015 inclusive (Game client traffic)
UDP 27015 to 27030 inclusive (Typically Matchmaking and HLTV)
TCP 27014 to 27050 inclusive (Steam downloads)
UDP 4380

Then I did the following rules

14   chain=dstnat action=dst-nat to-addresses=192.168.75.10 protocol=udp 
     dst-port=27000-27030




15   chain=dstnat action=dst-nat to-addresses=192.168.75.10 protocol=tcp 
     dst-port=27014-27050




16   chain=dstnat action=dst-nat to-addresses=192.168.75.10 protocol=udp 
     dst-port=4380

I tested them with the PortForward’s PortChecker tool and everything is fine but the Steam stops logging in when the rule 14 is active. Its one of those 30 UDP ports, I dunno which one but I guess it doesn’t matter. I need to know the reason the Steam stops working when I redirect the ports and the redirecting is working properly according to the testing tool.

2

I use Steam for play :wink:

The username on steam are the same as here… :wink:

You do not need to open anything, do not do any, remove all your rule, are all wrong,

simply enable UPNP on Routerboard and configure it correctly :wink:

This is my UPNP config, I never have one game that not work with that:

/ip upnp
set allow-disable-external-interface=no enabled=yes show-dummy-rule=yes
/ip upnp interfaces
add disabled=no interface=MATRIX type=internal
add disabled=no interface=pppoe-client type=external

MATRIX must be your local ethernet / bridge
pppoe-client your internet source.

3

Add the dst-address or in-interface parameter to the rules, this could solve your issue.

4

Have you Steam and using it?

5

Honestly no but I assumed this is ‘normal’ natting.
With the rules given, all packets will be dst-natted, inbound and outbound. That’s why I thought about specifying in-interface could help.

6

I know how to activate the UPnP and I actually use it, I disabled it in order to test something that involves the manual port opening.

7

And it did, indicating the in-interface solved the problem, thanks.

Can you manage to explain it to me? I don’t understand why the Port Checker had no problems being reached by the outside and the Steam Client didn’t.