All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thhoep" <thhoep@gmx.de>
To: Ramin Dousti <ramin@cannon.eng.us.uu.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Fri, 9 Jan 2004 17:50:41 +0100	[thread overview]
Message-ID: <001601c3d6d0$b8198e10$1684188d@Kiste> (raw)
In-Reply-To: 20040109173530.GC24304@cannon.eng.us.uu.net

> OK. You mean when doing MARK in mangle for ping a -> b, you see both
> ping and pong on ppp4 but the pongs get dropped somewhere between
> PREROUTING and FORWARD. When you remove the MARK from netfilter then
> all works fine??

nonono, the marking isnt the problem. but first:

for marking i use:
"iptables -t mangle -A PREROUTING -i eth4 -s 192.168.0.22 -d 141.24.12.2 -j
MARK --mark-with 1"

for selecting a routing table upon that marking i use:
"ip rule add fwmark 1 table test"

while table test has a local network route, a host route to the ppp peer and
a default route to the internet over the ppp peer as gateway.

the main table is the same but using another ppp interface.

all the other tables only differ only in the way out, but all include the
route to the one and only local net.


back to the problem:
the marking doesnt seem to be the problem. if i let the marking stay and
just remove the upon routing rule and replace it with:
"ip rule add from 192.168.0.22 table test"
then everything works absolutely fine. so i think its something with the
iproute trying to use the firewall mark what drops the packet, because it
seems to disappear while beeing routed.




  reply	other threads:[~2004-01-09 16:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 23:05 Iproute2 and fwmark usage Thhoep
2004-01-09 16:47 ` Ramin Dousti
2004-01-09 16:17   ` Thhoep
2004-01-09 17:35     ` Ramin Dousti
2004-01-09 16:50       ` Thhoep [this message]
2004-01-09 19:42         ` Ramin Dousti
2004-01-09 19:06           ` Thhoep
2004-01-09 20:47             ` Ramin Dousti
2004-01-09 20:09               ` Thhoep
2004-01-09 21:22                 ` Ramin Dousti
2004-01-09 21:30                   ` Thhoep
2004-01-09 22:02                     ` Thhoep
2004-01-11 20:57                       ` Thhoep
2004-01-11 21:07                         ` Antony Stone
2004-01-11 21:50                           ` Thhoep
2004-01-11 23:12                             ` Thhoep
2004-01-11 23:22                               ` Antony Stone
2004-01-13 23:46                               ` Thhoep
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:20 Filter out broadcast messages Gabby James
2004-01-08 14:31 ` iproute2 and fwmark usage Thhoep

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='001601c3d6d0$b8198e10$1684188d@Kiste' \
    --to=thhoep@gmx.de \
    --cc=netfilter@lists.netfilter.org \
    --cc=ramin@cannon.eng.us.uu.net \
    /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.