All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: [LARTC] RPDB && routing locally generated (and marked) traffic
Date: Wed, 04 Sep 2002 05:25:16 +0000	[thread overview]
Message-ID: <marc-lartc-103111715002020@msgid-missing> (raw)

Hello all,

I'm using iproute2 + ipchains and have a question about locally generated 
packets.

I have noticed that I have no problem marking packets in the input chain 
from sources other than my router.  These packets are marked and routed 
exactly as I expect.

Now supposing I want to mark particular outbound packets which are locally 
generated.  The only solution I have found so far
(http://www.quintillion.com/moat/ipsec+routing/iproute2.html) suggests

# ip rule add iif lo lookup $other

But the side effects are tremendous.  All of the processes on this box 
suddenly start using the $other routing table (exactly as I told them 
to!), which is not what I desire.

If I try marking the special locally generated packets with

# ipchains -I input -p tcp -s $OUTIF $PORT -d $ALL -m $other -j ACCEPT

nothing changes.  The return traffic ends up flowing out my main link 
according to my main routing table.

When I look at the ipchains HOWTO on how packets traverse filters,

  http://www.tldp.org/HOWTO/IPCHAINS-HOWTO-4.html#ss4.1

I fear that the routing decision has already been made by the time the 
local process is generating a packet.

Is there any way around this problem?

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com






_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2002-09-04  5:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-103111715002020@msgid-missing \
    --to=mabrown-lartc@securepipe.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.