[Udpcast] Automatic reboot and DHCP-timeout

[Michael D. Setzer II]

Just as a quick addition. I just created a udpcast floppy image to 
take a look at it, and unfortunately, the busybox included with the 
floppy image is very stripped down. It doesn't contain reboot or 
many other option. The other versions might have a larger version of 
busybox. 

The other option I've used is the ipmac.txt to have it get the ip 
addresses based on the mac address. That way to avoid the dhcp 
at all. 

I've used busybox with g4l (ghost for linux) and added udpcast as 
an option. 


On 28 Jun 2005 at 9:41, D Teed wrote:

Date sent:      	Tue, 28 Jun 2005 09:41:55 -0300 (ADT)
From:           	D Teed <dteed at artistic.ca>
To:             	Lasse Riis <lists at lasseriis.dk>
Subject:        	Re: [Udpcast] Automatic reboot and DHCP-timeout
Copies to:      	udpcast at udpcast.linux.lu

> 
> I don't know about the Cisco switch aspect, but we had
> a similar problem with buggy tg3 ethernet device drivers
> which sounds similar.  Our solution was to use ipappend 1
> at the head of the default file for the udpcast PXE boot.
> This forces it to reuse the initial DHCP address rather than
> request it again.  The other thing that might be helpful
> is the command line option --rexmit-hello-interval for
> udp-sender.  You might also want to experiment with starting
> the receivers or udp-sender first and see if one works better
> for you.
> 
> The reboot should be possible by making a udpreceiver.post
> shell script within your image.  Busybox includes a reboot command,
> which may work for you.
> 
> --Donald Teed
> 
> 
> On Tue, 28 Jun 2005, Lasse Riis wrote:
> 
> > Hello
> >
> > I have 2 problems with udpcast currently:
> >
> > 1. I need to make the nodes reboot automatically efter udprcv has run.
> > (Otherwise I'll need a ladder to go around and reboot 36 nodes :) ) I
> > don't know how I do this I've tried unzipping and "un-cpio-ing" the
> > initrd but averything seems to be embedded in busybox, so I don't know
> > what to add. Is there a "recipe" for this somewhere.
> >
> > 2. We are using a Cisco switch here, which has an annoying habbit of
> > closing ports once linux releases the device just prior to a dhcp
> > discover request. The port won't get opened till at least 5-6 seconds
> > later. Hence udpcasts automatic dhcp-attempt fails. Is there a way to
> > increase the number of tries, or the timeout? The netwait= option is no
> > good here, because the port gets closed just when the dhcprequest is
> > initialised, so I need 5-6 secs from there. And this I guess can only be
> > done with a higher number of tries or a higher timeout.
> >
> > Lasse Riis
> >
> > _______________________________________________
> > Udpcast mailing list
> > Udpcast at udpcast.linux.lu
> > https://lll.lgl.lu/mailman/listinfo/udpcast
> >
> _______________________________________________
> Udpcast mailing list
> Udpcast at udpcast.linux.lu
> https://lll.lgl.lu/mailman/listinfo/udpcast
> 


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes at kuentos.guam.net                            
  mailto:msetzerii at gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
+----------------------------------------------------------+

http://setiathome.berkeley.edu
Number of Seti Units Returned:  16,811
Processing time:  31 years,  58 days,  0 hours, 48 minutes
(Total Hours: 272,953)