All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xen.org
Subject: Re: Best way to get IP addresses from VMs without logging in to them?
Date: Wed, 11 Jun 2014 16:40:12 +0000	[thread overview]
Message-ID: <20140611164012.GG21583@bitfolk.com> (raw)
In-Reply-To: <CAHehzX2jLYYa7JZ2Kh5ZMWHULs3atTrLO+xd3hf_jNDvKOxTpw@mail.gmail.com>

Hello,

On Wed, Jun 11, 2014 at 12:32:50PM -0400, Russ Pavlicek wrote:
> Is there a better way to programmatically do this?  If so, we need to
> document it in the Wiki (and I'd be glad to work on that).  But how
> can we do this simply?

I'd rather route only the (blocks of) IPs that I want the VM to have
to the VM, not let them set any they like. That way I know what they
have (because I routed it to them) and I know they can only use what
they were given.

If I had to use DHCP though, I'd be using the DHCP logs for the
MAC/IP mapping.

Sniffing traffic would be my last resort.

I don't *think* that Xen has any way to know what interfaces are
configured on the domU end of a vif.

Cheers,
Andy

  parent reply	other threads:[~2014-06-11 16:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 16:32 Best way to get IP addresses from VMs without logging in to them? Russ Pavlicek
2014-06-11 16:38 ` Ian Campbell
2014-06-11 16:49   ` Andrew Cooper
2014-06-11 17:47     ` Russ Pavlicek
2014-06-11 18:02       ` Andrew Cooper
2014-06-11 18:14       ` Ian Campbell
2014-06-11 18:36         ` Russ Pavlicek
2014-06-11 18:44           ` Andrew Cooper
2014-06-11 22:10             ` Don Slutz
2014-06-12  7:26             ` Ian Campbell
2014-06-12  8:19               ` Tamas Lengyel
2014-06-11 16:40 ` Andy Smith [this message]
2014-06-11 16:49   ` Ian Campbell

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=20140611164012.GG21583@bitfolk.com \
    --to=andy@strugglers.net \
    --cc=xen-devel@lists.xen.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.