All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Capouch <brianc@palaver.net>
Cc: netfilter@lists.samba.org
Subject: Re: Completely NAT an ISP: A practical possibility?
Date: Sat, 15 Jun 2002 17:54:24 -0500	[thread overview]
Message-ID: <3D0BC5A0.2070703@palaver.net> (raw)
In-Reply-To: 200206152233.g5FMXPA27757@Networker.rockstone.co.uk

Antony Stone wrote:
> 
> Just out of interest, how are you proposing to handle bandwidth allocation - 
> making sure each customer gets a reasonable bandwidth without hogging the 
> whole link ?
> 

(Ducking) Still studying that matter, but the current 
candidates-of-record are tc, and cbq, but the Advanced Routing HOWTO is 
about to scare me off from CBQ, even though they admit there that it is 
the "most hyped."

I won't mind any advice in that arena, either :-)

Thx.

B.




  reply	other threads:[~2002-06-15 22:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 22:14 Completely NAT an ISP: A practical possibility? Brian Capouch
2002-06-15 22:33 ` Antony Stone
2002-06-15 22:54   ` Brian Capouch [this message]
2002-06-15 23:17   ` Nick Drage
2002-06-15 23:30     ` Antony Stone
2002-06-17  4:25     ` Sathi
2002-06-17 10:58       ` nat problem umar
2002-06-17 15:46         ` (no subject) skmail
2002-06-17 18:11         ` nat problem Antony Stone
2002-06-18 17:16     ` Completely NAT an ISP: A practical possibility? Rodrigo Senra
2002-06-18 18:50       ` Ramin Alidousti
2002-06-18 20:22         ` Rodrigo Senra
2002-06-18 22:50           ` Ramin Alidousti
2002-06-19 14:36             ` Rodrigo Senra
2002-06-19 15:20               ` Ramin Alidousti
2002-06-20  9:48             ` Antony Stone
2002-06-20 19:37               ` Rodrigo Senra
2002-06-21  0:19                 ` Ramin Alidousti
2002-06-24 18:42                   ` Rodrigo Senra
  -- strict thread matches above, loose matches on Subject: below --
2002-06-15 23:47 hard__ware

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=3D0BC5A0.2070703@palaver.net \
    --to=brianc@palaver.net \
    --cc=netfilter@lists.samba.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.