From: Shawn <core@enodev.com>
To: Tom Sightler <ttsig@tuxyturvy.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.64-mm8 breaks MASQ
Date: 18 Mar 2003 04:52:06 -0600 [thread overview]
Message-ID: <1047984726.3914.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1047922184.3223.2.camel@iso-8590-lx.zeusinc.com>
This actually broke in -mm7, but I don't know what causes it.
I have to admit, I haven't even looked at the patch to see what changed.
Oh well, I suspect good ol' 65-mm1 will fix things up. If so, my TiVo
could stop holding it's breath. ;)
Anyone else seeing this?
On Mon, 2003-03-17 at 11:29, Tom Sightler wrote:
> I have been attempting to test the -mm kernels. I was having problems
> with the anticipatory scheduler up causing the machine to hang during
> loading of the USB driver. The recent fixes that went into -mm8 seem to
> have corrected this problem, unfortunately I'm now hitting another
> issue.
>
> It seems that -mm8 breaks MASQ support in iptables. Actually I can't
> get any MASQ/NAT to work at all. The same exact config works fine with
> vanilla 2.5.64 and 2.5.64-ac4.
>
> Backing out the brlock patches returns everything to normal operation so
> there's something happening with those. I'll try to look at them
> individually if I get a chance but I know practically nothing about that
> code so somebody will probably spot a problem quicker.
>
> Later,
> Tom
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-03-18 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 17:29 2.5.64-mm8 breaks MASQ Tom Sightler
2003-03-18 10:52 ` Shawn [this message]
2003-03-18 10:55 ` Andrew Morton
2003-03-18 16:38 ` Tom Sightler
-- strict thread matches above, loose matches on Subject: below --
2003-03-18 19:43 jjs
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=1047984726.3914.2.camel@localhost.localdomain \
--to=core@enodev.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.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