From owner-freebsd-questions@FreeBSD.ORG Wed May 16 20:42:29 2012 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BEFD1065670 for ; Wed, 16 May 2012 20:42:29 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from nk11p00mm-asmtp003.mac.com (nk11p00mm-asmtp003.mac.com [17.158.161.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1F4978FC0A for ; Wed, 16 May 2012 20:42:29 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com (unknown [17.209.4.71]) by nk11p00mm-asmtp003.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPSA id <0M4400LFFUUJKZ60@nk11p00mm-asmtp003.mac.com> for questions@freebsd.org; Wed, 16 May 2012 20:42:21 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7580,1.0.260,0.0.0000 definitions=2012-05-16_08:2012-05-16, 2012-05-16, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1205160244 From: Chuck Swiger In-reply-to: <20120516200837.GA63280@skytracker.ca> Date: Wed, 16 May 2012 13:42:19 -0700 Message-id: <70BC5C41-FD4F-4B57-86F8-8C48BA075EC1@mac.com> References: <20120516200837.GA63280@skytracker.ca> To: David Banning X-Mailer: Apple Mail (2.1084) Cc: questions@freebsd.org Subject: Re: problems with networking and route command X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2012 20:42:29 -0000 Hi-- On May 16, 2012, at 1:08 PM, David Banning wrote: [ ... ] > It is machines that connect and receive via DHCP 192.168.1.2 and above that > can't connect to the internet though the server. I don't know a whole > lot about route - I have been attempting a variation of route commands > without success. You need to implement NAT on this box, since 192.168.0.0/16 is an RFC-1918 unrouteable private network range. Regards, -- -Chuck