From owner-freebsd-questions  Thu May 17 12:15:21 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from cody.jharris.com (cody.jharris.com [205.238.128.83])
	by hub.freebsd.org (Postfix) with ESMTP id EC37637B42C
	for <freebsd-questions@FreeBSD.ORG>; Thu, 17 May 2001 12:15:12 -0700 (PDT)
	(envelope-from nick@rogness.net)
Received: from localhost (nick@localhost)
	by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f4HKT1j56404;
	Thu, 17 May 2001 15:29:03 -0500 (CDT)
	(envelope-from nick@rogness.net)
Date: Thu, 17 May 2001 15:29:01 -0500 (CDT)
From: Nick Rogness <nick@rogness.net>
X-Sender: nick@cody.jharris.com
To: Peter Salvage <wizard@sybaweb.co.za>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Routing question - lengthy post
In-Reply-To: <015f01c0deeb$855fc1e0$0200a8c0@ait.co.za>
Message-ID: <Pine.BSF.4.21.0105171514270.54148-100000@cody.jharris.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 17 May 2001, Peter Salvage wrote:

> Hi all
> 

> I'm having a routing problem which I hope someone can help me solve:
> 
> This is a (lengthy - sorry) diagram of our network:


[snip'd out your drawing because of word wrap]
> 
> Routes added on Cisco 2511 are as follows:
> ip route 192.168.2.128 255.255.255.192 192.168.2.218
> ip route 192.168.2.228 255.255.255.252 192.168.2.218

	Why not add:

	ip route 192.168.0.0 255.255.255.0 192.168.2.218

> 
> Routes added on Cisco 1601 are as follows:
> ip route 0.0.0.0 0.0.0.0 192.168.0.1
> ip route 192.168.2.128 255.255.255.192 192.168.2.230

	OK.

> 
> This is the route I set on the remote router:
> ip route 0.0.0.0 0.0.0.0 192.168.2.229
> 
	OK.

> 1. If I telnet to the 1601,
> I can ping the remote router ser0 port (192.168.2.230)
> I can ping the remote router eth0 port (192.168.2.130)
> I can telnet to the remote router (192.168.2.230)
> I can traceroute to any of the above.
> 
> 2. From the 2511 or from my w/s behind the proxy (in the diagram
> above), I CAN'T traceroute or ping any of the above. I keep getting
> bounced between 192.168.2.217 and 192.168.2.218
> 

	The BSD machine does not know how to reach those networks.


> 3. From any of the w/s behind the remote router, I can't ping or
> traceroute past 192.168.0.9 (1601 eth0). Needless to say I can't surf
> or pop mail either
> 
> So, my conclusion is I need to add a route to the FreeBSD box.
> 
> Am I correct? If so, what would be the correct route statement(s) to
> add?

	Yes you are correct.


> add route 192.168.2.128/26 192.168.2.218?
> add route 192.168.2.228/30 192.168.2.218?
> 
> Am I close?

# route add -net 192.168.2.128 192.168.0.9 -netmask 255.255.255.192
# route add -net 192.168.2.228 192.168.0.9 -netmask 255.255.255.252


Nick Rogness <nick@rogness.net>
 - Keep on Routing in a Free World...
  "FreeBSD: The Power to Serve!"


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message