From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <15c1d64edb07599e1ec4cb90cbbfdb68@caldo.demon.co.uk> From: Charles Forsyth To: 9fans@cse.psu.edu Subject: Re: [9fans] OK, cpu server is up. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Fri, 25 Apr 2003 15:30:30 +0100 Topicbox-Message-UUID: 99592b54-eacb-11e9-9e20-41e7f4b1d025 >>Here is an interesting problem. 9load gets its IP address but won't >>respond to ARP requests, so the tftp load of 9pccpu can't happen as Linux >>doesn't have an ARP entry for the geode. I assume on plan9 this is not an >>issue, but I have to hardwire the ARP cache for the CPU server or nobody >>can talk to it. by curious coincidence i happened earlier today to notice that dhcpd(8) observes: These programs support booting over the Internet. They should all be run on the same server to allow other systems to be booted. Dhcpd and tftpd are used to boot everything; `all on the same server'? i wondered about that at the time, but now i think i see: dhcpd makes an arp entry which is what probably allows it to work: tftpd ends up using that entry and 9load is never asked. if dhcpd and tftpd are on different machines, it won't work (unless i suppose proxyarp is also set)