Steam client TCP over port 27019 issue


#1

I want to use mitmproxy to monitor the network traffic of a video game, but I can’t log into the Steam client because it uses port 27019 for some of it’s TCP traffic. Is there a way to make this work at all? I’ve already tried this: “–ignore d+.d+.d+.d+:27019” but that didn’t help at all. I’m assuming mitmproxy only allows ports 80 and 443?

Hopefully someone can help me with this issue.

Thank you.


#2

Did you take a look at http://docs.mitmproxy.org/en/stable/features/passthrough.html#limitations? We’re generally port-agnostic.


#3

No traffic appears at all in mitmproxy when the Steam client is logging on, I get a bunch of clientdisconnects and clientconnects in the event log but that’s pretty much it. I’m not really sure what the problem is.’

Edit: Okay I’ve tried another program and the same issue occurs, I don’t think Steam likes http proxies, I will probably have to use socks instead for it to work.