From: Arun Sharma <arun.sharma@intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reserving "special" port numbers in the kernel ?
Date: 17 Nov 2002 08:37:19 -0800 [thread overview]
Message-ID: <uu1ig9mps.fsf@unix-os.sc.intel.com> (raw)
In-Reply-To: <1037414638.21937.20.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sat, 2002-11-16 at 00:00, Arun Sharma wrote:
> > One of the Intel server platforms has a magic port number (623) that
> > it uses for remote server management. However, neither the kernel nor
> > glibc are aware of this special port.
>
> I can't find it in the IETF standards documents either.
It's been registered as a well known port:
http://www.iana.org/assignments/port-numbers
[..]
>
> > Has anyone run into this or similar problems before ? Thoughts on
> > what's the right place to handle this issue ?
>
> Run your remote management daemon from xinetd, it'll then get the port
> nice and early in the system runtime.
The thing that's unique about our situation is that the daemon in not
user level. It runs at hardware/firmware level, so that you can
remotely administer the machine even when software is malfunctioning.
-Arun
next prev parent reply other threads:[~2002-11-17 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 0:00 Reserving "special" port numbers in the kernel ? Arun Sharma
2002-11-16 0:11 ` Xavier Bestel
2002-11-16 0:53 ` Arun Sharma
2002-11-16 0:58 ` Sean Neakums
2002-11-16 1:00 ` Randy.Dunlap
2002-11-16 1:46 ` Arun Sharma
2002-11-16 2:03 ` Randy.Dunlap
2002-11-16 2:43 ` Alan Cox
2002-11-17 16:37 ` Arun Sharma [this message]
2002-11-17 22:59 ` Alan Cox
2002-11-16 7:30 ` Willy Tarreau
2002-11-17 0:03 ` Chris Wedgwood
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=uu1ig9mps.fsf@unix-os.sc.intel.com \
--to=arun.sharma@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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.