From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Packet marking for ingress shapping and NET
Date: Mon, 10 May 2004 20:09:17 +0000 [thread overview]
Message-ID: <409FE16D.7010909@dsl.pipex.com> (raw)
In-Reply-To: <409F5528.2070201@brn.czn.cz>
Patrick Spousta wrote:
> It looks working fine :-) I never found any details about IMQ and NAT
> patch, it looks that packet processing in kernel has path
>
> | PREROUTING chain |
> input interface -> contrack -> mangle -> nat -> imq
So which IMQ did you use - did you need to patch for NAT (there are
different versions about)
> ESFQ works fine, but only for ingress shapping over imq and NAT with
> destination hash (= download on private IPs). I'm trying to setup ESFQ
> on egress shaping for traffic from private to public IPs with source
> hash (upload from private) but qdisc sits after NAT, ie. packets source
> addresses are always the same public IP of external (wan) interface :-(
>
> I try to use imq for egress shapping (on POSTROUTING chain), may it helps
I don't think IMQ will help - but you can mark local src in postrouting
mangle OK. If you really want to use esfq, someone posted a patch on
here a while back which made esfq hash on fwmark.
Andy.
_______________________________________________
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-05-10 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 10:10 [LARTC] Packet marking for ingress shapping and NET Patrick Spousta
2004-05-10 10:59 ` Andreas Klauer
2004-05-10 12:06 ` Andy Furniss
2004-05-10 12:31 ` [LARTC] Packet marking for ingress shapping and NAT Patrick Spousta
2004-05-10 12:35 ` [LARTC] Packet marking for ingress shapping and NET Patrick Spousta
2004-05-10 13:48 ` Andy Furniss
2004-05-10 20:09 ` Andy Furniss [this message]
2004-05-11 4:25 ` [LARTC] Packet marking for ingress shapping and NAT Patrick Spousta
2004-05-11 13:13 ` 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=409FE16D.7010909@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.