Re: Xen in Etch, basic setup
On Thu, Apr 10, 2008 at 09:58:29AM -0700, Steve Lamb wrote: On Tue, April 8, 2008 3:19 pm, Andrew Sackville-West wrote: well, that's just plain frustrating. It's got me worried because my xen setup is working great in etch... might have to leave it there for a while. Well, the main problem is that testing installs 2.6.24-xen and does not have any of the 2.6.18-xen strain of kernels. The problem is 2.6.24 cannot boot as Dom0. What do you mean by cannot? Do you mean it will not by design or cannot due to bugs? curious. as to the rest, I'm out of ideas without sitting down at the machine... A signature.asc Description: Digital signature
Re: Xen in Etch, basic setup
Andrew Sackville-West wrote: What do you mean by cannot? Do you mean it will not by design or cannot due to bugs? curious. Cannot as in every kernel has to be reported to run under Xen. Supposedly the last kernel that can run both Dom0 and DomU is 2.6.18 but Ubuntu apparently has it up to 2.6.20 so my information might be a tad out of date. However when I first installed it on testing and it pulled in Xen from testing and tried to boot Dom0 it failed completely, just hung there. About 10 minutes of Googling and I found that it was a known issue in Debian that .24 can run DomU but not Dom0. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466492 After reading that report I pulled in .18 and it booted into Dom0 just fine. -- Steve C. Lamb | But who decides what they dream? PGP Key: 1FC01004 | And dream I do... ---+- signature.asc Description: OpenPGP digital signature
Re: Xen in Etch, basic setup
Just to clarify: if I need 2.6.24 to support my WiFi card, I therefore can not use Xen until some later kernel is released that can support both? I should therefore try one of QEMU/VirtualBox/VMWare/Something Else Entirely? -- Carl Fink [EMAIL PROTECTED] Read my blog at blog.nitpicking.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Tue, April 8, 2008 3:19 pm, Andrew Sackville-West wrote: well, that's just plain frustrating. It's got me worried because my xen setup is working great in etch... might have to leave it there for a while. Well, the main problem is that testing installs 2.6.24-xen and does not have any of the 2.6.18-xen strain of kernels. The problem is 2.6.24 cannot boot as Dom0. So to get Testing to work one has to know to look in the stable tree, retrieve 2.6.18-xen and use it as Dom0. In aptitude, at least, it would not let me even see 2.6.18-xen unless I told it to look only at stable. However, the rest of my problems I cannot say with certainty have anything to do with the testing version. I mean once I knew to pull the kernel from stable to get Dom0 working and did only that on my laptop it worked. However^2, last night I purged all the Xen packages from my router/server box. I then got the list of Xen packages installed on the laptop and installed only those packages on my router/server box. Booting into Dom0 with the configuration I had and only one ethernet device setup resulted in my IP showing up on xenbr1. *sigh* -- Steve Lamb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Sun, April 6, 2008 11:09 am, Andrew Sackville-West wrote: auto eth1 iface eth1 inet static address 192.168.1.21 netmask 255.255.255.0 gateway 192.168.1.1 auto eth1:1 iface eth1:1 inet static address 192.168.1.1 netmask 255.255.255.0 why are you running multiple interfaces on eth1 like this? Is this something you need? Yes. But actually I pasted the interfaces file from when Dom0 was running as the gateway. Normally the eth1:1 and eth0 auto lines are commented out. To explain eth1:0 and eth1:1, there was a time where I was bouncing between this machine being the router and a wireless router being the router. Stupid building practices in the house I am renting. Every time I swapped between those two IPs I'd have to reconfigure all my machines to look for the Squid proxy in a new location. Normally after my wife got frustrated that the proxy disappeared. So in the name of marital bliss I decided to just leave the machine on .21 permanently and alias .1 to it whenever it is acting as the router. xenbr interface automatically. and breakdown that eth1 setup to just a basic one (simplify, right?) and see what happens. I have done that. I get anything from the bridge getting the IP to nothing having the IP to no bridge/vif/veths at all. At this point I'm going to uninstall all the packages and start over. However since I know how to get it working thanks to my test on my laptop I'll just duplicate that setup. Really though, testing is a tad flubbed. -- Steve Lamb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
Apparently I had some mail in the queue on my laptop... On Tue, Apr 08, 2008 at 09:44:15AM -0700, Steve Lamb wrote: On Sun, April 6, 2008 11:09 am, Andrew Sackville-West wrote: auto eth1 iface eth1 inet static address 192.168.1.21 netmask 255.255.255.0 gateway 192.168.1.1 auto eth1:1 iface eth1:1 inet static address 192.168.1.1 netmask 255.255.255.0 why are you running multiple interfaces on eth1 like this? Is this something you need? Yes. But actually I pasted the interfaces file from when Dom0 was running as the gateway. Normally the eth1:1 and eth0 auto lines are commented out. To explain eth1:0 and eth1:1, there was a time where I was bouncing between this machine being the router and a wireless router being the router. Stupid building practices in the house I am renting. Every time I swapped between those two IPs I'd have to reconfigure all my machines to look for the Squid proxy in a new location. Normally after my wife got frustrated that the proxy disappeared. So in the name of marital bliss I decided to just leave the machine on .21 permanently and alias .1 to it whenever it is acting as the router. xenbr interface automatically. and breakdown that eth1 setup to just a basic one (simplify, right?) and see what happens. I have done that. I get anything from the bridge getting the IP to nothing having the IP to no bridge/vif/veths at all. At this point I'm going to uninstall all the packages and start over. However since I know how to get it working thanks to my test on my laptop I'll just duplicate that setup. Really though, testing is a tad flubbed. well, that's just plain frustrating. It's got me worried because my xen setup is working great in etch... might have to leave it there for a while. A signature.asc Description: Digital signature
Re: Xen in Etch, basic setup
On Sun, Apr 06, 2008 at 06:17:53AM -0700, Steve Lamb wrote: Andrew Sackville-West wrote: so far as I know, having shorewall turned off in /etc/defaults/shorewall completely prevents it from running. So you would be left with bog standard iptables setup -- wide open. For the record this is indeed the case. iptables -L showed nothing when I checked. okay. what does your Dom0 /etc/network/interfaces look like? [EMAIL PROTECTED]:/etc/network} cat interfaces auto lo iface lo inet loopback auto eth1 iface eth1 inet static address 192.168.1.21 netmask 255.255.255.0 gateway 192.168.1.1 auto eth1:1 iface eth1:1 inet static address 192.168.1.1 netmask 255.255.255.0 why are you running multiple interfaces on eth1 like this? Is this something you need? I suspect it is part of the problem. #auto eth0 #iface eth0 inet dhcp auto eth0 iface eth0 inet static address 69.68.200.5 netmask 255.255.255.128 gateway 69.68.200.1 [EMAIL PROTECTED]:/etc/network} The really funky thing is the last time I set the machine for bridge networking, just a few minutes ago, xenbr1 got eth1's IP and there was a xenbr1:2 which got eth1:1's IP. I think you're trying to set up a firewall on this domU right? in that case, leave eth0 unconfigured in the dom0 and configure it in domU (you may have to do some funky stuff to get that to work, I'll look at my config and see what I can remember.) and then let xen setup the xenbr interface automatically. and breakdown that eth1 setup to just a basic one (simplify, right?) and see what happens. A signature.asc Description: Digital signature
Re: Xen in Etch, basic setup
Andrew Sackville-West wrote: so far as I know, having shorewall turned off in /etc/defaults/shorewall completely prevents it from running. So you would be left with bog standard iptables setup -- wide open. For the record this is indeed the case. iptables -L showed nothing when I checked. what does your Dom0 /etc/network/interfaces look like? [EMAIL PROTECTED]:/etc/network} cat interfaces auto lo iface lo inet loopback auto eth1 iface eth1 inet static address 192.168.1.21 netmask 255.255.255.0 gateway 192.168.1.1 auto eth1:1 iface eth1:1 inet static address 192.168.1.1 netmask 255.255.255.0 #auto eth0 #iface eth0 inet dhcp auto eth0 iface eth0 inet static address 69.68.200.5 netmask 255.255.255.128 gateway 69.68.200.1 [EMAIL PROTECTED]:/etc/network} The really funky thing is the last time I set the machine for bridge networking, just a few minutes ago, xenbr1 got eth1's IP and there was a xenbr1:2 which got eth1:1's IP. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
Steve Lamb wrote: The really funky thing is the last time I set the machine for bridge networking, just a few minutes ago, xenbr1 got eth1's IP and there was a xenbr1:2 which got eth1:1's IP. I figured with funky results like the one above I should get a tar-ball of the same version form xen.org and toss it over the package just to make sure it isn't something funky in the package. The good news is that the bridges no longer have the IPs from the ethernet devices. The bad news is that there are no bridges, no veth devices, no vif devices, no peth, nothing. No change at all. I made sure the configuration file specified bridging, which it does. At this point I'm gonna call John Lithgow as he is the only person I know who has any experience with gremlins. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
Jeff D wrote: what options do you have in your xend-config.sxp? Do you have bridge-utils installed? Right now: [EMAIL PROTECTED]:/etc/xen} grep -v # xend-config.sxp_wip | sort | uniq (dom0-cpus 0) (dom0-min-mem 196) (logfile /var/log/xen/xend.log) (loglevel DEBUG) (network-script 'network-bridge netdev=eth1 bridge=xenbr1') (vif-script vif-bridge) I'm just trying to get networking to work at all at this point. Forget two bridges into DomU land, I just wanted Dom0 to talk to DomU at this point and it fails utterly. This is with 3.0.3, btw. Also, convirt segfaults when I tried using a GUI configuration. :( (network-script network-dummy) Is the only difference, really. From what I've read it isn't required in Xen 3.0. and in my domU configs i have something like this: vif = [ 'ip=10.1.2.94' ] vif = [ 'mac=00:16:3E:BA:17:79,bridge=xenbr1'] Does the IP make a difference? Should the bridges end up with an IP? For some reason when network-bridge is done xenbr1 has the IP assigned to eth1 on Dom0 prior to xend's start. and I also have that same ip in a static config for networking in the domU. Same here. In DomU I've got 192.168.1.2 as a test IP. When I backed out all my changes back to a working setup for gaming, email, researching the web I had the following which was failing: eth0 on Dom0 was set to 192.168.1.21 prior to xend starting up. After it ended up on xenbr1. eth0 inside DomU was set to 192.168.1.2. A laptop on the network with an ip of 192.168.1.7. Dom0 was unable to ping .2 or .7 DomU was unable to ping .21 or .7 Laptop was ignored since I was working on a console on the other side of the room. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Fri, Apr 04, 2008 at 01:09:09AM -0800, Steve Lamb wrote: Jeff D wrote: what options do you have in your xend-config.sxp? Do you have bridge-utils installed? Right now: [EMAIL PROTECTED]:/etc/xen} grep -v # xend-config.sxp_wip | sort | uniq (dom0-cpus 0) (dom0-min-mem 196) (logfile /var/log/xen/xend.log) (loglevel DEBUG) (network-script 'network-bridge netdev=eth1 bridge=xenbr1') (vif-script vif-bridge) I'm just trying to get networking to work at all at this point. Forget two bridges into DomU land, I just wanted Dom0 to talk to DomU at this point and it fails utterly. This is with 3.0.3, btw. Also, convirt segfaults when I tried using a GUI configuration. :( (network-script network-dummy) Is the only difference, really. From what I've read it isn't required in Xen 3.0. and in my domU configs i have something like this: vif = [ 'ip=10.1.2.94' ] vif = [ 'mac=00:16:3E:BA:17:79,bridge=xenbr1'] Does the IP make a difference? I think it does make some difference in that I don't specify an IP, my vif= lookslike this: dhcp = 'dhcp' vif = [ 'mac=aa:00:00:00:00:22, bridge=xenbrDMZ' ] but I use dhcp. the other likely important bit is the made-up MAC address for the virtual interface. That fake mac address becomes the HwAddr in my DomU's ifconfig output. It looks to me like you are passing a real mac address which would cause all kinds of problems, I suspect. And, in retrospect, IP probably *doesn't* matter because you can set that in the domU when it brings up it's interface. I strongly recommend you try this with a fake mac address of the type I'm using and see what happens. Should the bridges end up with an IP? For some reason when network-bridge is done xenbr1 has the IP assigned to eth1 on Dom0 prior to xend's start. the bridge will *not* end up with an IP. It will have a funcky hwaddr like FE:FF:FF:FF:FF:FF and that's it. The bridge just connects different ends of virtual interfaces and is not an interface itself, per se.*** and I also have that same ip in a static config for networking in the domU. Same here. In DomU I've got 192.168.1.2 as a test IP. When I backed out all my changes back to a working setup for gaming, email, researching the web I had the following which was failing: eth0 on Dom0 was set to 192.168.1.21 prior to xend starting up. After it ended up on xenbr1. you mean the IP address ended up on xenbr1? That's because you specified an actual piece of hardware in that vif= line, I think. My understanding is that you want something like this: eth0/Dom0 ( a real interface) | | 192.168.1.21 real mac address | Dom0--xenbr1potentially other DomU's on same subnet | | 192.168.1.2 fake mac address | DomU I have a working, 3 DomU xen setup with one as firewall, one as DMZ mail server, one as DMZ web server, Dom0 as local fileserver. This includes using pciback to hide my internet-side interface from Dom0. I would be happy to share my complete config if you'd like. A *** highly speculative on my part. signature.asc Description: Digital signature
Re: Xen in Etch, basic setup
On Fri, April 4, 2008 7:51 am, Andrew Sackville-West wrote: On Fri, Apr 04, 2008 at 01:09:09AM -0800, Steve Lamb wrote: I think it does make some difference in that I don't specify an IP, my vif= lookslike this: dhcp = 'dhcp' vif = [ 'mac=aa:00:00:00:00:22, bridge=xenbrDMZ' ] but I use dhcp. That'll be hard since the DomU is the one that's going to be running the DHCP server. But later on in the message you agree that this is probably not it so we'll leave it at that. the other likely important bit is the made-up MAC address for the virtual interface. That fake mac address becomes the HwAddr in my DomU's ifconfig output. It looks to me like you are passing a real mac address which would cause all kinds of problems, I suspect. Nope. From http://wiki.xensource.com/xenwiki/XenNetworking: It's recommended to use a MAC address inside the range 00:16:3e:xx:xx:xx. This address range is reserved for use by Xen. The MAC address I'm passing to DomU, 00:16:3E:BA:17:79, was generated by xen-tools when the image was created and is within the range suggested by Xen. the bridge will *not* end up with an IP. It will have a funcky hwaddr like FE:FF:FF:FF:FF:FF and that's it. The bridge just connects different ends of virtual interfaces and is not an interface itself, per se.*** I'll double check that. I think the bridge ending up with the IP was the result of me really munging something somewhere. I tried it again later in the evening and did not get the same results. I have a working, 3 DomU xen setup with one as firewall, one as DMZ mail server, one as DMZ web server, Dom0 as local fileserver. This includes using pciback to hide my internet-side interface from Dom0. I would be happy to share my complete config if you'd like. I appreciate the offer but I'm swimming in complex example configurations. The lack of examples isn't a problem. Something in the process I am missing is. I have to be missing something since my configuration, especially this single ethernet card test, should work. I can't find any glaringly obvious difference from the many examples I've seen and my configurations. Thank you for discussing it with me, however, since sometimes just having a sounding board will get the ol' synapses firing. :) -- Steve Lamb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Fri, Apr 04, 2008 at 09:17:46AM -0700, Steve Lamb wrote: On Fri, April 4, 2008 7:51 am, Andrew Sackville-West wrote: On Fri, Apr 04, 2008 at 01:09:09AM -0800, Steve Lamb wrote: I think it does make some difference in that I don't specify an IP, my vif= lookslike this: dhcp = 'dhcp' vif = [ 'mac=aa:00:00:00:00:22, bridge=xenbrDMZ' ] but I use dhcp. That'll be hard since the DomU is the one that's going to be running the DHCP server. But later on in the message you agree that this is probably not it so we'll leave it at that. yeah, I editted that several times and clearly munged it a bit. the other likely important bit is the made-up MAC address for the virtual interface. That fake mac address becomes the HwAddr in my DomU's ifconfig output. It looks to me like you are passing a real mac address which would cause all kinds of problems, I suspect. Nope. From http://wiki.xensource.com/xenwiki/XenNetworking: It's recommended to use a MAC address inside the range 00:16:3e:xx:xx:xx. This address range is reserved for use by Xen. heh. whoops. The MAC address I'm passing to DomU, 00:16:3E:BA:17:79, was generated by xen-tools when the image was created and is within the range suggested by Xen. the bridge will *not* end up with an IP. It will have a funcky hwaddr like FE:FF:FF:FF:FF:FF and that's it. The bridge just connects different ends of virtual interfaces and is not an interface itself, per se.*** I'll double check that. I think the bridge ending up with the IP was the result of me really munging something somewhere. I tried it again later in the evening and did not get the same results. I have a working, 3 DomU xen setup with one as firewall, one as DMZ mail server, one as DMZ web server, Dom0 as local fileserver. This includes using pciback to hide my internet-side interface from Dom0. I would be happy to share my complete config if you'd like. I appreciate the offer but I'm swimming in complex example configurations. The lack of examples isn't a problem. I so understand! Something in the process I am missing is. I have to be missing something since my configuration, especially this single ethernet card test, should work. I can't find any glaringly obvious difference from the many examples I've seen and my configurations. Thank you for discussing it with me, however, since sometimes just having a sounding board will get the ol' synapses firing. :) what does your Dom0 /etc/network/interfaces look like? also, what about the output of route on various Doms? A signature.asc Description: Digital signature
Re: Xen in Etch, basic setup
On Fri, April 4, 2008 9:54 am, Andrew Sackville-West wrote: On Fri, Apr 04, 2008 at 09:17:46AM -0700, Steve Lamb wrote: Something in the process I am missing is. I have to be missing something since my configuration, especially this single ethernet card test, should work. I can't find any glaringly obvious difference from the many examples I've seen and my configurations. Thank you for discussing it with me, however, since sometimes just having a sounding board will get the ol' synapses firing. :) I think there is something here. Do you, or anyone, know if telling Shorewall not to load in /etc/defaults/shorewall mean everything is wide open or that it loads some set which only allows those interfaces with routestopped to talk? If it is the latter that might be the problem since only eth0 and eth1 are in my shorewall configuration and neither of those are actively in use under Dom0. what does your Dom0 /etc/network/interfaces look like? also, what about the output of route on various Doms? I'll have to get back to you on these two in a few hours when I have some time. -- Steve Lamb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Fri, Apr 04, 2008 at 04:51:10PM -0700, Steve Lamb wrote: On Fri, April 4, 2008 9:54 am, Andrew Sackville-West wrote: On Fri, Apr 04, 2008 at 09:17:46AM -0700, Steve Lamb wrote: Something in the process I am missing is. I have to be missing something since my configuration, especially this single ethernet card test, should work. I can't find any glaringly obvious difference from the many examples I've seen and my configurations. Thank you for discussing it with me, however, since sometimes just having a sounding board will get the ol' synapses firing. :) I think there is something here. Do you, or anyone, know if telling Shorewall not to load in /etc/defaults/shorewall mean everything is wide open or that it loads some set which only allows those interfaces with routestopped to talk? If it is the latter that might be the problem Shorewall's init.d script won't do anything if /etc/defaults/shorewall isn't configured (or maybe if the startup variable is spoofed?), according to a look at /etc/init.d/shorewall on sid. It could probably be run by other means, so I don't know if that's definitive. Running iptables --list would show what's actually configured, regardless of how shorewall is or isn't configured. Ken since only eth0 and eth1 are in my shorewall configuration and neither of those are actively in use under Dom0. what does your Dom0 /etc/network/interfaces look like? also, what about the output of route on various Doms? I'll have to get back to you on these two in a few hours when I have some time. -- Steve Lamb -- Ken Irving, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Fri, Apr 04, 2008 at 04:51:10PM -0700, Steve Lamb wrote: On Fri, April 4, 2008 9:54 am, Andrew Sackville-West wrote: On Fri, Apr 04, 2008 at 09:17:46AM -0700, Steve Lamb wrote: Something in the process I am missing is. I have to be missing something since my configuration, especially this single ethernet card test, should work. I can't find any glaringly obvious difference from the many examples I've seen and my configurations. Thank you for discussing it with me, however, since sometimes just having a sounding board will get the ol' synapses firing. :) I think there is something here. Do you, or anyone, know if telling Shorewall not to load in /etc/defaults/shorewall mean everything is wide open or that it loads some set which only allows those interfaces with routestopped to talk? If it is the latter that might be the problem since only eth0 and eth1 are in my shorewall configuration and neither of those are actively in use under Dom0. so far as I know, having shorewall turned off in /etc/defaults/shorewall completely prevents it from running. So you would be left with bog standard iptables setup -- wide open. A signature.asc Description: Digital signature
Xen in Etch, basic setup
Hello, Does anyone know of a web page that describes a basic setup of Xen in Etch? I've seen several at howtoforge and each of them, while fairly simple, do not match my experience at all. I follow the directions exactly and after a time what those directions say should appear and what actually does appear diverge wildly. On the other end of the spectrum are the pages that the author of Shorewall has put up detailing his experiences with Xen and Shorewall. A fascinating read and one that I'll have to dig into later. But it is no howto nor was it written with that intent. Right now I've got Etch booting into Dom0 just fine. Oddly enough my routing is working fine though I'm not quite sure why. I have one DomU which boots fine but is unable to use the network. When I attempt to bring up a bridge the networking to the outside world on Dom0 fails but local networking still works, DomU can see a network card but cannot connect to Dom0 or the rest of the local network. Furthermore no bridge device shows up in ifconfig. This is where my experience and those of the howtoforge authors seriously diverges. What I would be content with, for now, is having both Dom0/DomU being able to speak to the rest of the local network. With that I could at least work away from the console and flip configurations to where I could pull things off the internet with Dom0 acting as my router and then switch it to where DomU communicates so I can pull things across and continue my work. Ideally I want to have the DomU machine act as the router/FW for my network, hence the interest in the Shorewall/Xen documents. -- Steve Lamb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xen in Etch, basic setup
On Thu, 3 Apr 2008, Steve Lamb wrote: Hello, Does anyone know of a web page that describes a basic setup of Xen in Etch? I've seen several at howtoforge and each of them, while fairly simple, do not match my experience at all. I follow the directions exactly and after a time what those directions say should appear and what actually does appear diverge wildly. On the other end of the spectrum are the pages that the author of Shorewall has put up detailing his experiences with Xen and Shorewall. A fascinating read and one that I'll have to dig into later. But it is no howto nor was it written with that intent. Right now I've got Etch booting into Dom0 just fine. Oddly enough my routing is working fine though I'm not quite sure why. I have one DomU which boots fine but is unable to use the network. When I attempt to bring up a bridge the networking to the outside world on Dom0 fails but local networking still works, DomU can see a network card but cannot connect to Dom0 or the rest of the local network. Furthermore no bridge device shows up in ifconfig. This is where my experience and those of the howtoforge authors seriously diverges. What I would be content with, for now, is having both Dom0/DomU being able to speak to the rest of the local network. With that I could at least work away from the console and flip configurations to where I could pull things off the internet with Dom0 acting as my router and then switch it to where DomU communicates so I can pull things across and continue my work. Ideally I want to have the DomU machine act as the router/FW for my network, hence the interest in the Shorewall/Xen documents. what options do you have in your xend-config.sxp? Do you have bridge-utils installed? some network options I use in my xend-config.sxp are: (network-script network-bridge) (network-script network-dummy) (vif-script vif-bridge) and in my domU configs i have something like this: vif = [ 'ip=10.1.2.94' ] and I also have that same ip in a static config for networking in the domU. hth, Jeff -- 8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
