From: Stephen Hemminger <shemminger@osdl.org>
To: Jeroen Hoek <jeroen.hoek@dcf.nl>
Cc: bridge@osdl.org
Subject: Re: [Bridge] Freezing bridges
Date: Fri, 16 Jan 2004 11:07:52 -0800 [thread overview]
Message-ID: <20040116110752.1c70ff18.shemminger@osdl.org> (raw)
In-Reply-To: <1074155350.3994.16.camel@haruka>
On Thu, 15 Jan 2004 09:29:11 +0100
Jeroen Hoek <jeroen.hoek@dcf.nl> wrote:
> On Wed, 2004-01-14 at 21:43, Stephen Hemminger wrote:
> > Sounds like the bridge freezes, but the server doesn't really crash.
> > Is there any console output or message log when this occurs?
> >
> > Are you running spanning tree protocol?
> > Are the machines SMP or UP?
> > What is the output of brctl show and ifconfig when the network freezes?
>
> Well, the servers become unapproachable. Ssh fails (although ping and
> daytime/xinetd work) and attaching a monitor and keyboard to the
> physical machine shows only a blank screen instead of a loginprompt. The
> logs show nothing at all afterwards. There seems to be some life left in
> the server during these freezes, but no ssh or tunnels.
>
> I have STP turned on on the bridges, although there is no chance of a
> networkloop. Should this be turned off?
Unless, you need to discover other bridges turn it off.
Just looking for what could disturb your system after it is running.
In 2.6 (and later 2.4) kernels STP defaults to off, to avoid potential
problems with those that don't need it.
You could try 2.6 (2.6.1) on one machine, it would at least provide information
about whether this problem has already been fixed.
next prev parent reply other threads:[~2004-01-16 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 16:09 [Bridge] Freezing bridges Jeroen Hoek
2004-01-14 20:43 ` Stephen Hemminger
2004-01-15 8:29 ` Jeroen Hoek
2004-01-16 19:07 ` Stephen Hemminger [this message]
2004-01-20 13:11 ` Jeroen Hoek
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=20040116110752.1c70ff18.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=bridge@osdl.org \
--cc=jeroen.hoek@dcf.nl \
/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