Ok, the short answer is... You need to figure out what outside-target ports you need to be able to reach and open up the outbound for them, and EITHER: (1) how to tell your programs that do so what ports to use,, OR (2) open up outbound-only above, say, 1050.

Depending on what tool(s) you use for firewalling, you may be able to control what programs can communicate outbound form/to the decided-upon ports.

That's the short version.

rgh.

Joseph wrote:

On Tue, 2005-04-12 at 14:09 -0500, Andrew Gaffney wrote:


Joseph wrote:


Is there a standard port the web-browser connection is going OUT (to
internet) on?


You might want to read up on how TCP/IP works. Outgoing connections are made on
a random (well, not random, but not exactly predictable) port >1024. All ports
<=1024 are restricted for root's use only. If you're trying to do something with
a firewall, trying matching a destination port of 80 instead of the source port.



I'm experimenting with a firewall. I've Stealth all port 0 to 79 and 81 to 1050 and I can connect IN to my server but not OUT.




-- [email protected] mailing list



Reply via email to