From owner-freebsd-questions  Tue Nov 14 03:09:42 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA27861
          for questions-outgoing; Tue, 14 Nov 1995 03:09:42 -0800
Received: from iis (iis.webnet.com.au [203.8.105.2])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA27840
          for <questions@freebsd.org>; Tue, 14 Nov 1995 03:09:13 -0800
Received: (from maral@localhost) by iis (8.6.12/8.6.9) id WAA15097; Tue, 14 Nov 1995 22:12:56 +1100
Date: Tue, 14 Nov 1995 22:12:55 +1100 (EST)
From: Peter Marelas <maral@webnet.com.au>
X-Sender: maral@iis
To: Steve Spiller <steve@microdot.com>
cc: questions@freebsd.org
Subject: Re: Now it routes, now it don't!
In-Reply-To: <Pine.BSF.3.91.951113213456.365A-100000@ledzeppelin.microdot.com>
Message-ID: <Pine.SOL.3.91.951114220416.14753C-100000@iis>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
Precedence: bulk

On Mon, 13 Nov 1995, Steve Spiller wrote:

> 
> Well, I'm not sure what I did, or maybe it was a fluke that it was even 
> working in the first place, but i'm having routing problems.
> 
> Heres the scenerio :
> 
> Machine A and B are both a part of the network 205.134.198
> Machine A is running FreeBSD 2.0.5, and Machine B is running Windows 95.  
> Machine A talks to machine B, machine B responds.  All is happy and good.
> 
> Now, machine A uses its modem to dial my PPP provider and establish a 
> connection.  This connection creates the address of 204.71.144.66 ( local 
> ) and 204.71.144.?? ( remote ).  So now machine A ( 205.134.198.1 ) can 
> talk to machine B ( 205.134.198.2 ) and machine A can also talk to the 
> rest of the Net.
> 
> I have the address 204.71.144.66 as my default router,  and I have 
> #define GATEWAY compiled into the kernel etc ... as I said, it was 
> working.  Now, I can't for the life of me get machine B to see the Net or 
> vice verca.  In fact, the Outside world won't see machine A as 
> 205.134.198.1, only 204.71.144.66.
> 
> The only other option is that my providers portmaster dropped my network 
> from its routing tables ( this has happened before ), but I mailed the 
> network guy at my provider and asked him to check.  *shrug* I suppose 
> that he may not have yet ... but if anyone has a similar setup, can you 
> please send me a copy of your 'netstat -rn' output?
> 

What are you dialing into? annex?

Generally ppp connections look like so..

     Annex------------>PPP----------->ed0---------------|
xxx.xxx.xxx.xxx  205.134.198.1   205.134.198.2		|
	      Default Route: annex			|
						      Win95
						  205.134.198.3
					  Default route: 205.134.198.2

Route on annex would be..

Destination		Gateway		Netmask		Metric
205.134.198.0		annex		255.255.255.0	1

ie.
	route add 205.134.198.0 255.255.255.0 xxx.xxx.xxx.xxx 1

Setup of your machine would be.

in /etc/sysconf
	ifconfig_ed0="inet 203.134.198.1 netmask 0xffffff00"
	ifconfig_lo0="inet localhost"
	routedflages=''

and your pppd options would be..

	defaultroute (and device, etc)

Peter

PS: easiest way to test, ie. see who's end is at fault, is to ping from 
    both ends and look at modem lights.