From owner-freebsd-ports@FreeBSD.ORG Thu Jul 7 09:03:59 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B724106564A; Thu, 7 Jul 2011 09:03:59 +0000 (UTC) (envelope-from david.hunt@internode.on.net) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id 79DA98FC1B; Thu, 7 Jul 2011 09:03:57 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkICAFJvFU7Letn9/2dsb2JhbAAMR5km3BiGOASHR5tQ Received: from ppp203-122-217-253.static.internode.on.net (HELO [192.168.201.24]) ([203.122.217.253]) by ipmail04.adl6.internode.on.net with ESMTP; 07 Jul 2011 18:18:39 +0930 From: David Hunt Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 7 Jul 2011 18:18:37 +0930 Message-Id: <23E261BB-3CF1-4B4A-A17D-A6A4746A604D@internode.on.net> To: olgeni@FreeBSD.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Cc: ports@FreeBSD.org Subject: FreeBSD Port: webmin-1.550 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2011 09:03:59 -0000 HI there I have FreeBSD 8.1 and just updated to the current version (1.550) of = webmin, trying to get around the following error: error parsing IPNAT line rdr fxp0 from any to 192.168.33.3 -> = 192.168.1.5 at 192.168.33.3 line 7 Here is the IPFNat config file, which works just fine: # Active FTP map rules map fxp0 192.168.1.0/24 -> 0/32 proxy port 21 ftp/tcp map fxp0 0.0.0.0/0 -> 0/32 proxy port 21 ftp/tcp # # NAT Internal Traffic map fxp0 192.168.1.0/24 -> 0.0.0.0/32 # Web Server rdr fxp0 from any to 192.168.33.3 -> 192.168.1.5 rdr fxp0 from any to 192.168.33.4 -> 192.168.2.2 rdr fxp0 from any to 192.168.33.5 -> 192.168.2.4 map fxp0 192.168.2.0/24 -> 0.0.0.0/32 Any suggestions on what the issue/bug is? Many thanks David