Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Network Security: Firewall, NAT, QoS, IPS and more

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 01-22-2004, 03:03 AM
Member
 
Join Date: Sep 2003
Posts: 38
Default UT 2003 Packet Filter Rules

Hello,
Has anyone setup packet filter rules to use Unreal Tournament on Astaro. We are not running a game server, just accessing other servers for gameplay. Also if anyone can help me with rules for Halo I would greatly appreciate it.
TIA
Reply With Quote
  #2 (permalink)  
Old 01-22-2004, 04:54 AM
Member
 
Join Date: Sep 2003
Location: Alberta
Posts: 72
Default Re: UT 2003 Packet Filter Rules

[ QUOTE ]
Hello,
Has anyone setup packet filter rules to use Unreal Tournament on Astaro. We are not running a game server, just accessing other servers for gameplay. Also if anyone can help me with rules for Halo I would greatly appreciate it.
TIA

[/ QUOTE ]
Halo:
[ QUOTE ]
MORE INFORMATION
The following DirectPlay ports must be open for you to play a game over a local area network (LAN), to play a direct Internet multiplayer game, or to play a game through GameSpy Internet Matchmaking:

* 80 (Transmission Control Protocol [TCP]) - Halo looks to see if there is a Halo update available. If there is an update, Halo downloads the update through this port.
* 2302 (User Datagram Protocol [UDP]) - the game host listens on this port.
* 2303 (UDP) - the game client connects to the game host through this port.

[/ QUOTE ]
So define new service and set a masq rule based on that service. Then create a new packet file rule based on tha sevice to allow the traffic.
Reply With Quote
  #3 (permalink)  
Old 01-22-2004, 05:03 AM
Member
 
Join Date: Sep 2003
Location: Alberta
Posts: 72
Default Re: UT 2003 Packet Filter Rules

Far as I can find UT2003 uses 7777-7779 range.
So follow the same steps as above to create a masq and packet filter rule.

If something doesn't work check the logs and figure out what was causing the problem.
Reply With Quote
  #4 (permalink)  
Old 01-22-2004, 04:25 PM
Member
 
Join Date: Sep 2003
Posts: 38
Default Re: UT 2003 Packet Filter Rules

Do you mean dnat/snat rules? I can't see how to set masquerading rules based on services. Dnat rules are a little over my head [img]/images/graemlins/confused.gif[/img]
Reply With Quote
  #5 (permalink)  
Old 01-22-2004, 09:00 PM
Member
 
Join Date: Sep 2003
Location: Alberta
Posts: 72
Default Re: UT 2003 Packet Filter Rules

[ QUOTE ]
Do you mean dnat/snat rules? I can't see how to set masquerading rules based on services. Dnat rules are a little over my head [img]/images/graemlins/confused.gif[/img]

[/ QUOTE ]
Yes, sorry. Dnat rules, I was a little tired yesterday. [img]/images/graemlins/wink.gif[/img]
They are very easy to set up. What are you getting stuck on?

Fore example here is my Dnat rule for Warcraft3:
http://members.monarch.net/mcmillan/WC3.png
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 03:30 PM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.