From: Bill Gradwohl <bill@ycc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] NAT & tc filter addresses
Date: Thu, 05 Aug 2004 16:47:56 +0000 [thread overview]
Message-ID: <411264BC.40801@ycc.com> (raw)
Is there a flow diagram as to where tc actions take place with respect
to NAT and other iptables functions on a multihomed box (private &
public NICs) ? Are tc filter rules consulted before or after NATing?
My real interest is in basic understanding first, and then solving a
real problem second.
Example:
Firewall Public NIC 123.123.123.1
Firewall Private NIC 192.168.168.1
Dedicated Video Conferencing equipment @ 192.168.168.100
I'd like to write a rule that says any traffic emanating from the
private .100 box gets 128kbit of bandwidth out of a T1's total 1.55mbit
as the traffic heads out on to the Internet to find the other end of the
Video Conference.
The shaping occurs on the Public NIC, but the only address I have to
work with is a private address. By time the traffic hits the public NIC
and tc rules are applied, I suspect the packet no longer has a source IP
of private .100, but has been NAT'd to the public NIC address. There's
no way to distinguish private .100's traffic via IP address. by time the
tc filters are queried. Is that correct?
What methods are available to do this? I can think of marking all the
packets on the private side then looking for the marks on the public
side. Or, NAT private.100 to a specific Public IP and then write rules
for that new Public IP. What other options are there?
--
Bill Gradwohl
bill@ycc.com
http://www.ycc.com
SPAMstomper Protected email
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-08-05 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 16:47 Bill Gradwohl [this message]
2004-08-05 20:04 ` [LARTC] NAT & tc filter addresses Stef Coene
2004-08-06 5:32 ` Martin A. Brown
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=411264BC.40801@ycc.com \
--to=bill@ycc.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.