From owner-freebsd-hackers Sun Mar 30 12:41:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA11266 for hackers-outgoing; Sun, 30 Mar 1997 12:41:03 -0800 (PST) Received: from homeport.org (lighthouse.homeport.org [205.136.65.198]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA11259 for ; Sun, 30 Mar 1997 12:40:58 -0800 (PST) Received: (adam@localhost) by homeport.org (8.8.5/8.6.9) id PAA03573 for freebsd-hackers@FreeBSD.ORG; Sun, 30 Mar 1997 15:38:15 -0500 (EST) From: Adam Shostack Message-Id: <199703302038.PAA03573@homeport.org> Subject: Forcing IP packets through a virtual interface? To: freebsd-hackers@FreeBSD.ORG Date: Sun, 30 Mar 1997 15:38:15 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL27 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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.) Adam PS: If this is the wrong list, let me know. "General technical discussion" sounded closer than "user questions." -- "It is seldom that liberty of any kind is lost all at once." -Hume