Hi, I'm trying to setup a custom bootp server for Qube3's so that when a Qube is restored, it talks to our bootp server, which does the OS restore as per the CD, but it also applies all the up-to-date patches, because I've added them to the correct location on the machines HDD.
For some reason though bootp seems to be failing, the bootp machine shows: Apr 11 10:38:16 tester dhcpd: BOOTREQUEST from 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:16 tester dhcpd: BOOTREPLY on 10.0.0.150 to 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:21 tester dhcpd: BOOTREQUEST from 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:21 tester dhcpd: BOOTREPLY on 10.0.0.150 to 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:37 tester dhcpd: BOOTREQUEST from 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:37 tester dhcpd: BOOTREPLY on 10.0.0.150 to 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:39 tester dhcpd: BOOTREQUEST from 0:10:e0:4:cf:76 via eth1 Apr 11 10:38:39 tester dhcpd: BOOTREPLY on 10.0.0.150 to 0:10:e0:4:cf:76 via eth1 Which looks correct apart from it requesting/replying quite a few times over and over, the errors shown on the console of the Qube3: Sending BOOTP requests ... timed out! IP-Config: Retrying forever (NFS root)... eth0: speed=100 duplex=full link=up eth1: Warning PHY setup did not complete. Check cable. Sending BOOTP requests .. Which continues on forever it seems. Is there something I'm missing, is the Qube checking something else when it received the bootp and not allowing the request? Any help would be gratefully accepted! Andy [EMAIL PROTECTED] http://www.raqpak.com http://ineedlinux.info/ _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
