TF2 Server - firewall doesn't allow LAN broadcasting?

English Network/Internet
1

I’m trying to set up a dedicated TF2 server (primarily for LAN use) on my openSUSE box, and I’m running into some issues with the firewall. Basically, if I disable the firewall, everything works fine. When I re-enable it, the server can’t be found, even though I’ve opened the necessary ports in YaST->Firewall->Allowed Services. I have a feeling it’s because the broadcast is being blocked, but I can’t for the life of me figure out how to un-block it.

Anyone know how?

2

So pardon my ignorance, but by TF2 do we refer to a Team fortress 2 server by chance? I found a short writeup if true here: Linux dedicated server - TF2 Wiki and indicates you need to open ports 27000-27015 and so I wonder just what ports have been opened?

Thank You,

3

Yeah, it’s a Team Fortress 2 server. And I’ve already opened those ports, but it’s not broadcasting to the network, so the clients can’t see it.

4

Here is some info on ports I found:

Application: TEAMFRT2 External port: 1200 Internal port: 1200 Protocol: TCP/UDP

Application: TEAMFT2A Port range: 27000 - 27015 Protocol: TCP/UDP
Application: TEAMFT2B Port range: 27020 - 27039 Protocol: TCP/UDP

I found it at this link here: Findports - Team Fortress 2 tcp/udp ports list

Does this help any?

Thank You,

5

That doesn’t seem to help. =/

6

So, things are never as simple as they seem. If a Windows server can do it, a Linux one should be able to do better. Perhaps you could use a sniffer program to determine what ports are really being used? You did not mention your openSUSE setup? Why not tell us more about openSUSE including kernel version, memory and so forth as it could be important I think.

Thank You,

7

This is with openSUSE 12.1 using Tumbleweed, so it should be up-to-date. This is the first time I’ve done any firewall configuring, so as far as that’s concerned it should be the same as the default install. Memory and hardware shouldn’t be an issue because it works fine without the firewall.

Kernel version 3.1.10-1.16-desktop.

I will add that YaST’s interface for opening ports is not very self-explanatory, especially with the distinction between “internal zone,” “external zone,” and “demilitarized zone.” I first tried opening up the ports in Custom Rules, then went to Allowed Services, which seems to be more accepted.

8

Well, no others asked why you did nopt mention which version of openSUSE you use. And now the surprise is: Tumbleweed.

We have a special forum for Tumbleweed. Why didn’t you post there?

9

Enable firewall loggin and see what gets dropped. This is a screenshot in polish but the windows should be more or less in the same place :
SUSE Paste

10

This may be of help with determining the ports being listened on:

Linux List The Open Ports And The Process That Owns Them