From owner-freebsd-hackers Sat Sep 27 03:23:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA15739 for hackers-outgoing; Sat, 27 Sep 1997 03:23:21 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA15734 for ; Sat, 27 Sep 1997 03:23:17 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.7/8.8.7) with ESMTP id DAA03335; Sat, 27 Sep 1997 03:23:15 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.7/8.8.7) with SMTP id DAA01288; Sat, 27 Sep 1997 03:23:15 -0700 (PDT) Date: Sat, 27 Sep 1997 03:23:15 -0700 (PDT) From: Chris Timmons To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: 'fxp' driver/hardware lossage (was Re: Alexander B. Povol's mail) In-Reply-To: <199709270110.SAA01062@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Are any of the folks who have "fxp driver" problems using aliases? I had an ip alias die on me the other day with a pile of arpresolve: can't allocate llinfo for n.n.n.n. where n.n.n.n was aliased on fxp0. 2.2-STABLE ~9/9/97 It probably just is a coincidence that this happened to me on fxp0; at about the same time i installed the pro/100b I started sending rip announcements up to the system through ppp0 from another box that has an ip address on the same network as fxp0's home via the miracle of proxyarp. This scenario has only happened once in about 6 weeks. To get things unconfused I had to say 'ifconfig fxp0 alias ...' again. Obviously this has nothing to do with the fxp driver per se, just that the symptoms were as these people described (at least as far as the ip alias was concerned.) Traffic through fxp0's true home network was not affected. -Chris