From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NAT and CBQ
Date: Mon, 08 Jul 2002 09:39:11 +0000 [thread overview]
Message-ID: <marc-lartc-102612122924564@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102610935315892@msgid-missing>
On Mon, Jul 08, 2002 at 09:45:38AM +0300, Daniel Sercaianu wrote:
>
> The same problem I encountered myself when I try to SNAT some ip's
> going through my router. The incoming is shaped ok but the outgoing
> doesn't seem to hit my rules. I think when the traffic leaves the outgoing
> interface isn't caught in the filter rules because the source address of
> the packets is already changed with the address specified in the SNAT
> rules or with the address of the outgoing interface if you do masquerade.
> To make some shapers, I think you have to shape the ip of the outgoing
Exactly - once tc 'sees' your packets they have everything done to them
already. Every translation by then will have finished.
> interface, but this only works if you want to shape globally only one
> filter rules because there is only one ip of the outgoing interface you can catch it in
> the filter rules. If someone can give any clues how we can solve this
> problem please help us.
Add fwmarks - they survive the NAT process and tell you where packets came
from. The HOWTO details this.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-07-08 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 6:21 [LARTC] NAT and CBQ Fozzie
2002-07-08 6:45 ` Daniel Sercaianu
2002-07-08 9:39 ` bert hubert [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=marc-lartc-102612122924564@msgid-missing \
--to=ahu@ds9a.nl \
--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.