Re: Using Mosaic and HTTPD with multiple network interfaces

• Mail folder: WWW Talk Apr 94-present
• Next message: Rick Troth: "Re: Performance analysis questions "
• Previous message: Daniel W. Connolly: "Re: Performance analysis questions "
• Maybe in reply to: Amarendranath: "Using Mosaic and HTTPD with multiple network interfaces"

Errors-To: listmaster@www0.cern.ch
Date: Sun, 29 May 1994 06:12:08 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9405290332.AA17161@Xenon.Stanford.EDU>
Errors-To: listmaster@www0.cern.ch
Reply-To: mogens@CS.Stanford.EDU
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Christian L. Mogensen <mogens@CS.Stanford.EDU>
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
Content-Type: text
X-Mailer: ELM [version 2.4 PL21]
X-Mailer: ELM [version 2.4 PL21]

Ugly hack:
hack the client to send a 
	Reply-To: <ip-address> 
along with its other HTTP requests (Accept: foo/bar ...).

Then hack the server so it groks Reply-To.  That's the software
version of fixing this - it sucks because it ties you to this
particular server and this particular client.

Better hack:
Hack the IP interface to reroute packets going down to PPP1 to
FR1.  Still ugly - and loses if you only want to redirect Mosaic
packets.  (or vice-versa: get PPP to make believe it is on frame
relay.  Get Mosaic to lie about its present IP address...  This
requires that the FR client (? - what is on the FR node anyway?)
to lie convincingly too.

Best hack:
Avoid the situation altogether; live with slow PPP connection
or drop PPP altogether...

Christian "eeew - ugleee"