All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Flanagan <barryf-lists@flanagan.ie>
To: Goetz Bock <bock@blacknet.de>, xen-devel@lists.sourceforge.net
Subject: Re: Multiple network interfaces setup
Date: Mon, 31 Jan 2005 17:43:27 +0000	[thread overview]
Message-ID: <E1CvfaL-0007FJ-00@gran.netsource.ie> (raw)
In-Reply-To: 20050131155537.GA21629@shell.blacknet.de

Goetz Bock wrote:

> 
> On Mon, Jan 31 '05 at 15:28, Lukas Kubin wrote:
>> I found the scripts for network interfaces and bridges setup
>> (/etc/xen/scripts) in last versions of Xen really useful. But I need to
>> utilize more physical interfaces available on server. [ ... ]
>> Do I have to perform such setup "by hand" or the current scripts can do
>> it for me somehow?
> 
> I've just replaced the network script with a shell script that returns
> true/0 and done all the presetup by hand.
> 
> The vif-bridge script is called when a new domain's interface comes up.
> It looks like if you can pass a bridge name to the vif-bridge script,
> from the config file. Maybe that's enough for your needs.


I have 2 nics, and it works for me by a small change to /etc/init.d/xend:

I simply include an additional call to /etc/xen/scripts/network before xend
start and after xend stop to set up the second interface. 

Hope this helps.

#!/bin/bash
#
# xend          Script to start and stop the Xen control daemon.
#
# Author:       Keir Fraser <keir.fraser@cl.cam.ac.uk>
#
# chkconfig: 2345 98 01
# description: Starts and stops the Xen control daemon.

case "$1" in
  start)
        /etc/xen/scripts/network start bridge=xen-br1 netdev=eth1
antispoof=yes
        xend start
        ;;
  stop)
        xend stop
        /etc/xen/scripts/network stop bridge=xen-br1 netdev=eth1
antispoof=yes
        ;;
  status)
        xend status
        ;;
  restart|reload)
        xend restart
        ;;
  *)
        # do not advertise unreasonable commands that there is no reason
        # to use with this device
        echo $"Usage: $0 {start|stop|status|restart|reload}"
        exit 1
esac

exit $?




-- 

-Barry Flanagan


-------------------------------------------------------
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

      reply	other threads:[~2005-01-31 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 14:28 Multiple network interfaces setup Lukas Kubin
2005-01-31 15:55 ` Goetz Bock
2005-01-31 17:43   ` Barry Flanagan [this message]

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=E1CvfaL-0007FJ-00@gran.netsource.ie \
    --to=barryf-lists@flanagan.ie \
    --cc=bock@blacknet.de \
    --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.