[BusyBox] udhcpc problem

[Miles Roper]

hi guys,

found the problem, from the ts 2.0.1 changelog

 * Fixed Problem with hostnames not being registered correctly in DNS, was
  caused by not first releasing the dhcp lease, before restarting udhcpc

Thanks for your help

Cheers

Miles

-----Original Message-----
From: Russ Dill [mailto:Russ.Dill at asu.edu]
Sent: Sunday, 16 May 2004 06:28 p.m.
To: Miles Roper
Cc: Thinstation-Developer (E-mail); Thinstation-General (E-mail);
'busybox at busybox.net'; Bob Gilmore
Subject: Re: [BusyBox] udhcpc problem


On Thu, 2004-05-13 at 21:24, Miles Roper wrote:
> Hi All,
> 
> I've got a problem which has been bugging me for ages with Thinstation.
For
> some reason some PCs don't seem to get there DNS entries updated.  other
> times it works ok.
> 
> How the network script works, basically....
> 
> first gets a dhcpc lease with a name of XX_MACADDRESS ie TS_1010101010101
> 
> it then downloads the thinstation.hosts file and finds the corresponding
MAC
> address.  It then shuts down the udhcpc daemon with a kill -SIGHUP.  Then
> starts it again with the new name.
> 
> This seems to work 80% of the time, but around 20% of the time the lease
> gets created, but no DNS entry gets updated.
> 
> We are using a win2k DHCP DNS server.
> 
> Its not a problem with the scripts as logging into the machine shows the
> hostname is correct and udhcpc is running with a 
> 
> udhcpc -i eth0 -H TS-018 -s /etc/init.d/network_script
> 
> this is the same on a machine which works and which doesn't
> 
> One interesting note, in Win2k DHCP, looking at the scope address leases,
> the machines which have this problem have a pencil symbol on top of the
> little computer picture.  From the MS website the description is below.
> 
> Active lease, DNS dynamic update pending. This address is not available
for
> lease by the DHCP server.
> 
> Any ideas?

get a packet dump of the activity.

-- 
Russ Dill <Russ.Dill at asu.edu>

==================================================
Attention:
The information contained in this message and/or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by person or entities other than the intended recipient
is prohibited.  If you receive this in error, please contact the sender and delete the material from your system and destroy any copies.
===================================================