Re: IPTables Blocking Outbound by destination port.
From: NeoSadist (neosad1st_at_charter.net)
Date: 12/02/03
- Next message: G Klein: "Re: Catch 22 with Norton Internet Security"
- Previous message: NeoSadist: "Re: Linksys BEFSX41 vs. high end firewalls"
- In reply to: Glenn: "IPTables Blocking Outbound by destination port."
- Next in thread: NeoSadist: "Re: IPTables Blocking Outbound by destination port."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 01 Dec 2003 18:18:34 -0700
Glenn wrote:
> I would like to set up some rules to block any internal traffic that
> is destined for any ports other than port 80, and port 443.
> I want to do this to prevent users doing anything other than looking
> at web pages on the internet.
> I would like to make some exceptions to these rules, in that the mail
> server is permitted to access 110, and our I.S team should be given
> unrestricted access to any destination port. (Obviously).
>
> My questions are...
>
> Is this possible with IPTables ?
> How do I go about it ?
> Have I overlooked anything that could cause issues ?
>
>
> With thanks
>
> Glenn
I'd say you need to download and install ethereal on some practice computer
(i.e. unused, if possible). Then sit there and surf the web normally while
recording the packets, stop after about say 100 packets and look at what
you've done.
Then start packet capture again, this time doing things you don't want the
employees to be able to do. You should be able to find some differences.
It is possible with IPTables to do these things. However, some may require
extra things like this:
1. Say you don't want them logging into msn/yahoo/aol/icq/irc from port 80.
You can put a rule at the beginning of the INCOMING chain to not allow
anything to those sites (since the login packets go to a very specific
server in those cases, one not accessed using a browser).
2. Say you don't want them transferring information such as login
information to web email. You can drop packets that contain @hotmail or
such in them.
These are advanced topics, though. However, I'd have to sit down and think
of all the possible "naughty" things I could do on a corporate LAN and get
back with you. As yet, to block msn messenger just block port 1863. Also,
make sure your default policy is to DROP packets (or else your rules will
be useless).
--
Fourth Law of Revision:
It is usually impractical to worry beforehand about
interferences -- if you have none, someone will make one for you.
- Next message: G Klein: "Re: Catch 22 with Norton Internet Security"
- Previous message: NeoSadist: "Re: Linksys BEFSX41 vs. high end firewalls"
- In reply to: Glenn: "IPTables Blocking Outbound by destination port."
- Next in thread: NeoSadist: "Re: IPTables Blocking Outbound by destination port."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|