From: "Maciej Żenczykowski" <zenczykowski@gmail.com>
To: Andreas Herz <andi@geekosphere.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: ip_route_output_key returns wrong gateway info with specific ip rules
Date: Sat, 10 May 2014 03:23:36 -0700 [thread overview]
Message-ID: <CAHo-Ooz2dCf5L0_w+kjHOG-byg+f0nPMS58bjUE1AnG3MRGE+Q@mail.gmail.com> (raw)
In-Reply-To: <CAHo-OoyP69f=4yvct+gy6rPsS3Dps_Ph=tn1SnRkH0yVS2+2OA@mail.gmail.com>
Btw. Obviously you could just skip the '--syn' match, MARK all tcp
packets to those ports, and rely on fwmark rule for everything (and
not just the SYN packets) and not even bother with the 'from
192.168.100.3' rule.
But that would be boring and not showing the issue at hand. ;-)
next prev parent reply other threads:[~2014-05-10 10:23 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 [this message]
2014-05-12 7:55 ` Andreas Herz
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=CAHo-Ooz2dCf5L0_w+kjHOG-byg+f0nPMS58bjUE1AnG3MRGE+Q@mail.gmail.com \
--to=zenczykowski@gmail.com \
--cc=andi@geekosphere.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).