I'm having similar problems with multiplayer Rune. I can get it to work
if I open all UDP ports. I enabled logging of rejected packets, and I
could see the ports that were coming through, but when I enabled them,
it still did not work. I'm probably missing something though. What
exactly do I look for? It shows I guess the IP address it's coming
from, and then a port number, and then it shows my address and I guess
another port number. Which one do I use? Also, it says PROTO=17. Does
that mean protocol? And what is 17? UDP or TCP?
Thanks. Other than that my firewall is working great! Y'all have done
a great job with this!
Michael
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Renaud
Chaillat
Sent: Friday, April 20, 2001 9:29 AM
To: [EMAIL PROTECTED]
Subject: Re: [Cooker-firewall] quake3 with ip_masq_quake
Le Jeudi 19 Avril 2001 12:07, vous avez écrit :
> it's working !
> it's not ip_masq_quake !
> I have open udp high ports (1024:) in internet traffic.
>
> thanks.
You're welcome ;-)
Anyway, you shouldn't leave your firewall box in this state,
especially if you play quake often (a lot of people will see your IP
address
and *will* try to crack your machine).
You should restrict the open udp ports to the only ones you actually
need.
The best way to do this is to close everything, activate the logging of
rejected packets, and watch the logs just after you try to get a list of
servers with quake. You should see the rejected packets in the logs,
with the
port(s) used.
In the future, with kernel 2.4, we should be able to allow this kind of
thing
in a dynamic way, thus not leaving open ports uselessly.
Regards,
Renaud
