From: "Catalin Borcea" <catalin@electricant.ambra.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] OUTPUT chain marking after or before routing?
Date: Fri, 18 Jul 2003 05:04:47 +0000 [thread overview]
Message-ID: <marc-lartc-105850492017579@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105842045025983@msgid-missing>
----- Original Message -----
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: "Chijioke Kalu" <kchijioke@msn.com>
Cc: <catalin@electricant.ambra.ro>; <lartc@mailman.ds9a.nl>
Sent: Thursday, July 17, 2003 6:55 PM
Subject: Re: [LARTC] OUTPUT chain marking after or before routing?
> Catalin,
>
> >When I try to connect to a smtp port somewhere in the Internet, tcpdump
show
> >me that these packets go to the eth2 interface (the main table default
> >route). I don't know where is my mistake but it seems that the marking in
> >the OUTPUT chain occurs AFTER and not BEFORE routing. Is this a correct
> >behaviour? How can I solve my problem? Please help!
>
> According to my reading of the KPTD (and my understanding), packets
> generated on the local machine have already been routed by the time the
> OUTPUT chain is traversed. See:
>
> http://www.docum.org/stef.coene/qos/kptd/
>
I'm very confused now. Look what is written in the iptables man page:
#############
mangle This table is used for specialized packet alteration. It has two
built-in
chains: PREROUTING (for altering incoming packets before
routing) and OUTPUT
(for altering locally-generated packets before routing).
######################
So how it is? OUTPUT marks packets AFTER or BEFORE routing?
> I see two potential approaches to this problem:
>
> - invert your logic; main routing table uses ppp0 gateway IP as default
> gateway, mark all traffic passing through your router box, and use
> "ip rule add fwmark $MARK table $INTERNET" with another routing
> table for the Internet-bound traffic.
This approach is harder for me because this is a working gateway and I don't
wan't to disturb the users with my tests. But, it is a very good idea and
maybe I will try it.
>
> - send all locally generated traffic via ppp0; "ip rule add iif lo
> table smtp" and watch all traffic generated on the local machine leave
> via ppp0. You'll want to add the locally connected networks to table
> smtp.
I also tried that and it works. But I don't want to send all locally
generated traffic to ppp0. In fact I want only the smtp traffic on ppp0. The
Web traffic (including Squid generated, which is locally generated) must go
to eth2.
Thank you for your reply,
- catalin -
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-18 5:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 5:37 [LARTC] OUTPUT chain marking after or before routing? Catalin Borcea
2003-07-17 6:04 ` ???????? ?????
2003-07-17 6:31 ` Catalin Borcea
2003-07-17 6:37 ` ???????? ?????
2003-07-17 7:15 ` Catalin Borcea
2003-07-17 7:32 ` ???????? ?????
2003-07-17 14:08 ` Chijioke Kalu
2003-07-17 15:55 ` Martin A. Brown
2003-07-17 16:50 ` lartc
2003-07-18 5:04 ` Catalin Borcea [this message]
2003-07-18 18:41 ` Martin A. Brown
2003-07-18 18:46 ` Martin A. Brown
2003-07-19 7:45 ` lartc
2003-07-20 15:19 ` Leonardo Balliache
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-105850492017579@msgid-missing \
--to=catalin@electricant.ambra.ro \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox