From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>,
"David S. Miller" <davem@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.22-bk2 and 2.4.23-pre1 broke routing
Date: Thu, 28 Aug 2003 11:36:18 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.55L.0308281134120.9167@freak.distro.conectiva> (raw)
David?
---------------------------
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.
Dual AMD Athalon
512Megs of ram
00:0a.1 I2O: Distributed Processing Technology SmartRAID V Controller (rev
02)
(Adaptec I20 SCSI controller, no hardware or software raid in use
though)
00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev
02)
00:0d.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
Robert
next reply other threads:[~2003-08-28 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 14:36 Marcelo Tosatti [this message]
2003-08-28 16:01 ` 2.4.22-bk2 and 2.4.23-pre1 broke routing Patrick McHardy
2003-08-28 23:21 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 14:05 Robert L. Harris
2003-08-28 14:55 ` Patrick McHardy
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.55L.0308281134120.9167@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=Robert.L.Harris@rdlg.net \
--cc=davem@redhat.com \
--cc=linux-kernel@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).