Now this makes sense... Now how will the ! -y option affect this for
TCP? What about UDP? It's hanging out there in the breeze right?
-----Original Message-----
From: Wil Cooley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 5:10 PM
To: Scott H
Cc: [EMAIL PROTECTED]
Subject: Re: Chains question
Thus spake Scott H:
> In many IPchains scripts I see ports above 1024 set to accept in-bound
> traffic on TCP and UDP. There is usually a comment to the effect of
> ports above 1024 are fair game. Could some one explain why this is
> considered to be ok? In my case I am using a linux firewall
for my home
> network.
You need to allow ports above 1024 to be connected to if you're going
to be running any clients on the firewall, like SSH. What happens is
that a client requests a randomly-assigned high port that forms the
local end of the connection.
Wil
--
W. Reilly Cooley [EMAIL PROTECTED]
Naked Ape Consulting http://nakedape.cc
LNXS: Get 0.2.0-devel at http://sourceforge.net/projects/lnxs/
irc.openprojects.net #lnxs
"The only way for a reporter to look at a politician is down."
-- H.L. Mencken
_______________________________________________
Firewalls mailing list
[EMAIL PROTECTED]
http://lists.gnac.net/mailman/listinfo/firewalls
