From owner-freebsd-isp Sun Aug 9 17:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12728 for freebsd-isp-outgoing; Sun, 9 Aug 1998 17:05:03 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12709 for ; Sun, 9 Aug 1998 17:05:00 -0700 (PDT) (envelope-from dev@wopr.inetu.net) Received: from localhost (dev@localhost) by wopr.inetu.net (8.8.8/8.8.5) with SMTP id UAA03099 for ; Sun, 9 Aug 1998 20:04:50 -0400 (EDT) Date: Sun, 9 Aug 1998 20:04:50 -0400 (EDT) From: Dev To: freebsd-isp@FreeBSD.ORG Subject: Basic routing question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have a few FreeBSD servers (2.2.5 - 2.2.7) listening on 5 class-c networks. Server A will allow connections from server B. Lets say server A is on 10.1.1.x and server B is on 10.2.2.x. Server allows connections from 10.2.2.2 (Server B). Now, Server B now also listens for a virtual host on 10.1.1.20. Now, Server B will contact server A through 10.1.1.20 instead of 10.2.2.2. Now, server A does not allow connections from that IP address. I am looking for the option that will explicity tell FreeBSD always talk from the 10.2.2.2 address. Thanks in advance Dev Chanchani - INetU, Inc.(tm) - http://www.INetU.net Electronic commerce - Web development - Web hosting dev@INetU.net - Phone: (610) 266-7441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message