Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge seems to not be usable from a guest domain. My motivation for this is that dom0 has 4 interfaces which could be on 4 networks. I didn''t want to assign IP addresses for dom0 on ALL of these networks. So am I missing something? Thanks. -- Steve Feehan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Donnerstag 09 November 2006 23:11 schrieb Steve Feehan:> Hi. I have another question, hopefully easier than my last: > > Do all physical interfaces in dom0 need to have an IP addresse in > order to be used > as a bridge by guest domains?In dom0 you have physical interfaces, the naming is pethX, and you have virtual ones, which are these named ethX. Neighter the physical ones nor the bridges shoud have ip configured. If you really nead ip traffic going from dom0 to your domUs configure ip on ethX in Dom0 und DomU. It is sufficient.> > I thought that the interface would have to merely be "up" but not > necessarily have an > IP address configured since bridging is done at layer 2. But alas, if > I don''t configure > an IP address on dom0 the bridge seems to not be usable from a guest domain.It shoult not happen. Did you have read the howto for multiple bridges: at the bottom, starting with: "With Xen 3.0 the best method for additional bridges is t..." http://wiki.xensource.com/xenwiki/XenNetworking You also can use something like: /etc/xen/scripts/network-bridge netdev=lan0 bridge=xenbr0 start vifnum=0 /etc/xen/scripts/network-bridge netdev=lan1 bridge=xenbr1 start vifnum=1> > My motivation for this is that dom0 has 4 interfaces which could be on > 4 networks. I > didn''t want to assign IP addresses for dom0 on ALL of these networks.You need 4 bridges, no need to configure any ip in dom0> > So am I missing something? Thanks. >cheers Jaroslaw _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/9/06, Christian <chris@computersalat.de> wrote:> Hi Steve, > > AFAIK you need only one nic on dom0 if you want to have networking for dom0. > If you configure one nic (eth0) and want this bridged (xenbr0) with a domU, > configure your domU.config nic as following > vif = [ ''mac=00:16:E3:00:00:00 , bridge=xenbr0'' ] > > Understand a bridge like a switch. > > hope that helps. > > ChrisMy question rephrased is: if I have 2 bridges in dom0 (say xenbr0 and xenbr1) does dom0 require a configured IP address on each bridge? My instincts told me no, but my experiment showed otherwise. Imagine the simplest case of one physical interface. You don''t want the interface in dom0 to have IP address, but you still want to provide networking to the guests via the bridge configured in dom0. Is this possible? I think it must be and either I''m doing something wrong or that I''m experiencing a limitation in the tools (either those provided by Xen or from SUSE) but I was hoping to get some confirmation before I dig any deeper. Thanks, -- Steve Feehan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/10/06, Jaroslaw Zdrzalek <jz@silpion.de> wrote:> Am Donnerstag 09 November 2006 23:11 schrieb Steve Feehan:> In dom0 you have physical interfaces, the naming is pethX, > and you have virtual ones, which are these named ethX. > Neighter the physical ones nor the bridges shoud have ip > configured. If you really nead ip traffic going from dom0 to > your domUs configure ip on ethX in Dom0 und DomU. > It is sufficient.Yes, I understand this.> > I thought that the interface would have to merely be "up" but not > > necessarily have an > > IP address configured since bridging is done at layer 2. But alas, if > > I don''t configure > > an IP address on dom0 the bridge seems to not be usable from a guest domain. > It shoult not happen. Did you have read the howto for multiple bridges: > at the bottom, starting with: > "With Xen 3.0 the best method for additional bridges is t..." > http://wiki.xensource.com/xenwiki/XenNetworkingYes, that is what I based my configuration on. Here is my custom network script: #!/bin/sh /etc/xen/scripts/network-bridge $@ bridge=xenbr0 netdev=eth0 vifnum=0 /etc/xen/scripts/network-bridge $@ bridge=xenbr1 netdev=eth1 vifnum=1 /etc/xen/scripts/network-bridge $@ bridge=xenbr3 netdev=eth3 vifnum=3 And this works fine as long as the virtual interfaces (eth0, etc.) have IP addresses configured. Actually, let me state this more completely: My custom network-script works if the phsical interfaces have IP addresses BEFORE xen starts. And when I say it works, I mean that: * bridges are created * the virtual interfaces exist in the guests * AND they are usable. It''s the last point that is the important part. When I don''t configure IP addresses on the physical interfaces in dom0 BEFORE starting Xen the bridges are still created and the virtual interfaces exist in the guests, but they''re not usable. And by not usable I mean if I configure them with an IP address and try to ping from the guest I get "network unreachable" errors. At least, that is what I recall. This is all getting a bit fuzzy in my memory after the long weekend. I need to go back and reproduce the problem again.> > My motivation for this is that dom0 has 4 interfaces which could be on > > 4 networks. I > > didn''t want to assign IP addresses for dom0 on ALL of these networks. > You need 4 bridges, no need to configure any ip in dom0Yes, this is what I think too. I will try and reproduce the problem and follow up with the result. Thanks, -- Steve Feehan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Steve, I have one dual port network card. the first port eth0 is connected to the company''s intranet and the second port eth1 is connected to the switch on my desk. The first port is configured as dhcp and the second port is configured as static IP address (192.168.2.2). Both port are set active on boot. Question 1: Xen (3.0.3) only created peth0 for the first port while I have to create peth1 manually. Question 2: I created a guest domain with two interfaces (the first interface eth0 is dhcp and the second interface eth1 has fixed ipaddress 192.168.2.3). The eth0 in the domain get the dhcp address without problem. I can ping the dhcp address of eth0 in domain0 from eth0 in the guest domain. However, I can not ping the eth1 in domain0 from guest domain unless I configure the bridge xenbr1 with the IP address 192.168.2.6 (xenbr1 is created when peth1 is created) Could you give me some explanation about this? Thanks, Liang ----- Original Message ----- From: "Steve Feehan" <sfeehan@gmail.com> To: <xen-users@lists.xensource.com> Sent: Monday, November 13, 2006 8:17 AM Subject: Re: [Xen-users] bridge interfaces in dom0> On 11/10/06, Jaroslaw Zdrzalek <jz@silpion.de> wrote: >> Am Donnerstag 09 November 2006 23:11 schrieb Steve Feehan: > >> In dom0 you have physical interfaces, the naming is pethX, >> and you have virtual ones, which are these named ethX. >> Neighter the physical ones nor the bridges shoud have ip >> configured. If you really nead ip traffic going from dom0 to >> your domUs configure ip on ethX in Dom0 und DomU. >> It is sufficient. > > Yes, I understand this. > >> > I thought that the interface would have to merely be "up" but not >> > necessarily have an >> > IP address configured since bridging is done at layer 2. But alas, if >> > I don''t configure >> > an IP address on dom0 the bridge seems to not be usable from a guest >> > domain. >> It shoult not happen. Did you have read the howto for multiple bridges: >> at the bottom, starting with: >> "With Xen 3.0 the best method for additional bridges is t..." >> http://wiki.xensource.com/xenwiki/XenNetworking > > Yes, that is what I based my configuration on. Here is my custom network > script: > > #!/bin/sh > /etc/xen/scripts/network-bridge $@ bridge=xenbr0 netdev=eth0 vifnum=0 > /etc/xen/scripts/network-bridge $@ bridge=xenbr1 netdev=eth1 vifnum=1 > /etc/xen/scripts/network-bridge $@ bridge=xenbr3 netdev=eth3 vifnum=3 > > And this works fine as long as the virtual interfaces (eth0, etc.) have IP > addresses configured. > > Actually, let me state this more completely: > > My custom network-script works if the phsical interfaces have IP addresses > BEFORE xen starts. > > And when I say it works, I mean that: > > * bridges are created > * the virtual interfaces exist in the guests > * AND they are usable. > > It''s the last point that is the important part. When I don''t configure > IP addresses > on the physical interfaces in dom0 BEFORE starting Xen the bridges are > still > created and the virtual interfaces exist in the guests, but they''re > not usable. And > by not usable I mean if I configure them with an IP address and try to > ping from > the guest I get "network unreachable" errors. At least, that is what I > recall. This > is all getting a bit fuzzy in my memory after the long weekend. I need > to go back > and reproduce the problem again. > >> > My motivation for this is that dom0 has 4 interfaces which could be on >> > 4 networks. I >> > didn''t want to assign IP addresses for dom0 on ALL of these networks. >> You need 4 bridges, no need to configure any ip in dom0 > > Yes, this is what I think too. I will try and reproduce the problem > and follow up with > the result. > > Thanks, > > -- > Steve Feehan > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Montag 13 November 2006 16:17 schrieb Steve Feehan:> On 11/10/06, Jaroslaw Zdrzalek <jz@silpion.de> wrote: > > Am Donnerstag 09 November 2006 23:11 schrieb Steve Feehan: > > > In dom0 you have physical interfaces, the naming is pethX, > > and you have virtual ones, which are these named ethX. > > Neighter the physical ones nor the bridges shoud have ip > > configured. If you really nead ip traffic going from dom0 to > > your domUs configure ip on ethX in Dom0 und DomU. > > It is sufficient. > > Yes, I understand this. > > > > I thought that the interface would have to merely be "up" but not > > > necessarily have an > > > IP address configured since bridging is done at layer 2. But alas, if > > > I don''t configure > > > an IP address on dom0 the bridge seems to not be usable from a guest domain. > > It shoult not happen. Did you have read the howto for multiple bridges: > > at the bottom, starting with: > > "With Xen 3.0 the best method for additional bridges is t..." > > http://wiki.xensource.com/xenwiki/XenNetworking > > Yes, that is what I based my configuration on. Here is my custom network script: > > #!/bin/sh > /etc/xen/scripts/network-bridge $@ bridge=xenbr0 netdev=eth0 vifnum=0 > /etc/xen/scripts/network-bridge $@ bridge=xenbr1 netdev=eth1 vifnum=1 > /etc/xen/scripts/network-bridge $@ bridge=xenbr3 netdev=eth3 vifnum=3 > > And this works fine as long as the virtual interfaces (eth0, etc.) have IP > addresses configured. > > Actually, let me state this more completely: > > My custom network-script works if the phsical interfaces have IP addresses > BEFORE xen starts. > > And when I say it works, I mean that: > > * bridges are created > * the virtual interfaces exist in the guests > * AND they are usable. > > It''s the last point that is the important part. When I don''t configure > IP addresses > on the physical interfaces in dom0 BEFORE starting Xen the bridges are still > created and the virtual interfaces exist in the guests, but they''re > not usable. And > by not usable I mean if I configure them with an IP address and try to ping from > the guest I get "network unreachable" errors. At least, that is what I > recall. This > is all getting a bit fuzzy in my memory after the long weekend. I need > to go back > and reproduce the problem again. > > > > My motivation for this is that dom0 has 4 interfaces which could be on > > > 4 networks. I > > > didn''t want to assign IP addresses for dom0 on ALL of these networks. > > You need 4 bridges, no need to configure any ip in dom0 > > Yes, this is what I think too. I will try and reproduce the problem > and follow up with > the result.I just tryed out your scenario. I have two physical interfaces and also two bridges. I use debian sid, it stores the network config in /etc/network/interfaces. I renamed that file and also /etc/init.d/xend. Then I restartet and none of the interfaces in dom0 was configured. I started xend and it came up as usual (all cables was attached). I started an hvm guest and it have had networking up & running. sorry, but at least on my debian it is working as expected ;-) I attach a log from the session. cheers Jaroslaw> > Thanks, >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Nov 13, 2006, Steve Feehan wrote:> My question rephrased is: if I have 2 bridges in dom0 (say xenbr0 and > xenbr1) > does dom0 require a configured IP address on each bridge?> My instincts told me no, but my experiment showed otherwise.> Imagine the simplest case of one physical interface. You don''t want > the interface in dom0 to have IP address, but you still want to > provide networking to the guests via the bridge configured in dom0. Is > this possible?Yup. I think the bridging stuff is fine but the scripts aren''t. In any case, to get around that I just have ''bogus'' IP addresses on my "bridge-only" interfaces/vlans. domU doesn''t care whether there''s an IP or not on it.> I think it must be and either I''m doing something wrong or that I''m > experiencing a limitation in the tools (either those provided by Xen > or from SUSE) but I was hoping to get some confirmation before I dig > any deeper.I think you''ll find the networking scripts in Xen make a lot of assumptions about the underlying interface behaviour. This was why things like vlan interfaces didn''t work (and I haven''t verified it with newer script versions - but, in essence, it''d grab the IP, down the interface, then try to put it into the bridge group - but downing a vlan subinterface -> interface deletion; so there''s no interface to bind into the bridge group. Grr. :) Adrian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- bridge with IP address, "received packet with own address as source address"
- Setting up virtual ''ethX'' devices in Xen 3.4
- installing DomU with two network bridges via virt-install
- No cdrom in windows 2003 HVM guest
- XEN multiple bridge problem - VM won' start!