From owner-freebsd-questions Sun Apr 29 15:53:32 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nameserver.austclear.com.au (nameserver.austclear.com.au [192.83.119.132]) by hub.freebsd.org (Postfix) with ESMTP id 7502037B423 for ; Sun, 29 Apr 2001 15:53:28 -0700 (PDT) (envelope-from ahl@austclear.com.au) Received: from tungsten.austclear.com.au (tungsten.austclear.com.au [192.168.70.1]) by nameserver.austclear.com.au (8.9.3/8.9.3) with ESMTP id IAA04482; Mon, 30 Apr 2001 08:53:27 +1000 (EST) Received: from tungsten (tungsten [192.168.70.1]) by tungsten.austclear.com.au (8.9.3/8.9.3) with ESMTP id IAA12219; Mon, 30 Apr 2001 08:53:27 +1000 (EST) Message-Id: <200104292253.IAA12219@tungsten.austclear.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: kevin Cc: freebsd-questions@FreeBSD.ORG Subject: Re: routing troubles In-Reply-To: Message from kevin of "Sun, 29 Apr 2001 12:57:55 MST." <3AEC7243.D2AC9ABF@cco.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Apr 2001 08:53:26 +1000 From: Tony Landells Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use NAT. The 192.168.0.0/16 addresses should not be routed over the Internet and so the error would be if something actually responded from beyond your intranet. And by the way; what do you think you're accomplishing by hashing out part of the addresses? All it does it make it harder for other people to see what's going on and offer useful suggestions. If it weren't so obvious what's going on here, I would have ignored your message as I generally do with messages where people fiddle the addresses in the posted message "for security". Tony -- Tony Landells Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message