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] IMQ+HTB problem
Date: Tue, 15 Apr 2003 16:51:24 +0000	[thread overview]
Message-ID: <marc-lartc-105042556203227@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105040846112114@msgid-missing>

> > Never add a htb qdisc to a htb class.  It will only add extra delays.
> WHAT IS RECOMENDED
Only use classes.  You don't need the qdiscs.

> > >  iptables -t mangle -A POSTROUTING -p tcp --dport 80 -j IMQ

> > > Chain POSTROUTING (policy ACCEPT 121733 packets, 17224986 bytes)
> > >     pkts      bytes target     prot opt in     out     source
> > > destination
> >
> > Euh.  Where is your iptables command ????
>
> YES IAM WONDERING WHERE IS THE RULE GONE, THIS IS WHAT MAIN PROBLEM, SEE
> ABOVE I HAVE EXECUTED THE IPTABLE LINE
I know.  
Are you sure you can execute the iptables command and you didn't had any 
errors?  If I do this on my box (I just did iptables -t mangle -A POSTROUTING 
-p tcp --dport 80) and get a list of the iptables rules, I can see the rule I 
added.  So it works.  Can you check it again ?

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-15 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 12:29 [LARTC] IMQ+HTB problem hare ram
2003-04-15 13:23 ` Stef Coene
2003-04-15 13:57 ` hare ram
2003-04-15 16:51 ` Stef Coene [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 18:31 [LARTC] IMQ & HTB problem Alin Nastac
2002-04-21  1:33 ` Patrick McHardy

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-105042556203227@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.