From: Jeff Wiegley <jeffw@csun.edu>
To: netfilter@vger.kernel.org
Subject: marking/mangling of local packets for altering routes?
Date: Wed, 22 May 2013 12:30:23 -0700 [thread overview]
Message-ID: <519D1CCF.2030707@csun.edu> (raw)
I'm trying to do to some service based routing using the "ip rule" and
"ip route"
by marking packets.
I'm confused by: http://www.iptables.info/en/structure-of-iptables.html
For forwarded packets (those generated on another machine, passing through
my router) it is obvious that I can mark all my traffic for routing in
the mangle
table's PREROUTING chain just like I want to.
But Table 6-2 Source Local host (our own machine) indicates that traffic
generated on the routing machine itself (say you are logged in and want to
SSH to another box) can't be marked for special routing. According to the
table the routing decision for these packets happens before ANY iptables
table
or chain is consulted.
This is problematic. I have two interfaces
eth0 and eth1 and each has a default route associated with it. I want
certain
traffic to go out eth0's gateway as the default and the rest of the
traffic I want
to go out eth1. But according to Table 6-2 I cannot make such routing
decisions
for locally generated packets. Only those forwarded from another machine.
That lack of ability to traffic shape local traffic seems unreasonable.
Is Table 6-2
only taking about 127.0.0.1 (and the IPv6 equivalent) when they are talking
about "Source Local Host"? Or can you really not traffic shape all
locally generated
outbound traffic?
Thank you.
next reply other threads:[~2013-05-22 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 19:30 Jeff Wiegley [this message]
2013-05-22 20:22 ` marking/mangling of local packets for altering routes? Bryan Harris
2013-05-23 17:39 ` Jeff Wiegley
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=519D1CCF.2030707@csun.edu \
--to=jeffw@csun.edu \
--cc=netfilter@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.