All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adis Nezirovic <nezirus@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB is being hang my computer :/
Date: Mon, 13 Jun 2005 19:00:45 +0000	[thread overview]
Message-ID: <748eb71b050613120027c2ed6d@mail.gmail.com> (raw)
In-Reply-To: <42A6DA9A.1010900@tlen.pl>

> > after incoming packets  jump  to ( -i eth0 -j IMQ1) i made another jump when
> > packets leaving out eth1 (-o eth1 -j IMQ1)
> >
> > he he he , results, kernel crash and reboot several times when big packets
> > arrived. So, enough for the try n error, wont try again.

I think kernel panics are triggered by IMQ. I was able to solve that
problem with following rules:

iptables -t mangle -A POSTROUTING -o eth0 -s ! 192.168.100.100 -j IMQ
--todev imq0
iptables -t mangle -A PREROUTING -i eth0 -j IMQ --todev imq0

(eth0 is my internal NIC, with 192.168.100.100 ip address).
i.e. no download shaping from "local machine". By using the same IMQ
and NIC device for both, POSTROUTING and PREROUTING, I am able to
simulate "half-duplex" link. (bandwidth for upload/download is
shared).

tcng works great in the above combination.


Kernel 2.6.11.11 (with ck patches)
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-06-13 19:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 11:46 [LARTC] HTB is being hang my computer :/ Konrad
2005-06-08 12:25 ` Rio Martin.
2005-06-08 12:43 ` Thomas Graf
2005-06-08 12:51 ` Peter Surda
2005-06-08 12:52 ` Konrad
2005-06-08 12:56 ` Konrad
2005-06-08 13:06 ` Thomas Graf
2005-06-08 13:31 ` Rio Martin.
2005-06-08 13:53 ` Konrad
2005-06-09 23:48 ` Andy Furniss
2005-06-10  6:23 ` Rio Martin.
2005-06-13 14:40 ` Andy Furniss
2005-06-13 19:00 ` Adis Nezirovic [this message]
2005-06-16  0:05 ` Andy Furniss
2005-06-16  0:32 ` Andy Furniss

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=748eb71b050613120027c2ed6d@mail.gmail.com \
    --to=nezirus@gmail.com \
    --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.