What port does EternalChat use and is there a way to change it?
The port to connect to b.net is 6112.
It probably does not bind to any particular local port, if that's what you're after. Since it's a client application, there is no point in choosing a set port on the local side to bind to.
Battle.net accepts a connection on a wide variety of ports, as choosable in WC3 settings. I'm not sure what the range is, and I'm almost certain its hardcoded.
Quote from: Joex86] link=topic=10880.msg108719#msg108719 date=1113616660]
Battle.net accepts a connection on a wide variety of ports, as choosable in WC3 settings. I'm not sure what the range is, and I'm almost certain its hardcoded.
That port for War3 settings is the port
you will use if you host a custom and/or arranged team game
Quote from: Joex86] link=topic=10880.msg108719#msg108719 date=1113616660]
Battle.net accepts a connection on a wide variety of ports, as choosable in WC3 settings. I'm not sure what the range is, and I'm almost certain its hardcoded.
No, Battle.net accepts connections on port 6112. The settings that can be chosen are for what port you want to open on your machine to host non-ladder games.
Is it correct to say 9367? Since EternalChat connects through BNLS and uses 9367. Jarlaxle asked what port EternalChat used, not what port Battle.net used, that's why I believe the correct answer would be 9367.
Quote from: Yegg on April 22, 2005, 02:50 PM
Is it correct to say 9367? Since EternalChat connects through BNLS and uses 9367. Jarlaxle asked what port EternalChat used, not what port Battle.net used, that's why I believe the correct answer would be 9367.
EternalChat does not use any particular port. BNLS uses port 9367, and Battle.net uses port 6112. If you were to packetlog your connections to BNLS and Battle.net, you would find that EternalChat would use different ports on your side every time.