From owner-freebsd-current Sat Aug 24 00:23:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA13499 for current-outgoing; Sat, 24 Aug 1996 00:23:26 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA13493 for ; Sat, 24 Aug 1996 00:23:23 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id AAA20488 for ; Sat, 24 Aug 1996 00:23:21 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA15616; Sat, 24 Aug 1996 09:21:22 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA15971; Sat, 24 Aug 1996 09:21:22 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA09341; Sat, 24 Aug 1996 09:07:05 +0200 (MET DST) From: J Wunsch Message-Id: <199608240707.JAA09341@uriah.heep.sax.de> Subject: Re: rarpd broken on 2.2-960801-SNAP? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 24 Aug 1996 09:07:05 +0200 (MET DST) Cc: taob@io.org (Brian Tao) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Brian Tao at "Aug 24, 96 02:31:38 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Brian Tao wrote: > In all cases, tcpdump shows rarp requests from the terminal is > being received by the interface on the server. However, the 2.2 > server isn't sending out a reply according to tcpdump. I tried using > a 255.255.255.0 netmask on the server and renumbering the X terminal > to 10.0.0.4 (to be in the same network), to no avail. The /etc/hosts, > /etc/ethers and /tftpboot directory are all in order. That's already the second question in this direction. Basically, rarpd misses a -v option, so the best you could do is stuffing a bunch of printf's into it, and watching it why it doesn't send replies. The source of rarpd itself has not been modified for a long time. Of course, if you hide the printf's fine behind some -v option, finally fire off send-pr, and submit the modification! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)