From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Forwarding bug in kernel 3.14.1 and 3.14.2
Date: Mon, 05 May 2014 20:28:04 -0400 [thread overview]
Message-ID: <53682C94.703@gentoo.org> (raw)
In-Reply-To: <53676EBA.1060305@taydin.org>
On 05/05/2014 06:58 AM, Timur Aydin wrote:
>
> I finally found a bug report that explains the symtom:
>
> http://www.spinics.net/lists/netdev/msg280571.html
>
> I then downgraded the kernel to 3.13.11, which fixed the problem. So,
> all of you guys using your Gentoo PC as your internet gateway, keep
> 3.13.11 around for a while.
>
Thanks for the warning. You should file a Gentoo bug for this -- the
maintainers take the open bugs into consideration when stabilizing
things, so an open bug report for something this critical might prevent
the 3.14.x series from going stable for a while.
Not that you shouldn't post it here as well, I've personally been saved
from disaster twice by posts like these.
prev parent reply other threads:[~2014-05-06 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 10:58 [gentoo-user] Forwarding bug in kernel 3.14.1 and 3.14.2 Timur Aydin
2014-05-06 0:28 ` Michael Orlitzky [this message]
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=53682C94.703@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-user@lists.gentoo.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