All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Evans <pevans@catholic.org>
To: lartc@vger.kernel.org
Subject: [LARTC] throttling individual dhcpd clients
Date: Sun, 02 Mar 2003 21:21:07 +0000	[thread overview]
Message-ID: <marc-lartc-104664053907976@msgid-missing> (raw)

I have 2 multipathed external links and one internal link which has dhcpd on 
it and is masqueraded.

I have begun with ahu's script on the two external links and things look good 
there too.

At this point I am only using the ingress policer on each external, but want 
to use a tbf (or recommendation) on the internal interface instead.

The thing is, it is needed that each lease be given a certain amount of 
bandwidth with borrowing. I don't think there is any good way to do this 
other than building each of them their own qdisc.

I wonder if anyone has any tips one how to keep the rules in sync with the 
dynamic nature of the ip's? I suppose, one could just build for all 
possibilities. Also, I read somewhere that a script could be named dhcpd.exe 
which would run after each lease and thought that might be the way to go.

Thoughts? I'd especially like to hear someone call me an idiot for thinking it 
would have to be that complicated...

-- 
Regards, Paul Evans


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-03-02 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 21:21 Paul Evans [this message]
2003-03-08 20:14 ` [LARTC] throttling individual dhcpd clients Stef Coene

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-104664053907976@msgid-missing \
    --to=pevans@catholic.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.