From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Little problem with IMQ
Date: Wed, 11 Aug 2004 03:05:48 +0000 [thread overview]
Message-ID: <009801c47f50$1a780140$030aa8c0@t> (raw)
In-Reply-To: <003501c47e25$a7aae0e0$4603a8c0@neo>
Originaly this always was imq problem, because prerouting and postrouting
hooks do not alow do what you want.
you can only capture all ingress, or all egress which is same as usual tc
just unstable.
you can change imq source to hook on other places, like input and forward.
or you can use my version where I already did that.
http://pupa.da.ru/imq/
----- Original Message -----
From: "Lenthir" <lth@wp.pl>
To: "$LARTC" <lartc@mailman.ds9a.nl>
Sent: Tuesday, August 10, 2004 11:47 AM
Subject: Re: [LARTC] Little problem with IMQ
> rc.htb is now working for me. But packet addressed to server don't match
> correct class.
>
> htb1.2rc3 don't work because i can't discern traffic to LAN and traffic to
> server.
>
> in script
> prs it is address of server
> lan[0], lan[1] - lists of IP address to each interfaces... (defined in
> dev_lan)
>
> I tried on two types of compiled kernel - 2.4.26 with only IMQ patch and
> 2.4.26 with IMQ and NAT patch.
> I don't see any differences...
>
> I have iptables 1.2.11 compiled with the kernel.
>
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-08-11 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 15:29 [LARTC] Little problem with IMQ Lenthir
2004-08-09 21:03 ` Andre Correa
2004-08-10 8:47 ` Lenthir
2004-08-11 3:05 ` Roy [this message]
2004-08-11 7:47 ` Lenthir
2004-08-11 9:56 ` Lenthir
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='009801c47f50$1a780140$030aa8c0@t' \
--to=roy@xxx.lt \
--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.