From: Patrick McHardy <kaber@trash.net>
To: Jay Libove <libove@felines.org>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] BitTorrent still crashes Linux firewall running bridging :-(
Date: Thu, 29 Nov 2007 17:45:21 +0100 [thread overview]
Message-ID: <474EECA1.2090100@trash.net> (raw)
In-Reply-To: <8A55DBB97B4FBF4D9A6F23C92FE0F117EA45D6@BE08.exg3.exghost.com>
Jay Libove wrote:
> Unfortunately, I did speak too soon, dammit. Even after replacing the
> Quad Tulip card with three independent Ethernet cards, BitTorrent
> (actually, Azureus) downloads are still regularly crashing this Linux
> firewall running bridging.
>
> So, back to the drawing board. What's the next diagnostic step? I guess
> I could just kill the VoIP device for a day or two. Who needs home phone
> service, anyway? Oh, yeah, wait, my wife... So, next diagnostic steps,
> please?
Try capturing an oops using serial console or netconsole and post it.
next prev parent reply other threads:[~2007-11-29 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200711282000.lASK04sR013906@smtp2.linux-foundation.org>
2007-11-29 13:33 ` [Bridge] BitTorrent still crashes Linux firewall running bridging :-( Jay Libove
2007-11-29 16:45 ` Patrick McHardy [this message]
2007-11-29 22:16 ` [Bridge] bridge in 'hub' mode possible? kevin
2007-11-29 22:52 ` Stephen Hemminger
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=474EECA1.2090100@trash.net \
--to=kaber@trash.net \
--cc=bridge@lists.linux-foundation.org \
--cc=libove@felines.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