Re: Using Mosaic and HTTPD with multiple network interfaces

Dave Long <dave@navisoft.com>
Errors-To: listmaster@www0.cern.ch
Date: Sun, 29 May 1994 13:37:28 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <Chameleon.4.00.940529044503.dave@sialic.navisoft.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: dave@navisoft.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Dave Long <dave@navisoft.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Using Mosaic and HTTPD with multiple network interfaces 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
Christian's hack isn't *that* ugly, when you consider that it
could be used for web robots and slideshows as well.  It
does need to be Reply-To: <socket>, instead of just <ip>.

If one didn't mind generally making the connection between
the machines asymmetric, it ought to be relatively easy to
modify the routing tables on both machines such that
A looks up B, and uses PPP0, then B looks up A, and uses FR0.

-Dave