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:
- 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.
- 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@udpcast.linux.lu https://lll.lgl.lu/mailman/listinfo/udpcast