From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: ip_conntrack_max
Date: Thu, 8 Jul 2004 18:42:18 +0100 [thread overview]
Message-ID: <200407081842.18007.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <40ED8294.4060103@cisbic.com>
On Thursday 08 July 2004 6:21 pm, Fallucchi Antonio wrote:
> > Why do you want to limit connections per machine? What are you
> > trying to achieve?
>
> The problem are the P2P software that create any connection on the
> conntrack..
> Because filter all p2p port is very difficult, I thought that to limit
> the number of simultaneous connection is a good idea..
I think the right solution for this problem is to connect your internal users
through proxy machines, so they can't do direct P2P connections at all.
What network connections do your users need? Email is SMTP / POP3 / IMAP to
a local server (or a single specified server at your ISP). HTTP / HTTPS /
FTP you can proxy very simply through Squid. DNS should be to a local
caching server only (on the same machine as Squid for good Squid
performance). If you need to allow SSH, then only allow it from one
specific machine on your network, which people have to connect through (and
disable port forwarding).
I can't think of any other protocols you're likely to need, and this should
stop all P2P activity as well as enhance the performance of your network by
using a caching proxy server for the website which can be cached.
> ps: it's ok the signature now?
---------------------------------------------------------------
| ||||||| || | Fallucchi Antonio Giuseppe mat. 2282 |
| || |||| | --> Live free() of die() <-- |
| |||| || || | OpenSource philosophy |
| || |||||||| | Universita' di Bologna sede di Cesena |
| || || || | Cdl di Scienze dell'Informazione |
---------------------------------------------------------------
No, I don't quite think so - I think your want "or" instead of "of" in "Live
free() or die()"?
Regards,
Antony.
--
"When you talk about Linux versus Windows, you're talking about which
operating system is the best value for money and fit for purpose. That's a
very basic decision customers can make if they have the information available
to them. Quite frankly if we lose to Linux because our customers say it's
better value for money, tough luck for us."
- Steve Vamos, MD of Microsoft Australia
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-07-08 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 9:38 ip_conntrack_max Fallucchi Antonio
2004-07-08 9:56 ` ip_conntrack_max Antony Stone
2004-07-08 10:31 ` ip_conntrack_max Fallucchi Antonio
2004-07-08 10:52 ` ip_conntrack_max Antony Stone
2004-07-08 13:13 ` ip_conntrack_max Fallucchi Antonio
2004-07-08 13:29 ` ip_conntrack_max Antony Stone
2004-07-08 17:02 ` ip_conntrack_max Fallucchi Antonio
2004-07-08 17:21 ` ip_conntrack_max Fallucchi Antonio
2004-07-08 17:42 ` Antony Stone [this message]
2004-07-08 15:28 ` ip_conntrack_max James Sneeringer
2004-07-08 9:56 ` ip_conntrack_max Evgeni Vachkov
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 9:34 ip_conntrack_max Fallucchi Antonio
2003-02-13 19:04 ip_conntrack_max homsher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407081842.18007.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox