All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivan Groenewald" <ivan@office.adept.co.za>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] tc ip group
Date: Fri, 20 Jun 2003 08:48:21 +0000	[thread overview]
Message-ID: <marc-lartc-105609899314973@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105609792614046@msgid-missing>

I have only used u32 in the past.

On the LAN I still have to decide. Marking the packets with Iptables
sounds like a good idea and is quite simple.

How would I setup tc to match the marked packets (sorry I'm a bit lazy
to rtfm today :-))

Regards
Ivan




-----Original Message-----
From: Giannis Stoilis [mailto:giannis@stoilis.gr] 
Sent: Friday, June 20, 2003 10:42 AM
To: Ivan Groenewald
Cc: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] tc ip group


----- Original Message ----- 
From: "Ivan Groenewald" <ivan@office.adept.co.za>
To: <lartc@mailman.ds9a.nl>
Sent: Παρασκευή, 20 Ιουνίου 2003 11:28 πμ
Subject: [LARTC] tc ip group


> Is it possible to classify traffic by ip groups ?

How do you classify your packets? u32?
Generally speaking, I have many problems with the u32 classifier. Now, I
do marking with IPtables, which has power to do just about anything
anyone could ever want... Including the exceptions you want. Have you
tried it?

- Giannis


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

  parent reply	other threads:[~2003-06-20  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20  8:28 [LARTC] tc ip group Ivan Groenewald
2003-06-20  8:42 ` Giannis Stoilis
2003-06-20  8:48 ` Ivan Groenewald [this message]
2003-06-20  9:11 ` Giannis Stoilis

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-105609899314973@msgid-missing \
    --to=ivan@office.adept.co.za \
    --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.