From owner-freebsd-hackers Mon Mar 31 00:36:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27242 for hackers-outgoing; Mon, 31 Mar 1997 00:36:23 -0800 (PST) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA27213 for ; Mon, 31 Mar 1997 00:36:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nlsystems.com (8.8.5/8.8.5) with SMTP id JAA27568; Mon, 31 Mar 1997 09:35:28 +0100 (BST) Date: Mon, 31 Mar 1997 09:35:28 +0100 (BST) From: Doug Rabson To: Adam Shostack cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Forcing IP packets through a virtual interface? In-Reply-To: <199703302038.PAA03573@homeport.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 30 Mar 1997, Adam Shostack wrote: > I'm having a problem NFS mounting disks where the server is a > FreeBSD (2.1.5) machine with several virtual interfaces and the client > is an OpenBSD 2.0 machine. The freebsd machine has two web servers in > two domains (www.homeport.org, www.chips4less.com). > > Having looked at a lot of tcpdumps, I believe that the problem > is that when Openbsd is trying to mount from machine A, it is > unwilling to accept NFS packets from machine B. > > Is there a way to force Freebsd to respond on the interface to > which a packet was addressed? I've examined the release notes for > versions between 2.1.5 and the current -RELEASE, and didn't see > anything that seemed applicable. (I'm considering moving the machine > to 2.2.1, to get the NFS 3 code, and see if that works any better, but > don't want to move without knowing that it will/is likely to fix the > problem.) This is on my list of things to fix. I would expect that a fix for this should be in the 2.2.5 release. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891