From owner-freebsd-isp Thu Jun 4 16:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02342 for freebsd-isp-outgoing; Thu, 4 Jun 1998 16:06:20 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02295 for ; Thu, 4 Jun 1998 16:06:12 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.8.7/8.8.2) with SMTP id QAA28373; Thu, 4 Jun 1998 16:07:15 -0700 (PDT) Date: Thu, 4 Jun 1998 16:07:15 -0700 (PDT) From: Dan Busarow To: Paul Stewart cc: freebsd-isp@FreeBSD.ORG Subject: Re: Long Question...:) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 4 Jun 1998, Paul Stewart wrote: > Our upsteam provider is telling us that we don't need to change our LAN as > they can tell our LAN router to route all packets in that range to the > server that connects the remote LAN to ours... does this make sense? They > say it's just a matter of static routing? Yes and no. You could enter static routes for each machine on the remote net but only packets going to/through the router will see them. So Internet traffic for the remote site would work fine. LAN to LAN wouldn't unless you added static routes to everything on the LAN. Going with NAT and private address space is much easier. Dan -- Dan Busarow 949 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message