From nobody  Wed Apr 16 05:30:21 1997
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA24163;
          Wed, 16 Apr 1997 05:30:21 -0700 (PDT)
Message-Id: <199704161230.FAA24163@freefall.freebsd.org>
Date: Wed, 16 Apr 1997 05:30:21 -0700 (PDT)
From: simat@enta.net
To: freebsd-gnats-submit@freebsd.org
Subject: Unable to Route to a different Class C with machine on same ethernet and diff Class C
X-Send-Pr-Version: www-1.0

>Number:         3307
>Category:       bin
>Synopsis:       Unable to Route to a different Class C with machine on same ethernet and diff Class C
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 16 05:40:01 PDT 1997
>Closed-Date:    Tue Apr 14 12:30:41 PDT 1998
>Last-Modified:  Tue Apr 14 12:30:56 PDT 1998
>Originator:     Simon Atkin
>Release:        2.2.1
>Organization:
Enta Technologies Ltd
>Environment:
FreeBSD callisto.enta.co.uk 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE #0: Wed Apr  9 13:29:46 BST 1997     
simat@callisto.enta.co.uk:/usr/src/sys/compile/SIMAT  i386
# 
>Description:
My new FreeBSD is on IP 207.24.132.1, I am trying to route
to network 207.24.36.0 using route add -net 207.24.36.0 207.24.132.1
This machine is on a different Class C because the company is
split in two.
If I add the above route the machine runs dog slow and normal
name resolution from /etc/hosts doesn't work very fast.

The machine is a P133 with 48MB and 2GB SCSI Drive.
P.S Networks 207.24.36.0 and 207.24.132.0 are on the same ethernet.

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: joerg 
State-Changed-When: Sun Aug 24 10:53:52 MEST 1997 
State-Changed-Why:  

What you are doing is not the way this is supposed to work.  I'm 
surprised you even get something that is ``slightly operational'' 
using your method (i.e. it's more like a bug than a feature that it 
works ``a little'' at all). 

In order to route between two networks on a single wire, you need an 
IP (alias) address in boths nets.  (That's what IP aliases have been 
introduced for in 4.4BSD.)  If you are going to offer routing service 
between both nets for other hosts, you also need to turn on IP 
forwarding. 

So please try 

ifconfig xx0 207.24.132.1 
ifconfig xx0 207.24.36.YYY alias 

and tell us whether this solved your problem. 

State-Changed-From-To: feedback->closed 
State-Changed-By: phk 
State-Changed-When: Tue Apr 14 12:30:41 PDT 1998 
State-Changed-Why:  
timed out 
>Unformatted:
