From owner-freebsd-questions@FreeBSD.ORG Fri Feb 18 11:05:26 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 048BF16A4CE for ; Fri, 18 Feb 2005 11:05:26 +0000 (GMT) Received: from priv-edtnes28.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FCC543D41 for ; Fri, 18 Feb 2005 11:05:25 +0000 (GMT) (envelope-from pfak@telus.net) Received: from [192.168.1.253] (really [64.180.103.26]) by priv-edtnes28.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20050218110525.URUB9620.priv-edtnes28.telusplanet.net@[192.168.1.253]>; Fri, 18 Feb 2005 04:05:25 -0700 Message-ID: <4215CBFA.7090706@telus.net> Date: Fri, 18 Feb 2005 03:05:30 -0800 From: Peter Kieser User-Agent: Mozilla Thunderbird 0.6+ (Windows/20050216) MIME-Version: 1.0 To: Dick Hoogendijk References: <4215BD9A.7070002@telus.net> <20050218105830.GC34932@lothlorien.nagual.st> In-Reply-To: <20050218105830.GC34932@lothlorien.nagual.st> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD multi-homed w/ipnat X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 11:05:26 -0000 Dick Hoogendijk wrote: >On 18 Feb Peter Kieser wrote: > > >>vr0: flags=8843 mtu 1500 >> inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 >> inet6 fe80::211:d8ff:fe3d:564a%vr0 prefixlen 64 scopeid 0x3 >> ether 00:11:d8:3d:56:4a >> media: Ethernet autoselect (100baseTX ) >> status: active >>map dc0 192.168.1.0/24 -> 0/32 >>map dc1 192.168.2.0/24 -> 0/32 >> >> > >I only seee 192.168.1.1 defined. Is this a typo or is there inof >missing? > > > The map with the CIDR prefix only specifies what IP addresses the NAT will masquerade for, still doesn't explain why 192.168.1.0/24 masquarde fails to work. You can specify the subnet mask for 192.168.1.1 as 255.255.254.0 to cover both those blocks, which is a 192.168.0.0/23.