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. I wish to route some of my domains through one NIC and some through the other one because of different VLANs they should appear in. Do I have to perform such setup "by hand" or the current scripts can do it for me somehow? Looking at the code it seems that only one default interface can be setup this way. Thank you. lukas
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. -- /"\ Goetz Bock at blacknet dot de -- secure mobile Linux everNETting \ / (c) 2004 Creative Commons, Attribution-ShareAlike 2.0 de X [ 1. Use descriptive subjects - 2. Edit a reply for brevity - ] / \ [ 3. Reply to the list - 4. Read the archive *before* you post ] ------------------------------------------------------- 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel