All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis" <alexis@tpys.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] making a traffic shaper for wireless users
Date: Sun, 06 Jun 2004 15:03:52 +0000	[thread overview]
Message-ID: <006f01c44bd7$7af38cd0$0200000a@heretic> (raw)

Hello all,

Im new using tc, ive been reading the howto at least 2 or 3 times, but there's a
lot information to aquire all of it quickly.

I've installed a linux box as firewall for a wireless Network in a hotel, this
box is a radius for the access points and it uses iptables to redirect and
permit/deny the customers to use the net. So it uses iptables to count the bytes
to restrict the user using the bytes transferred.

Now i have to create a different bandwith restrictions, i've testing using
iptables to mark the users and then restrict the bandwith, but it was in a lab
scenario, my question is


if i create suppose a classifier for 64kbps, 128kbps, 256kbps and so on. do i
have to create different classifiers for each customer? or just sending 2 or
more customers to the 128kbps lane, both of them will have 128kbps to use and
not 128/users?


to restrict incoming and outgoing, i need to set a classifier in both
interfaces? for incoming traffic the classifier goes to the LAN interface and
for outgoing traffic in the WAN? of course switching the source/destination
information at the iptables rules used to mark.


Thank you.




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

             reply	other threads:[~2004-06-06 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-06 15:03 Alexis [this message]
2004-06-06 23:30 ` [LARTC] making a traffic shaper for wireless users Damion de Soto

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='006f01c44bd7$7af38cd0$0200000a@heretic' \
    --to=alexis@tpys.com.ar \
    --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.