From: Patrick McHardy <kaber@trash.net>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: 2.4.22-bk2 and 2.4.23-pre1 broke routing
Date: Thu, 28 Aug 2003 16:55:41 +0200 [thread overview]
Message-ID: <3F4E17ED.8070801@trash.net> (raw)
In-Reply-To: <20030828140549.GA698@rdlg.net>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Please try this patch, i think it should fix it.
Regards,
Patrick
Robert L. Harris wrote:
>I'm running 2.4.22 now and have a NAT behind my firewall as well as IPv6
>happily run through unixcore.com. I upgraded to 2.4.22-bk2 last night
>to fix an odd problem where I can't ssh-6 to one host. All of a sudden
>it all works within the nat but nothing behind the firewall can get out
>from behind to the real work though the firewall still can. Recompiled
>trying 2.4.23-pre1 and I get the exact same behavior. All 3 use the
>same .config file.
>
>The only noticable change I can see is a bunch of messages:
>
>Aug 27 22:09:10 wally kernel: MASQUERADE: No route: Rusty's brain broke!
>Aug 27 22:09:16 wally kernel: MASQUERADE: No route: Rusty's brain broke!
>Aug 27 22:09:16 wally kernel: MASQUERADE: No route: Rusty's brain broke!
>
>
>As soon as I reverted to 2.4.22 everything works great again. Attaching
>my .config. Please contact me directly if you need any additional
>testing done.
>
>
[-- Attachment #2: x.diff --]
[-- Type: text/plain, Size: 440 bytes --]
===== net/ipv4/netfilter/ipt_MASQUERADE.c 1.6 vs edited =====
--- 1.6/net/ipv4/netfilter/ipt_MASQUERADE.c Tue Aug 12 11:30:12 2003
+++ edited/net/ipv4/netfilter/ipt_MASQUERADE.c Thu Aug 28 16:54:15 2003
@@ -90,6 +90,7 @@
#ifdef CONFIG_IP_ROUTE_FWMARK
key.fwmark = (*pskb)->nfmark;
#endif
+ key.oif = 0;
if (ip_route_output_key(&rt, &key) != 0) {
/* Funky routing can do this. */
if (net_ratelimit())
next prev parent reply other threads:[~2003-08-28 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 14:05 2.4.22-bk2 and 2.4.23-pre1 broke routing Robert L. Harris
2003-08-28 14:55 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 14:36 Marcelo Tosatti
2003-08-28 16:01 ` Patrick McHardy
2003-08-28 23:21 ` David S. Miller
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=3F4E17ED.8070801@trash.net \
--to=kaber@trash.net \
--cc=Robert.L.Harris@rdlg.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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