From: jjs <jjs@tmsusa.com>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.64-mm8 breaks MASQ
Date: Tue, 18 Mar 2003 11:43:05 -0800 [thread overview]
Message-ID: <3E7776C9.4040201@tmsusa.com> (raw)
Shawn wrote:
>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?
>
>
I'm seeing a weird problem with later 2.5.64-mm,
probably related - when the problem hits, I have
to "make things work" quickly, so there is not a
lot of time to analyze (booting back into the
latest -ac kernel makes everyone happy)
The box in question, running RH 8.0, is set up
as a dhcp server, iptables firewall, and squid
proxy for a small network of 6 systems (3 linux,
3 ms windows)
After booting up, it all works initially, but after
some time, the windows/dhcp users complain
that they can't get out to the internet anymore.
Very odd, since my internet access via a linux
workstation seems fine - I could just say "wow,
it sure sucks to be a win doze user" and move
on, but I can't quite get away with that...
So the problem is rather interesting, and multi-
faceted - I'm not sure at this point whether the
problems follow the ms windows users, or the
dhcp users, or those not plugged into the same
switch that's in my office... but I'm willing to
try possible fixes through a brute force trial
and error approach.
Joe
next reply other threads:[~2003-03-18 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 19:43 jjs [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 17:29 2.5.64-mm8 breaks MASQ Tom Sightler
2003-03-18 10:52 ` Shawn
2003-03-18 10:55 ` Andrew Morton
2003-03-18 16:38 ` Tom Sightler
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=3E7776C9.4040201@tmsusa.com \
--to=jjs@tmsusa.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