Re: Dom1 always does DHCP requests and vmid increasing

[Mike Brady <mike.brady@devnull.net.nz>]

I don't have tcpdump installed at the moment, but will do so shortly.

In the mean time I have been playing around a bit and have found the 
following.

1) Putting an ip=192.168.42.36 on the config file stops the DHCP request, but 
the domain still has two addresses - the 192.168.42.36 and 192.168.42.35 
(this is what is on the ifcfg-eth0 file).

2)  In looking at the create.py script (after a crash course in Python :-) I 
noticed that the 1.2.3.4 address is actually assigned as the nfsserver 
address, not the IP address.  To test this I set the nfs_server variable to 
'169.254.1.0' and now this address shows up in the DHCP server log.  The log 
entry is below.

Jul 28 20:49:22 spitfire dhcpd: DHCPREQUEST for 255.255.255.255 (169.254.1.0) 
from aa:00:00:00:00:11 via eth0: wrong network.
Jul 28 20:49:22 spitfire dhcpd: DHCPNAK on 255.255.255.255 to 
aa:00:00:00:00:11 via eth0
Jul 28 20:49:24 spitfire dhcpd: DHCPDISCOVER from aa:00:00:00:00:11 via eth0
Jul 28 20:49:25 spitfire dhcpd: DHCPOFFER on 192.168.42.96 to 
aa:00:00:00:00:11 via eth0
Jul 28 20:49:25 spitfire dhcpd: DHCPREQUEST for 192.168.42.96 (192.168.42.51) 
from aa:00:00:00:00:11 via eth0
Jul 28 20:49:25 spitfire dhcpd: DHCPACK on 192.168.42.96 to aa:00:00:00:00:11 
via eth0

I am still looking at the xm code to try and understand it.

Thanks

Mike



On Wed, 28 Jul 2004 08:00, Ian Pratt wrote:
> > > There's nothing in your config file below to cause the kernel to
> > > do a DHCP. Are you sure that your rc scripts aren't doing it?
> >
> > THe DHCP request that I am seeing requests ip adddress 1.2.3.4.  The only
> > place that I can find that address mentioned is in the domain
> > configuration, so I don't believe that it is the rc scripts, but I will
> > have another look later in the day.  Syslog entries also indicate that it
> > is a kernel DHCP request as opposed to a dhcpcd request.
>
> I might expect to see an ARP request for 1.2.3.4, but not a DHCP
> request. The 1.2.3.4 is just there to workaround a linux 2.6 bug,
> so could be removed altogether if you're booting 2.4.
>
> Can you post the first few packets of output from:
>  tcpdump -i vifX.Y -s 2048 -vvxe
>
> Ian


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click