Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!lll-lcc!qantel!hplabs!sdcrdcf!usc-oberon!bacall!uscvax!pv
From: pv@uscvax.UUCP (Peter Vanderbilt)
Newsgroups: net.unix-wizards
Subject: Gateway generates wrong IP returns address (4.2, Vax)
Message-ID: <29@uscvax.UUCP>
Date: Thu, 15-May-86 14:58:26 EDT
Article-I.D.: uscvax.29
Posted: Thu May 15 14:58:26 1986
Date-Received: Tue, 20-May-86 06:11:26 EDT
Reply-To: pv@usc-cse.UUCP (Peter Vanderbilt)
Organization: CS&CE Depts, U.S.C., Los Angeles, CA
Lines: 20


We have a VAX 750 running 4.2 gatewaying between two ethernets.  For some
reason, connections running over the second ethernet have the return
(source) IP address of the first ethernet.  This causes minor problems like
machines on the second net generating arp requests that are not responded
to.  Also the address of the first ethernet happens to end in .255 (class C
host number is all 1's) which some systems don't like (we're planning to
change this).

The code in ip_output.c looks OK which implies that higher level protocols
are (incorrectly) filling in the source IP address.

Has this been seen before?  Is there a known fix?

-- 
Peter Vanderbilt
  arpa:  pv@usc-cse.usc.edu
  csnet: pv@usc-cse
  uucp:  pv@uscvax.uucp or
    ...!{{decvax,ucbvax}!sdcsvax,hplabs,allegra,trwrb}!sdcrdcf!uscvax!pv