From owner-freebsd-isp Thu Sep 12 07:31:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA07812 for isp-outgoing; Thu, 12 Sep 1996 07:31:09 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA07791; Thu, 12 Sep 1996 07:31:03 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14761(2)>; Thu, 12 Sep 1996 07:30:28 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177595>; Thu, 12 Sep 1996 07:30:13 -0700 To: Stephen Fisher cc: Jos Vissers , Bill Fenner , questions@freebsd.org, isp@freebsd.org Subject: Re: Ethernet routes wrong? [was: Why does arp not work when ip-alias] In-reply-to: Your message of "Wed, 11 Sep 96 20:56:54 PDT." Date: Thu, 12 Sep 1996 07:30:09 PDT From: Bill Fenner Message-Id: <96Sep12.073013pdt.177595@crevenia.parc.xerox.com> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message you write: >Windows/Dos PC on my ethernet. What happens is when I try to >ping it it automatically pops up in the routing tables as: > >IP.IP.IP.11 link#2 UHRLW 0 7 ep0 10 > >link#2? Why? Then ping start spitting up things about "host is down". "link#2" indicates that it knows which interface it wants to send it out, but that ARP hasn't succeeded in fully resolving the address yet. If you say "arp -a" it will print "(incomplete)" for this address. To help figure out why arp is failing, your best bet is to use tcpdump. You need to have bpf compiled into your kernel, and then you can say "tcpdump -n -i arp". >When I manually add it and set the gateteway to someone else on my >ethernet like my main router and it doesn't work out and I delete it the >entire system crashes. This crash is fixed in -current. Bill