Hey guys, Usually all my guests go out through various bridges connected to eth0, but I came across a scenario where I need to connect one guest to a special backend network. The network is connected to an access port on a switch via eth2 on the xen server. If I set an IP on eth2 in the correct network it works just fine. How can I share this connection up to a domU? I cant tell the switchport to become a trunk and bridge out internally like I usually do. Any help is greatly appreciated!! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hey guys, > > Usually all my guests go out through various bridges connected to eth0, but I > came across a scenario where I need to connect one guest to a special > backend network. The network is connected to an access port on a switch via > eth2 on the xen server. If I set an IP on eth2 in the correct network it works just > fine. How can I share this connection up to a domU? I cant tell the switchport > to become a trunk and bridge out internally like I usually do. Any help is greatly > appreciated!!What you may want to try is bridging the connection on eth2 to something like xenbr2 and in the config file have a line that is: vif=[''bridge=xenbr2''] Just make sure that before you bridge the connection that eth2 is given the IP that will make it work. To create the bridge (after getting eth2 connected with the proper IP): brctl addbr xenbr2 brctl addif xenbr2 eth2 ifconfig xenbr2 up Then you put the line in the config file as stated above, and bring up the VM. It should be able to connect to resources on the "special backend network" once it either gets an IP from a DHCP source or if you manually configure it. If you need any help, let me know. Is it for a Windows or Linux VM? Tait _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Hey guys, > > > > Usually all my guests go out through various bridges connected to eth0, but I > > came across a scenario where I need to connect one guest to a special > > backend network. The network is connected to an access port on a switch via > > eth2 on the xen server. If I set an IP on eth2 in the correct network it works > just > > fine. How can I share this connection up to a domU? I cant tell the switchport > > to become a trunk and bridge out internally like I usually do. Any help is > greatly > > appreciated!! > > What you may want to try is bridging the connection on eth2 to something like > xenbr2 and in the config file have a line that is: > > vif=[''bridge=xenbr2'']EDIT: If you have a line in the domU configuration file that already has a vif stated, which will probably be the case (eg. vif=[''bridge=xenbr0'']) you can just add the following configuration for two network connections by doing something like: vif=[''bridge=xenbr0'',''bridge=xenbr2''] I have a similar setup for an iSCSI storage network where one of the NICs on the dom0 is connected to the iSCSI network and allows connectivity to the domU through a special network bridge "iscsibr0" which I add to the config file as I showed above. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you for getting back to me so quickly. I IP-ed the interface appropriately and was able to ping members of the network. I created the bridge and added eth2 to it, at that point I could no longer ping members of that network. I continued to configure the guest, and rebooted it, it came up with the new network interface containing IP identical to the one configured in the dom0. It was not able to ping the network either. I checked all manner of firewalls and routes, but nothing looked out of place. As a lark, I removed eth2 from the newly created xenbr2 and it was able to ping again. Any other ideas? -----Original Message----- From: Tait Clarridge [mailto:Tait.Clarridge@lavalife.com] Sent: Thursday, July 02, 2009 1:12 PM To: Tait Clarridge; Jonathan Bayles; xen-users@lists.xensource.com Subject: RE: Simple network config question> > Hey guys, > > > > Usually all my guests go out through various bridges connected to > > eth0, but I came across a scenario where I need to connect one guest > > to a special backend network. The network is connected to an access > > port on a switch via > > eth2 on the xen server. If I set an IP on eth2 in the correct > > network it works > just > > fine. How can I share this connection up to a domU? I cant tell the > > switchport to become a trunk and bridge out internally like I > > usually do. Any help is > greatly > > appreciated!! > > What you may want to try is bridging the connection on eth2 to > something like > xenbr2 and in the config file have a line that is: > > vif=[''bridge=xenbr2'']EDIT: If you have a line in the domU configuration file that already has a vif stated, which will probably be the case (eg. vif=[''bridge=xenbr0'']) you can just add the following configuration for two network connections by doing something like: vif=[''bridge=xenbr0'',''bridge=xenbr2''] I have a similar setup for an iSCSI storage network where one of the NICs on the dom0 is connected to the iSCSI network and allows connectivity to the domU through a special network bridge "iscsibr0" which I add to the config file as I showed above. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I should add, I was able to ping again from the dom0, not the quest. Additionally, I should mention that I changed the IP address of the guest(windows2008 server) on the new adapter to something that wouldn''t conflict with the dom0 eth2 and it still failed to work properly. -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Jonathan Bayles Sent: Thursday, July 02, 2009 1:57 PM To: Tait Clarridge; xen-users@lists.xensource.com Subject: [Xen-users] RE: Simple network config question Thank you for getting back to me so quickly. I IP-ed the interface appropriately and was able to ping members of the network. I created the bridge and added eth2 to it, at that point I could no longer ping members of that network. I continued to configure the guest, and rebooted it, it came up with the new network interface containing IP identical to the one configured in the dom0. It was not able to ping the network either. I checked all manner of firewalls and routes, but nothing looked out of place. As a lark, I removed eth2 from the newly created xenbr2 and it was able to ping again. Any other ideas? -----Original Message----- From: Tait Clarridge [mailto:Tait.Clarridge@lavalife.com] Sent: Thursday, July 02, 2009 1:12 PM To: Tait Clarridge; Jonathan Bayles; xen-users@lists.xensource.com Subject: RE: Simple network config question> > Hey guys, > > > > Usually all my guests go out through various bridges connected to > > eth0, but I came across a scenario where I need to connect one guest > > to a special backend network. The network is connected to an access > > port on a switch via > > eth2 on the xen server. If I set an IP on eth2 in the correct > > network it works > just > > fine. How can I share this connection up to a domU? I cant tell the > > switchport to become a trunk and bridge out internally like I > > usually do. Any help is > greatly > > appreciated!! > > What you may want to try is bridging the connection on eth2 to > something like > xenbr2 and in the config file have a line that is: > > vif=[''bridge=xenbr2'']EDIT: If you have a line in the domU configuration file that already has a vif stated, which will probably be the case (eg. vif=[''bridge=xenbr0'']) you can just add the following configuration for two network connections by doing something like: vif=[''bridge=xenbr0'',''bridge=xenbr2''] I have a similar setup for an iSCSI storage network where one of the NICs on the dom0 is connected to the iSCSI network and allows connectivity to the domU through a special network bridge "iscsibr0" which I add to the config file as I showed above. _______________________________________________ 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
> Thank you for getting back to me so quickly. > > I IP-ed the interface appropriately and was able to ping members of the > network. > > I created the bridge and added eth2 to it, at that point I could no longer ping > members of that network.I found this happening to me as well, but the domU would be able to connect once I gave it an IP that was DIFFERENT from the one that was configured for "eth2" on the dom0 side.> > I continued to configure the guest, and rebooted it, it came up with the new > network interface containing IP identical to the one configured in the dom0. It > was not able to ping the network either. I checked all manner of firewalls and > routes, but nothing looked out of place.Yeah, like I said above, you need to have an IP different from the one configured for eth2 on the dom0 side. So for example, if eth2 in dom0 is 10.10.20.1 the IP for the new interface in domU should be 10.10.20.2 (or just something different). Could you give this a shot?> > As a lark, I removed eth2 from the newly created xenbr2 and it was able to > ping again.Yep, this was annoying for us as well, but I wasn''t going to dig through routes and stuff to figure it out. But like I said, even though I couldn''t ping from dom0 the domU interface had full connectivity... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I should add, I was able to ping again from the dom0, not the quest. > Additionally, I should mention that I changed the IP address of the > guest(windows2008 server) on the new adapter to something that wouldn''t > conflict with the dom0 eth2 and it still failed to work properly. >Interesting. And there are no iptables rules that would be conflicting? To troubleshoot you can try again after stopping iptables (Redhat: service iptables stop).. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users