From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>, netdev@vger.kernel.org
Subject: Re: My e1000e GBE card is eating all port 623 pks
Date: Wed, 25 Apr 2012 11:57:47 +0200 [thread overview]
Message-ID: <4F97CA9B.3060105@ens-lyon.org> (raw)
In-Reply-To: <OF497D4E52.CC9EA3C0-ONC12579EB.0031DCB3-C12579EB.003213E4@transmode.se>
On 25/04/2012 11:06, Joakim Tjernlund wrote:
> Jesse Brandeburg<jesse.brandeburg@intel.com> wrote on 2012/04/24 23:51:28:
>> On Sat, 21 Apr 2012 15:31:09 +0200
>> Joakim Tjernlund<joakim.tjernlund@transmode.se> wrote:
>>
>>> Looks like port 623 is some mgmt protocol and our e1000e boards are eating these
>>> pkgs and this trips NIS, finger and yptest hangs for a long time before timing out and
>>> moving on.
>>>
>>> Is there a way to tell the network stack not to eat port 623 pkgs or
>>> have NIS not to use port 623?
>> I think you might be looking for something like portreserve
>> (see man portreserve)
> Seen portreserve on the web(gentoo does not have it) but it seems like a workaround.
> Should not eating port 623 be something one should turn on? Now it is default on
> and I cannot find a way to turn it off.
>
It might be related to IPMI (UDP/623 iirc). Try looking in your BIOS
and/or network firmware config at boot, there might be things to disable
there.
Brice
next prev parent reply other threads:[~2012-04-25 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 13:31 My e1000e GBE card is eating all port 623 pks Joakim Tjernlund
2012-04-24 21:51 ` Jesse Brandeburg
2012-04-25 9:06 ` Joakim Tjernlund
2012-04-25 9:57 ` Brice Goglin [this message]
2012-04-25 10:13 ` Joakim Tjernlund
2012-04-25 16:40 ` Allan, Bruce W
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=4F97CA9B.3060105@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=jesse.brandeburg@intel.com \
--cc=joakim.tjernlund@transmode.se \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.