Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!ptimtc!nntp-server.caltech.edu!gah From: gah@hood.hood.caltech.edu (Glen Herrmannsfeldt) Newsgroups: comp.protocols.nfs Subject: Re: RARP failure on subnets? Message-ID: Date: 14 Apr 91 05:40:33 GMT References: <9104122345.aa20048@ICS.UCI.EDU> Sender: news@nntp-server.caltech.edu Organization: California Institute of Technology, Pasadena Lines: 25 About RARP and subnets.... First, you have to run a separate rarpd for each ethernet interface. This is obvious. The second parameter to rarpd is the address, or name that translates to the address, of the interface. This is the address that rarpd uses as the from address in its reply packets. Some machines do not care where the reply packets come from. We recently bought some Sun SLC's, and added them to a subnet that had a diskless 4/110. I could not get the SLC's to net boot. A little etherfind would show that they would ignore the replies from bootparamd. It turned out that they came from what it thought was the wrong address. It expected the reply to come from the same machine that it got its rarp reply from. It did, but the rarp return address was wrong, so it didn't believe it. Anyway, check that address. Some machines may ignore it, so you won't notice anything wrong. Some may not, and you won't know why. I hope this helps someone. It took me a while to track down, including calls to sun. They had no idea, even though I sent etherfind -x output.