Port Forward Starcraft2?(Failed to retrieve version information from Battle.net)

[mastablastaz]

I tried everything. I can't play Starcraft 2 behind pfsense.

Can't even start the updater when you launch the game.

20:14:34.8432 Failed to retrieve version information from Battle.net.
20:14:42.0626 Failed to retrieve version information from Battle.net.

Seems it can't connect to battle.net and I don't see any blocked packets in the pfsense logs?!

Opened the following ports WAN TCP/UDP (ingoing) for:
*BlizzardDownloader: 1119, 3724, 4000, 6112:6114, 6881:6999
*Starcraft2   1119, 1120

Port forwarded the above ports to my host.

Opened everything LAN TCP/UDP (outgoing) for my host

Trying to avoid using upnp (don't think it can tho).

Note: yes it does work when I connect directly to the internet.
Any ideas?

[Gertjan]

Installed with default outgoing (firewall) rules, pfSense doesn’t behave any different as any other ISP router.
I’m talking about the fire wall rule on the LAN interface : let all connection go out without restriction.

I'm not using StarCraft (but I know Blizzard apps very well - being a wow client for 5 years) and pfSense doesn’t block Blizzard port - or the client port used for outgoing connections.

Btw: Blizzard downloader (for WOW) speaks very well with the uPNP implemented in pfSense.
It opens the right ports for downloading - something that speeds up things a little bit.
uPNP isn’t needed for ‘playing’.

I presume that your PC is connected to the LAN interface (although using WoW on the captive portale works also very well).
So, what did you do with your pfSense setup (please detail) that stops you from using it correctly – or how do you use it ?

[Mad Professor]

I'm on a pfsense setup and I'm not having any problems with starcraft 2.

My lan rules are default.

proto: *
Source: Lan Net
Port: *
Destination: *
port: *
gateway: *

I have not port forward anything, or 1:1 Nat except for my parents sorenson videophone, parents are deaf.

Are you running windows xp, I have heard a few complaints about SC2 and the downloader not working.

You want incoming to be open. Outgoing is already open but incoming is blocked by default. But still I have not had to do anything. I love pfsense when it just works, on the other hand it can be a bitch.

[mastablastaz]

Hi guys, I have still not played a single min of starcraft 2 :(

Anyway, Here is how my pfsense is configured:

Usually I block all outgoing and only open ports I want.

Example:

TCP/UDP  LAN net  *  *  53 (DNS)  *      Allow DNS 
TCP LAN net * * 80 (HTTP) *   Allow HTTP 
TCP LAN net * * 443 (HTTPS) *   Allow HTTPS

TCP/UDP  myComputer  *  *  Steam  *      Allow Steam 
UDP myCumputer SteamPing * * *   Allow Steam

with

Steam  27000:27039, 1200, 7024
SteamPing 2400:2600, 27005

For steam games.

Ingoing I usually open the ports I want.

TCP/UDP  *  *  bob  Starcraft2  *      NAT Starcraft2 
Starcraft2  1119, 1120

I noticed I can't attach/upload images to forums. This is linked to my problems I think. Something is being blocked by pfsense. (I have javascript and flash enabled)
I might need to reinstall my pfsense because it seems it's blocking some connection attempts randomly without logs.

Yes im using WinXP SP3 latests patches.

Any ideas guys?

[mastablastaz]

Solved my problem. Don't know how on the firewall side.

Updated SC2 to the latest patch going directly into the modem.

I guess I will have the same problem when a new patch is required.

[Jahntassa]

@mastablastaz:

Any ideas guys?

Personally i'd be less restrictive with pfSense and utilize a software firewall like Comodo to block unwanted outgoing stuff. Blizzard likes using Bittorrent and other such fun things for doing updates, and aren't always forthcoming with all the ports / connections they use. Generally they assume (which I would as well) that most setups are fairly unrestricted outbound, or using software firewalls with program-based rulesets.

[mastablastaz]

@Jahntassa:

@mastablastaz:

Any ideas guys?

Personally i'd be less restrictive with pfSense and utilize a software firewall like Comodo to block unwanted outgoing stuff. Blizzard likes using Bittorrent and other such fun things for doing updates, and aren't always forthcoming with all the ports / connections they use. Generally they assume (which I would as well) that most setups are fairly unrestricted outbound, or using software firewalls with program-based rulesets.

Well, I just open everything outbound when playing games (still have kaspersky internet security on) and close everything up againg when Im not on my computer.

Thanks for your input.

[Guest]

Allow all outgoing connections, log it, fire up SC2, and then view the log and see what ports are being used. I'm going to assume it's a dynamic range and you're in for a full, full log file. (For any updates through the blizzard downloader)

@mastablastaz:

@Jahntassa:

@mastablastaz:

Any ideas guys?

Personally i'd be less restrictive with pfSense and utilize a software firewall like Comodo to block unwanted outgoing stuff. Blizzard likes using Bittorrent and other such fun things for doing updates, and aren't always forthcoming with all the ports / connections they use. Generally they assume (which I would as well) that most setups are fairly unrestricted outbound, or using software firewalls with program-based rulesets.

Well, I just open everything outbound when playing games (still have kaspersky internet security on) and close everything up againg when Im not on my computer.

Thanks for your input.