All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Monitoring problem,
Date: Wed, 23 Apr 2003 20:06:03 +0000	[thread overview]
Message-ID: <marc-lartc-105112846022881@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105099580521956@msgid-missing>

> > > i have downloaded monitor_tc.pl, and try to monitor my imq0 Device
> > That's from docum.org.
> Yes I have downloaded from Docum.org and i have changed from eth0 to imq0
I said that for the other members of the list so they know what monitor_tc.pl 
is.

> > > modprobe imq numdevs=1
> > >  tc qdisc add dev imq0 handle 1: root htb default 1
> > >  tc class add dev imq0 parent 1: classid 1:1 htb rate 1mbit
> > >  tc qdisc add dev imq0 parent 1:1 handle 10: htb default 5
> > Adding a htb qdisc to a class is useless and will only add extra delays.
> Ok i understand now, let me correct it, since let it be delay the
> proceedure should work right ?
Yes.  It works with that extra qdisc.

> > If you upload, the packets are entering the box with destination address
> the
> > ip-address of your box.  I'm not sure when the packet gets demasqued but
> when
> > this happens AFTER the marking, your packets have not the dst address of
> your
> > host so they are not marked and they end up in the default class.
> See while iam uploading to test FTP Server,
> i have table which all the packets which is belong to ftp  or any to go to
> IMQ Device
> and while iam downloading also the same
> Please correct if iam wrong
Sorry, bot our english is not so good.  I have no idea about what you want to 
say.

> i have lot of  individual clients, who required up+down=total b/w
> so for each customer i need to have different IMQ Device or
> all can be used with one IMQ Device , and make some classes  for each IP to
> solve the problem
You can create 1 imq device and give each client a class.  So each client has 
his traffic in his own class.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  parent reply	other threads:[~2003-04-23 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22  7:37 [LARTC] Monitoring problem, hare ram
2003-04-23  5:29 ` hare ram
2003-04-23 20:06 ` Stef Coene [this message]
2003-04-24  5:47 ` hare ram
2003-04-24 19:15 ` 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-105112846022881@msgid-missing \
    --to=stef.coene@docum.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.