TW2 outgoing port 80, incoming listening on TCP 47000 ?

[foo_]

TW2 outgoing port 80, incoming listening on TCP 47000 ?

I noticed two sorts of internet connections when starting The Witcher 2.
One is by the launcher, connecting to port 80 (HTTP) of some webserver in France.
I have some ideas what this could be, but instead of guessing, I'd better ask what is done there.

But then, the game itself (witcher2.exe) also opens a listening port for incoming TCP connections on port number 47000.
For this, I am at a complete loss. What sort of connections does TW2 expect, and where from?

I have checked the FAQ and the README.TXT but haven't found any information on this.
Please enlighten me

 

[drunknmunkey666]

It connects to an update server to check for updates, and the listening port is probably for when an update server sends information about "this update just arrived"?

 

[foo_]

It connects to an update server to check for updates, and the listening port is probably for when an update server sends information about "this update just arrived"?

Update check by the launcher I expected, as I wrote. But it's not likely the game is expecting update notifications - for one, it couldn't perform the update since it's running already. The Launcher could perform the update, but it's not listening (and doesn't have to).

Also, it's not likely that this listening port can be readily accessed; port 47000 is not mapped by default on most routers. In general, most routers do not map incoming connections unless explicitly configured to do so - except for the most common ports. Which makes it even more mysterious to me - if we were to open the port for any purpose, shouldn't we be told so we can take care of configuring routers? Is it really local mbus according to RFC 3259, and if so, what will it do? Or is it some mysterious multiplayer option? Whatever it is, I'm curious.

 

[drunknmunkey666]

Hehe some day all of a sudden every person playing TW2 will be merged into the same game - Geralt everywhere

I've got no idea as to why the game itself listens on ports, sorry I read your initial post wrong and thought it was the launcher listening

Maybe it's New World Order sneaking into games

I hope someone from RED team joins this thread and enlightens us!
BTW: nice catch, how did you get the idea of investigating a single player game for net traffic?

 

[tommy5761]

Is this a disc install or Steam download ? I would assume if Steam download that would be achievements unlocking...not entirely sure though .

 

[foo_]

Is this a disc install or Steam download ? I would assume if Steam download that would be achievements unlocking...not entirely sure though .

No Steam. I bought TW2 directly from GOG.com, preordered and downloaded it right there.

 

[foo_]

Hehe some day all of a sudden every person playing TW2 will be merged into the same game - Geralt everywhere

Or the hidden multiplayer bonus kicks into effect, once a certain monk makes a mysterious announcement including a four-letter-word activation code

I hope someone from RED team joins this thread and enlightens us!

So do I!

BTW: nice catch, how did you get the idea of investigating a single player game for net traffic?

I didn't. Every piece of software on my PCs is routinely screened, and no connections or port openings happen without my consent. So I get the notice "witcher2.exe wants to listen on TCP 47000", and wonder what's that good for. (Doesn't everybody handle it like this? )

If I were actually investigating, I would've intercepted or snooped the port 80 traffic of the launcher, checking what happens if you change its contents a bit and so on. But in the interest of mutual politeness, I'd rather ask first.

 

[drunknmunkey666]

I just run with Windows Firewall, It's not so picky I guess?
Do you run a different firewall utility?

 

[GuyNwah]

Port 80 is the Launcher asking dl.thewitcher.com about updates. If there were any updates, they would likewise come in from port 80. Port 80 is the well-known port for HTTP. I've tracked the Launcher's use of that one with Wireshark.

Port 47000 is some local functionality, such as Mbus (which normally occupies that port). It is not listening to the Internet; your gateway wouldn't let any traffic through to it. I have never seen any actual traffic while TW2 is running on that port.

It is a common practice for applications and services to communicate over Internet-domain sockets even when they communicate only with other local components. It has the annoying effect of tripping firewalls that check for things like that.

 

[guywithknife]

Indeed, TCP/UDP sockets are a fairly standard method of Inter Process Communication. Not sure what The Witcher 2 uses it for, though there could be many uses, eg, a remote debugger or accessing the running game from the game editors, or even just communicating with the launcher.