From: Unknown <borg@uu3.net>
To: Patrick McHardy <kaber@trash.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 16216] New: wrong source addr of UDP packets when using policy routing
Date: Tue, 22 Jun 2010 11:21:26 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1006221120150.23555@cube> (raw)
In-Reply-To: <4C2053A8.4040400@trash.net>
Hmm. This is not an option.
Okey, thx for info. Seems its time for some hack & slash ;)
---------- Original message ----------
From: Patrick McHardy <kaber@trash.net>
To: Unknown <borg@uu3.net>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>, netdev@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 16216] New: wrong source addr of UDP packets when
using policy routing
Date: Tue, 22 Jun 2010 08:09:44 +0200
Message-ID: <4C2053A8.4040400@trash.net>
Unknown wrote:
> Okey. Did you people came into any conclusions?
> Is there a patch I can test?
As I said, its known and expected behaviour and there's nothing
netfilter can do about it. You could patch your application to use
the SO_MARK socket option to set the socket mark.
prev parent reply other threads:[~2010-06-22 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16216-10286@https.bugzilla.kernel.org/>
2010-06-16 16:33 ` [Bugme-new] [Bug 16216] New: wrong source addr of UDP packets when using policy routing Andrew Morton
2010-06-16 16:46 ` Patrick McHardy
2010-06-16 17:28 ` Eric Dumazet
2010-06-16 17:43 ` Patrick McHardy
2010-06-18 9:56 ` Unknown
2010-06-22 6:09 ` Patrick McHardy
2010-06-22 9:21 ` Unknown [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=Pine.LNX.4.64.1006221120150.23555@cube \
--to=borg@uu3.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@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).