All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Gaissmaier <karl.gaissmaier@rz.uni-ulm.de>
To: lartc@vger.kernel.org
Subject: [LARTC] Q: best solution to stop traffic to huge amount of unregistered hosts
Date: Thu, 22 Aug 2002 07:38:58 +0000	[thread overview]
Message-ID: <marc-lartc-103000210313805@msgid-missing> (raw)

Hi

perhaps someone else already had the same problem.

Problem description:

I'm running a class B University network with approx 10k hosts
attached. I would now like to stop traffic from and to hosts
in my network not already registered in my DNS server.

This means I've to handle with approx 50k rules|routes. Sure
I can summarize the unalloctaed address space a little bit
with masks to approx 30k rules, anyway this seems to be a problem.

Question:

What will be the best solution between the different choices
netfilter/iptables, ip route(s) ... type prohibit and
tc filter ... u32 ... police 0kbps

netfilter/iptables doesn't seem to scale well and the only
match module "pool" which is able to deal with pools of addresses
seemes to stay in alpha state.


With ip route I think I have to describe all unregistered hosts
to stop traffic and not the smaller amount of registered hosts.
Does the FIB and route cache scale well to approx 30k routes?

Is it possible and more performant to use tc to throttle down
traffic to unregistered hosts already in the ingress lane
without hitting the routing and netfilter engine with this
traffic? Does tc scale well with this huge amount addresses/masks?

How could this be handled with tc?

Regards and thanks in advance for any hint
	Charly

P.S. Speed is important, this linux router/firewall connects
Gigabit Ethernet networks

-- 
Karl Gaissmaier          Computing Center,University of Ulm,Germany
Email:karl.gaissmaier@rz.uni-ulm.de          Network Administration
Tel.: ++49 731 50-22499
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-08-22  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22  7:38 Karl Gaissmaier [this message]
2002-08-22 20:44 ` [LARTC] Q: best solution to stop traffic to huge amount of Karl Gaissmaier
2002-08-22 20:55 ` Karl Gaissmaier
2002-08-22 21:04 ` Karl Gaissmaier
2002-09-03 11:13 ` Karl Gaissmaier

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=marc-lartc-103000210313805@msgid-missing \
    --to=karl.gaissmaier@rz.uni-ulm.de \
    --cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.