From: "B.G. Bruce" <bgb@nt-nv.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Other additional vnet questions
Date: Thu, 10 Feb 2005 08:38:57 -0400 [thread overview]
Message-ID: <1108039137.4813.25.camel@master.vms.security> (raw)
In-Reply-To: <420B35DA.2080705@hpl.hp.com>
Mike,
Thanks for your input, it helped a lot, as did getting a box up and
actually running it. I think I have a better grasp of what it does, and
how it does it (for the basics). I guess at first I was hoping it would
be more like one large virtual switch with solid VLAN capabilities. I
see now that it is more like a normal bridge internally, but like having
one or more switches with IPSEC/*S/wan controlling your physical nics.
Some new questions: (I can hear the <groan> from here) :-)
1) for auth and conf security, how is keying handled?
2) how do you set this up other than defining the security model?
3) How can you differentiate between a valid second xend host that is
running vnets, and a rogue xend box (unlikely at this time, but ...)
that got lucky in guessing your vnetid, and security setting.
Regards,
Brian.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-10 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 16:15 Other additional vnet questions B.G. Bruce
2005-02-10 10:22 ` Mike Wray
2005-02-10 12:38 ` B.G. Bruce [this message]
2005-02-10 13:21 ` Mike Wray
2005-02-10 14:39 ` B.G. Bruce
2005-02-10 16:55 ` B.G. Bruce
2005-02-11 23:31 ` Felipe Alfaro Solana
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=1108039137.4813.25.camel@master.vms.security \
--to=bgb@nt-nv.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.