I''ve asked this question before, and aside from a response asking me if DHCP was turned on (it is and all other clients on that network are communicating properly), received no further assistance. I hope someone can be of further assistance this time. I have a CentOS 5 64-bit machine running a 4-core Intel processor and 4GB of memory with two onboard network cards. The network cards are fully supported, eth0 and eth1 show up and obtain DHCP addresses from their respective networks eth0 is 192.168.1.220 (/24 subnet) gateway: 192.168.1.254 eth1 is 192.168.2.220 (/24 subnet) gateway: 192.168.2.254 default gateway is 192.168.2.254 (eth1 comes up second, this is auto-set) I have this script running as my network-bridge script wrapper: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1 as such, I have both bridges: xenbr0 mapped to eth0 and xenbr1 mapped to eth1 Any and all guests on XEN Virtualization obtain an IP address from the eth0/xenbr0 side of the equation (an address on the 192.168.1.0/24 network) Any and all guests on XEN Virtualization DO NOT obtain an IP address from the eth1/xenbr1 side of the equation (on the 192.168.2.0/24 network) Here is an example of one of my guest configurations: name = "VendPrintMDID" builder = "hvm" memory = "1024" disk = [ ''file:/xen/disks/VendPrintMDID,hda,w'', ''file:/xen/iso/MWS2003R2-i386-DISK1.iso,hdc:cdrom,r'', ''file:/xen/iso/MWS2003R2-i386-DISK2.iso,hdd:cd$ vif = [ ''type=ioemu, mac=00:16:3e:4c:69:28, bridge=xenbr0'', ''type=ioemu, mac=01:16:3e:4c:69:28, bridge=xenbr1'' ] #uuid = "0a08915c-636d-cc1d-8a6c-8d1e457bdcd1" device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 and the routing table: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 192.168.2.254 0.0.0.0 UG 0 0 0 eth1 ifconfig shows both xenbr0 and xenbr1 up, a bunch of vif''s up/etc. does anyone have any clue what the problem is here and why my guests can''t communicate in or out on xenbr1? Thanks! David Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Todd wrote:> I''ve asked this question before, and aside from a response asking me > if DHCP was turned on (it is and all other clients on that network are > communicating properly), received no further assistance. I hope > someone can be of further assistance this time. > > > I have a CentOS 5 64-bit machine running a 4-core Intel processor and > 4GB of memory with two onboard network cards. > > The network cards are fully supported, eth0 and eth1 show up and > obtain DHCP addresses from their respective networks > eth0 is 192.168.1.220 (/24 subnet) gateway: 192.168.1.254 > eth1 is 192.168.2.220 (/24 subnet) gateway: 192.168.2.254 > default gateway is 192.168.2.254 (eth1 comes up second, this is auto-set) > > I have this script running as my network-bridge script wrapper: > #!/bin/sh > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=0 > "$dir/network-bridge" "$@" vifnum=1 > > as such, I have both bridges: xenbr0 mapped to eth0 and xenbr1 mapped > to eth1 > > Any and all guests on XEN Virtualization obtain an IP address from the > eth0/xenbr0 side of the equation (an address on the 192.168.1.0/24 > network) > Any and all guests on XEN Virtualization DO NOT obtain an IP address > from the eth1/xenbr1 side of the equation (on the 192.168.2.0/24 network) > > Here is an example of one of my guest configurations: > name = "VendPrintMDID" > builder = "hvm" > memory = "1024" > disk = [ ''file:/xen/disks/VendPrintMDID,hda,w'', > ''file:/xen/iso/MWS2003R2-i386-DISK1.iso,hdc:cdrom,r'', > ''file:/xen/iso/MWS2003R2-i386-DISK2.iso,hdd:cd$ > vif = [ ''type=ioemu, mac=00:16:3e:4c:69:28, bridge=xenbr0'', > ''type=ioemu, mac=01:16:3e:4c:69:28, bridge=xenbr1'' ]It''s because the mac address for the second NIC is not from the reserved range for xen. Use a mac address from 00:16:3e:xx:xx:xx. --Sadique> #uuid = "0a08915c-636d-cc1d-8a6c-8d1e457bdcd1" > device_model = "/usr/lib64/xen/bin/qemu-dm" > kernel = "/usr/lib/xen/boot/hvmloader" > vnc=1 > vncunused=1 > apic=1 > acpi=1 > pae=1 > > and the routing table: > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window > irtt Iface > 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth1 > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > 0 eth1 > 0.0.0.0 192.168.2.254 0.0.0.0 UG 0 0 > 0 eth1 > > > ifconfig shows both xenbr0 and xenbr1 up, a bunch of vif''s up/etc. > > does anyone have any clue what the problem is here and why my guests > can''t communicate in or out on xenbr1? > > Thanks! > David Todd > > > _______________________________________________ > 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
Sadique Puthen wrote:> David Todd wrote: >> vif = [ ''type=ioemu, mac=00:16:3e:4c:69:28, bridge=xenbr0'', >> ''type=ioemu, mac=01:16:3e:4c:69:28, bridge=xenbr1'' ] > > It''s because the mac address for the second NIC is not from the reserved > range for xen. Use a mac address from 00:16:3e:xx:xx:xx. > > --SadiqueHi! Sadique''s advice to use 00:16:3e:xx:xx:xx is correct, but the reason that "01:16:3e:4c:69:28" doesn''t work is because it is a broadcast address. Nothing else. mac=01:16:3e:4c:69:28 -----^--------------- A broadcast address is specified by setting the least significant bit in the most significant byte is set to 1. See <http://en.wikipedia.org/wiki/MAC_address>. (And by the way, you can pick any MAC address that begins with "x2", "x6", "xA" or "xE". They are so called "locally administered addresses" and their first byte is binary "xxxxxx10".) Best regards, /Martin Leben _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Quoting Martin Leben <martin2006@leben.nu>:> > Hi! > > Sadique''s advice to use 00:16:3e:xx:xx:xx is correct, but the reason > that "01:16:3e:4c:69:28" doesn''t work is because it is a broadcast > address. Nothing else. > > mac=01:16:3e:4c:69:28 > -----^--------------- > A broadcast address is specified by setting the least significant bit > in the most significant byte is set to 1. See > <http://en.wikipedia.org/wiki/MAC_address>. > > (And by the way, you can pick any MAC address that begins with "x2", > "x6", "xA" or "xE". They are so called "locally administered addresses" > and their first byte is binary "xxxxxx10".) > > Best regards, > /Martin Leben >Thanks for that bit of information. I did not know this. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users