* [email protected] [2009-11-25 15:59:47] > Sorry my configuration in the first email was - dom0+ dhcpserver(dom0 > running a DHCP-server) that is why you see e1000g0 as well along with > the r1 (vnic interface). > > However in my new configuration i.e dom0+ UC-dhcp (dhcpserver domU > running a DHCP-server) + UC-web (domU trying to obtain an IP address > via dhcp) The issue I see is the domU UC-web doesn't get an IP > address.
Understood. If snoop in the domU sees the DHCP request yet no offer is made it sounds like a dhcpd configuration problem. I know nothing about that piece of software, sorry. > Running snoop on domU (UC-dhcp): > bash-3.2# snoop -v -i /var/tmp/snoop.out > ETHER: ----- Ether Header ----- > ETHER: > ETHER: Packet 1 arrived at 7:54:13.78628 > ETHER: Packet size = 342 bytes > ETHER: Destination = ff:ff:ff:ff:ff:ff, (broadcast) > ETHER: Source = 0:16:3e:48:ee:66, > ETHER: Ethertype = 0800 (IP) > ETHER: > IP: ----- IP Header ----- > IP: > IP: Version = 4 > IP: Header length = 20 bytes > IP: Type of service = 0x00 > IP: xxx. .... = 0 (precedence) > IP: ...0 .... = normal delay > IP: .... 0... = normal throughput > IP: .... .0.. = normal reliability > IP: .... ..0. = not ECN capable transport > IP: .... ...0 = no ECN congestion experienced > IP: Total length = 328 bytes > IP: Identification = 11774 > IP: Flags = 0x4 > IP: .1.. .... = do not fragment > IP: ..0. .... = last fragment > IP: Fragment offset = 0 bytes > IP: Time to live = 255 seconds/hops > IP: Protocol = 17 (UDP) > IP: Header checksum = 4ca7 > IP: Source address = 0.0.0.0, OLD-BROADCAST > IP: Destination address = 255.255.255.255, BROADCAST > IP: No options > IP: > UDP: ----- UDP Header ----- > UDP: > UDP: Source port = 68 > UDP: Destination port = 67 (BOOTPS) > UDP: Length = 308 > UDP: Checksum = 0145 > UDP: > DHCP: ----- Dynamic Host Configuration Protocol ----- > DHCP: > DHCP: Hardware address type (htype) = 1 (Ethernet (10Mb)) > DHCP: Hardware address length (hlen) = 6 octets > DHCP: Relay agent hops = 0 > DHCP: Transaction ID = 0xf1071626 > DHCP: Time since boot = 0 seconds > DHCP: Flags = 0x0000 > DHCP: Client address (ciaddr) = 0.0.0.0 > DHCP: Your client address (yiaddr) = 0.0.0.0 > DHCP: Next server address (siaddr) = 0.0.0.0 > DHCP: Relay agent address (giaddr) = 0.0.0.0 > DHCP: Client hardware address (chaddr) = 00:16:3E:48:EE:66 > DHCP: > DHCP: ----- (Options) field options ----- > DHCP: > DHCP: Message type = DHCPDISCOVER > DHCP: Maximum DHCP Message Size = 1472 bytes > DHCP: IP Address Lease Time = -1 seconds > DHCP: Client Class Identifier = "SUNW.i86xpv" > DHCP: Requested Options: > DHCP: 1 (Subnet Mask) > DHCP: 3 (Router) > DHCP: 6 (DNS Servers) > DHCP: 12 (Client Hostname) > DHCP: 15 (DNS Domain Name) > DHCP: 28 (Broadcast Address) > DHCP: 43 (Vendor Specific Options) > > domU(UC-web) which is trying to obtain an IP address: > bash-3.2# ifconfig xnf0 > xnf0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2 > inet 0.0.0.0 netmask ff000000 broadcast 255.255.255.255 > ether 0:16:3e:48:ee:66 > > Sagun > On Nov 25, 2009, at 1:08 AM, David Edmondson wrote: > > Sagun, I'm confused about your configuration. You say: > > On system A the setup I have is: > > dom0+ dhcpserver(domU running a DHCP-server) + dhcpclientA (domU tryng > > to obtain an IP address via dhcp) > > Yet your in.dhcpd invocation mentions e1000g0: > > r...@lm2-dom0:~# /usr/lib/inet/in.dhcpd -dv -i r1,e1000g0 > > The domU can't access e1000g0, so how can you be running in.dhcpd there? > > dme. > -- > David Edmondson, Sun Microsystems, http://dme.org dme. -- David Edmondson, Sun Microsystems, http://dme.org _______________________________________________ xen-discuss mailing list [email protected]
