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 13:48:51 +0000 [thread overview]
Message-ID: <409F8843.1020503@dsl.pipex.com> (raw)
In-Reply-To: <409F5528.2070201@brn.czn.cz>
Patrick Spousta wrote:
> Hi
>
> Andy Furniss wrote:
>
>>> Does exists solution how to NAT and MARK in PREROUTING, but in this
>>> order?
>>>
>>
>> If you really need to shape for local and forwarded on ingress then
>> you use IMQ + the IMQ NAT patch and use u32 to filter on dst IP (if
>> you are masquerading a dynamic IP mark LAN traffic and use default for
>> local).
>
>
> It sounds good, but can you be more conrete?
Using IMQ generally or a script? - mine is pretty lame, unfinished and
needs netfilter patches, though I suppose it could give an indication of
what to do - I am still learning HTB myself, but have got sidetracked at
the moment playing with esfq.
There is a new imq website www.linuximq.net from which you should be
able to get imq working for whatever kernel you use. I don't know if
they include the NAT patch yet - but it's only a couple of lines and
should apply OK. If you happen to use 2.4.24 I can give urls for the
patches I use.
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 13:48 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 [this message]
2004-05-10 20:09 ` Andy Furniss
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=409F8843.1020503@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.