From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Jared Rhine <jared@wordzoo.com>, xen-devel@lists.sourceforge.net
Subject: Re: [PATCH] xenctld - a control channel multiplexing daemon
Date: Tue, 25 Jan 2005 18:31:06 -0800 [thread overview]
Message-ID: <41F700EA.8010709@diku.dk> (raw)
In-Reply-To: <1106593648.18670.23.camel@localhost>
Anthony Liguori wrote:
> They do not take into account things like endianness into
> consideration. They certainly don't security into account at all. To
> export a proper TCP interface requires a higher level protocol. The TCP
> interface will have to do a certain amount of work to take these things
> into account.
>
> I think we all agree that we need a TCP interface.
No. In my implementation I think I have shown that you can run your
cluster with a much more minimal network-interface.
My current implementation is less than 100 lines of network-facing code
(using ICMP payloads, but the same could be achieved with UDP), though
that increases to about 300 if you count in the SHA-1 implementation
that I am using for verifying customer credentials. So 300 lines is for
a complete solution including crypto and accounting/payment.
My nodes answer ARPs and pings, but that is all.
# nmap -sS blackbox07
Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2005-01-25 18:26 PST
All 1660 scanned ports on blackbox07 are: filtered
Nmap run completed -- 1 IP address (1 host up) scanned in 71.969 seconds
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-26 2:31 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 15:55 [PATCH] xenctld - a control channel multiplexing daemon Anthony Liguori
2005-01-21 16:39 ` Andrew Warfield
2005-01-21 17:19 ` Ronald G. Minnich
2005-01-21 19:59 ` Anthony Liguori
2005-01-21 20:44 ` Ronald G. Minnich
2005-01-21 21:14 ` Anthony Liguori
2005-01-21 20:54 ` Ronald G. Minnich
2005-01-21 21:28 ` Anthony Liguori
2005-01-21 21:37 ` Jared Rhine
2005-01-24 15:33 ` Ronald G. Minnich
2005-01-24 16:35 ` Anthony Liguori
2005-01-24 16:55 ` Jared Rhine
[not found] ` <Pine.LNX.4.58.0501240957520.12186@bluesteel.lanl.gov>
2005-01-24 17:52 ` Jared Rhine
2005-01-24 19:11 ` Anthony Liguori
2005-01-24 19:07 ` Anthony Liguori
2005-01-24 20:44 ` B.G. Bruce
2005-01-26 2:31 ` Jacob Gorm Hansen [this message]
2005-01-26 5:43 ` Anthony Liguori
2005-01-26 6:59 ` Jacob Gorm Hansen
2005-01-21 19:56 ` Anthony Liguori
2005-01-26 0:21 ` Michael Hohnbaum
2005-01-26 14:33 ` Andrew Warfield
2005-01-26 19:31 ` Anthony Liguori
2005-01-26 19:11 ` Andrew Warfield
2005-01-26 20:01 ` Anthony Liguori
2005-01-26 21:21 ` Daniel Stekloff
2005-01-26 22:28 ` Anthony Liguori
2005-01-26 21:57 ` Daniel Stekloff
2005-01-26 21:49 ` Michael Hohnbaum
2005-01-26 22:57 ` Anthony Liguori
2005-01-26 23:55 ` Michael Hohnbaum
2005-01-26 23:59 ` Daniel Stekloff
2005-01-27 7:05 ` Tobias Hunger
2005-01-27 14:19 ` Anthony Liguori
2005-01-27 18:05 ` Daniel Stekloff
2005-01-28 9:17 ` Steven Hand
2005-01-28 16:56 ` Daniel Stekloff
2005-01-27 0:13 ` Daniel Stekloff
2005-01-27 3:48 ` Daniel Stekloff
2005-01-26 23:36 ` Daniel Stekloff
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=41F700EA.8010709@diku.dk \
--to=jacobg@diku.dk \
--cc=aliguori@us.ibm.com \
--cc=jared@wordzoo.com \
--cc=xen-devel@lists.sourceforge.net \
/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.