Subject: Re: wierd routing problem
To: John F. Woods <jfw@jfwhome.funhouse.com>
From: Rick Byers <rickb@iaw.on.ca>
List: current-users
Date: 05/20/1999 14:47:14
Hi,
I have the exact same problem on my network (see my latest message to
current-users).  In my case, the clients are Win95 and NetBSD-1.4
machines.  This just started when I upgraded to NetBSD-1.4.  I can get
to the IP you mentioned, but atleast two other IP's (209.5.112.33 and
204.71.148.0) get redirected to my gateway box.  Have you had any luck
solving this?  Seems pretty serious to me.

Thanks,
	Rick

"John F. Woods" wrote:
> 
> I have a fairly traditional setup, NetBSD 1.4 box with modem to the
> internet and an ethernet card for the house network; I also have a
> routed /24 for the home network (gotten way back when they were still
> encouraging organizations to apply for class C blocks if they ever
> *might* attach to the Internet).  I have an iMac on the Ethernet which
> I use for web browsing.  The important IP adresses are:
> 
>   146.115.236.216        jfwhome-ppp0.funhouse.com
>   192.160.125.65         jfwhome-we0.funhouse.com
>   192.160.125.71         imac.funhouse.com
> 
> OK, here's the strange part.  Just after I updated my main system to
> 1.4 (from mid-April current sources), I became unable to reach
> www.macosrumors.com from the iMac; instead, bizarrely enough, I get
> connected to my own web server on 192.160.125.65!  Yet, I have no
> trouble getting to any other web server I've tried.
> 
> It gets stranger.  If I use a traceroute program on the mac and do a
> traceroute to www.macosrumors.com (206.170.14.55), it goes one hop and
> stops, evidently satisfied, with a packet marked as coming from
> 192.160.125.65.  Yet if I try 206.160.14.54 or 206.160.14.56, it goes
> all the way out to the net and ends up at the appropriate host after
> an entirely plausible traceroute.
> 
> A mac problem?  I don't think so:  if I do a netstat -a while the iMac
> is connected to my webserver (after I tried to contact
> macosrumors.com), I see this:
> 
> $ netstat -a | less
> Active Internet connections (including servers)
> Proto Recv-Q Send-Q  Local Address        Foreign Address          State
> tcp        0      0  jfwhome.www          proxyi.emirates..64027   TIME_WAIT
> tcp        0      0  localhost.www        localhost.64359          TIME_WAIT
> tcp        0      0  mosr.com.www         imac.2051                ESTABLISHED
> tcp        0      0  jfwhome.www          proxyi.emirates..63758   TIME_WAIT
> tcp        0      0  mosr.com.www         imac.1864                FIN_WAIT_2
> 
> mosr.com is an alternate name for the address in question; yet
> evidently the NetBSD box believes that is a reasonable IP address to have
> as a local address!
> 
> And yet:  if I run a web browser on the NetBSD box, I can get to
> 206.170.14.55 just fine.  (Hmm, a second mac on the network gets the
> anomalous result.)
> 
> So it seems that there is a routing problem.  I (of course) don't have
> an explicit route; all I have is this:  (10.220.10.118 is the address
> of the ISP side of my PPP link)
> 
> $ route show
> Routing tables
> 
> Internet:
> Destination      Gateway            Flags
> default          10.220.10.118      UG
> 10.220.10.118    146.115.236.216    UH
> localhost        127.0.0.1          UH
> 192.160.125.0    link#1             U
> funhouse.com     0:40:5:a1:d4:ac    UH
> millan           0:5:2:eb:90:64     UH
> familymac        0:0:c5:42:ad:eb    UH
> imac             0:5:2:43:2:b0      UH
> 
> AppleTalk:
> (The appletalk routes had *better* *not* have anything to do with
> this...)
> 
> So, any ideas?