netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Herz <andi@geekosphere.org>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: ip_route_output_key returns wrong gateway info with specific ip rules
Date: Mon, 12 May 2014 09:55:26 +0200	[thread overview]
Message-ID: <20140512075526.GV10939@kvmbude> (raw)
In-Reply-To: <CAHo-Ooww_a0jXJGQru9E5mGTW4LUqNi6559AWy79wdHErB0Y8w@mail.gmail.com>

Hi Maciej,

thanks for your explanations!

On 10/05/14 at 02:56, Maciej Żenczykowski wrote:
> Easiest fix has been to use iptables mangle prerouting to mark
> packets, thus also forcing a reroute, and then using fwmark ip rules
> instead of (or maybe in addition to) from ip rules.

I can workaround this with marked packets etc., sure.  But i want to
know/learn why the "ip_route_output_key" from route.c function returns a
different value in my scenario although the data it gets via the
parameter is the same and just the ip rule is different.

I guess i have to add debug parts into route.c and dig more into that, i
just thought maybe some developer already knows what the problem might
be.

Thanks.

-- 
Andreas Herz
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-05-12  7:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 13:41 ip_route_output_key returns wrong gateway info with specific ip rules Andreas Herz
2014-05-10  9:56 ` Maciej Żenczykowski
2014-05-10 10:18   ` Maciej Żenczykowski
2014-05-10 10:23     ` Maciej Żenczykowski
2014-05-12  7:55   ` Andreas Herz [this message]

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=20140512075526.GV10939@kvmbude \
    --to=andi@geekosphere.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=zenczykowski@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).