From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB is being hang my computer :/
Date: Thu, 16 Jun 2005 00:32:33 +0000 [thread overview]
Message-ID: <42B0C8A1.1090006@dsl.pipex.com> (raw)
In-Reply-To: <42A6DA9A.1010900@tlen.pl>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Adis Nezirovic wrote:
>>>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)
I am lucky I don't really have to shape for single duplex.
There are alternatives eg if you only need to do forwarded traffic mark
-i eth0 -o eth1 in forward and visa versa and then jump to imq for the
marked packets just from postrouting.
If you need to include local traffic and don't need to hook imq after
de-nat in prerouting you could use a modified dummy device instead.
Replace drivers/net/dummy.c with the one attached rebuild and you can
shape with it.
I can't find the script I tested but could do another example sometime
if anyone needed.
Andy.
[-- Attachment #2: dummy.c.gz --]
[-- Type: application/x-gzip, Size: 2952 bytes --]
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-06-16 0:32 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
2005-06-16 0:05 ` Andy Furniss
2005-06-16 0:32 ` Andy Furniss [this message]
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=42B0C8A1.1090006@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.