PDA

View Full Version : firewall rules for UT2004


legacy-fdfhtdyhsfrh
09-18-2005, 08:41 PM
currently i have given unreal full access in outpost firewall pro but i was wondering if there are any more specific or tighter rules i can use. id prefer not to let ut have full internet access.
legacy-fdfhtdyhsfrh
09-27-2005, 08:47 PM
bump
legacy-NiTrOcALyPsE
09-27-2005, 09:15 PM
I don't think so. Why would you not want UT2004 to have full internet access?
legacy-fdfhtdyhsfrh
10-01-2005, 01:25 AM
security reasons? i just wanted to know if there was any specific firewall rules or guidelines that either Epic or someone could suggest.
Spaz
10-01-2005, 01:28 AM
From the [Ultimate Faq Guide]

The default ports are:

7777 UDP/IP (Game Port)
7778 UDP/IP (Query Port)
7787 UDP/IP (GameSpy Query Port)
28902 TCP/IP (Allows your Server to Connect to the UT2004 Master Server Browser)
legacy-fdfhtdyhsfrh
10-01-2005, 01:33 AM
thank you, would u mind helping me put those rules into outpost?
Spaz
10-01-2005, 02:07 AM
Originally posted by fdfhtdyhsfrh
thank you, would u mind helping me put those rules into outpost?

Never used outpost so I wouldn't be much help.
legacy-fdfhtdyhsfrh
10-01-2005, 11:52 AM
ok but at least help me understand teh rules. iirc, udp doesnt need to have a direction specified so for the first three rules i can ignore the direction of teh packets. am i correct? also what do the rules mean bu udp/ip whats ip for? and for tcp, which direction should i specify, inbound, outbound or both. and lastly, hopefully not a stupid question, but these are for my local ports right?
NakedApe
10-01-2005, 12:04 PM
Originally posted by Spaz007
From the [Ultimate Faq Guide]

The default ports are:

7777 UDP/IP (Game Port)
7778 UDP/IP (Query Port)
7787 UDP/IP (GameSpy Query Port)
28902 TCP/IP (Allows your Server to Connect to the UT2004 Master Server Browser)

These kinds of rules are stupid for clients since it will limit you to servers that run on that particular port. They are meant for servers.

Most firewalls by default allow any outgoing traffic from internal clients so you shouldn't have to do anything to play.

What makes you think you gain any security by limiting the connectivity of UT2k4?
Spaz
10-01-2005, 03:07 PM
Originally posted by NakedApe
Most firewalls by default allow any outgoing traffic from internal clients so you shouldn't have to do anything to play.


I would suggest using a different firewall that at least asks for outgoing access.
legacy-fdfhtdyhsfrh
10-01-2005, 06:59 PM
ill just continue letting UT2004 have full internet access, also i have one other question. look n stop firewall has rules on their website for UT, are they based on the rules Spaz007 mentioned?
NakedApe
10-02-2005, 12:57 PM
Originally posted by fdfhtdyhsfrh
ill just continue letting UT2004 have full internet access, also i have one other question. look n stop firewall has rules on their website for UT, are they based on the rules Spaz007 mentioned?

I wouldn't know. But trying to limit the outgoing connectivity of UT2k4 is an exercise in futility if you want to be able to play on "any server". Plus it does not give you any extra security to speak of. Inbound connectivity should be limited to, in the case of a game client, traffic matching the state tables for your outgoing connections in any firewall worth it's name and there is really not much to improve there.

Spaz: You right of course. I meant most firewalls allow any outgoing traffic by default when an application has been granted permission.