All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Dinn <robbie@microbus.com>
To: Nicholas Lee <emptysands@gmail.com>
Cc: Xen development list <xen-devel@lists.xensource.com>
Subject: Re: vif0.0/veth0 or eth0
Date: Mon, 20 Feb 2006 09:51:41 +0000	[thread overview]
Message-ID: <43F9912D.40300@microbus.com> (raw)
In-Reply-To: <2b6116b30602191821n39c8b2f6y@mail.gmail.com>

Nicholas Lee wrote:
> When does vif0.0 get created?
don't know
> 
> Is there some shell magic?
Are you using bridging?
If so, I think I know this!
look for shell function 'op_start' in file /etc/xen/scripts/network-bridge

> 
> I'm trying to figure out how to do a similar peth1/veth1 split for eth1.

Maybe it is as simple as replacing /etc/xen/scripts/network-bridge
with a wrapper that invokes the original /etc/xen/scripts/network-bridge
twice, each time with different values for environment variables
vifnum, bridge, and netdev. Those environment variables are documented
at the top of /etc/xen/scripts/network-bridge.

quoting from /etc/xen/xend-config.sxp:
> # It is possible to use the network-bridge script in more complicated
> # scenarios, such as having two outgoing interfaces, with two bridges, and
> # two fake interfaces per guest domain.  To do things like this, write
> # yourself a wrapper script, and call network-bridge from it, as appropriate.
> #

HTH

Robbie Dinn

  reply	other threads:[~2006-02-20  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20  2:21 vif0.0/veth0 or eth0 Nicholas Lee
2006-02-20  9:51 ` Robbie Dinn [this message]
2006-02-20 15:19   ` Ewan Mellor
2006-02-20 20:13     ` Nicholas Lee

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=43F9912D.40300@microbus.com \
    --to=robbie@microbus.com \
    --cc=emptysands@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.