Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Jeroen Hoek <jeroen.hoek@dcf.nl>
Cc: bridge@osdl.org
Subject: Re: [Bridge] Freezing bridges
Date: Wed, 14 Jan 2004 12:43:05 -0800	[thread overview]
Message-ID: <20040114124305.5a68c7c2.shemminger@osdl.org> (raw)
In-Reply-To: <1074096593.12422.1.camel@haruka>

On Wed, 14 Jan 2004 17:09:54 +0100
Jeroen Hoek <jeroen.hoek@dcf.nl> wrote:

> I have the following situation:
> 
> A Linux 2.4.22 server:
> 
> Physical ethernet:
> lan1 - Ethernet port (Internet)
> lan2 - Ethernet port (Cisco Switch, Trunk port)
> 
> Tunnel:
> tap1 - OpenVPN in tcp-server mode
> 
> VLAN's:
> lan2.201
> lan2.202
> lan2.203
> tap1.201
> tap1.202
> tap1.203
> 
> Bridges:
> br201 (lan2.201, tap1.201)
> br202 (lan2.202, tap1.202)
> br203 (lan2.203, tap1.203)
> 
> On the other end, the same type of server:
> 
> Physical ethernet:
> lan1 - Ethernet port (Internet)
> lan2 - Ethernet port (LAN)
> lan3 - Ethernet port (LAN)
> lan4 - Ethernet port (LAN)
> 
> Tunnel:
> tap1 - OpenVPN in tcp-client mode
> 
> VLAN's:
> tap1.201
> tap1.202
> tap1.203
> 
> Bridges:
> br201 (lan2, tap1.201)
> br202 (lan3, tap1.202)
> br203 (lan4, tap1.203)
> 
> Both servers are connected over Internet. This setup works. The server
> with the trunk port actually has more bridges; there are 3 servers that
> connect to it thru an OpenVPN tunnel, and all 3 server have 3 unique
> VLAN's bridged to it.
> 
> The problem is, that although in testing the setup everything runs
> stable, in reality, it doesn't. The first server crashes irregularly,
> but usually after a day or 2/3. The other servers have the exact same
> hardware, and crash aswell, albeit after a longer period of time. There
> is no indication as to what goes wrong. The servers still reply to ping
> and xinetd-daytime, but ssh is gone, as are the tunnels. The log shows
> nothing. The hardware watchdog does not reset and seems to keep
> receiving signals from the kernel module to prevent it from rebooting.
> 
> I don't know anymore. I replaced vtun with OpenVPN for the ethernet
> tunneling, but that does not seem to matter.
> 
> Please advice, I am lost. Would upgrading to kernel 2.6.1 be a valid
> solution? Am I overreaching the possibilities of the bridging
> functionality? Am I overlooking some pitfall?
> 
> With kind and desperate regards,
> 
> ing. Jeroen Hoek
> 
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/bridge

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?

  reply	other threads:[~2004-01-14 20:43 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 [this message]
2004-01-15  8:29   ` Jeroen Hoek
2004-01-16 19:07     ` Stephen Hemminger
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=20040114124305.5a68c7c2.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