All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Hickey <bugfood-ml@fatooh.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Massive filtering
Date: Sat, 12 May 2007 21:51:33 +0000	[thread overview]
Message-ID: <464636E5.5080709@fatooh.org> (raw)
In-Reply-To: <200705050130.AA2025718096@ipro.net>

ericr wrote:
> I am trying to build a trafic control rule set for a huge NATed
> network, and I have it working for single known addresses but I need
> to scale it to 16M potential client addresses.  I'm using iptables
> for NAT.  Incoming traffic is simple because I can match destination
> address, outgoing traffic I use iptables IPMARK then tc match mark
> and it works perfectly if I build rules for each client individually.
> I am worried about performance as the client list increases.
> 
> I need to place client IPs into classes like routers, freeloaders,
> lite-access, premium-access, etc. I have no problem with rewriting
> rules on the fly.  It is easy to pop in a rule change any time a user
> authenticates or is disconnected for inactivity.

I don't know what exactly it is you're doing, but here's a thought.

Do you control the allocation of addresses via DHCP? If so, it might be
faster/easier to simply set up IP ranges for your separate classes of user.

10.1.0.0/16        routers
10.2.0.0/16        freeloaders
10.3.0.0/16        ...etc...

Then you can use single matches in iptables/tc to identify packets
to/from each class.

-Corey
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-05-12 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  5:30 [LARTC] Massive filtering ericr
2007-05-05  6:15 ` Vladimir Vitkov
2007-05-08 18:10 ` Stanislav Kruchinin
2007-05-12 21:51 ` Corey Hickey [this message]

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=464636E5.5080709@fatooh.org \
    --to=bugfood-ml@fatooh.org \
    --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.