From owner-freebsd-questions@FreeBSD.ORG  Wed Jun 18 10:05:20 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 9B94537B401
	for <questions@freebsd.org>; Wed, 18 Jun 2003 10:05:20 -0700 (PDT)
Received: from norton.palomine.net (norton.palomine.net [66.93.48.52])
	by mx1.FreeBSD.org (Postfix) with SMTP id DC14D43F93
	for <questions@freebsd.org>; Wed, 18 Jun 2003 10:05:19 -0700 (PDT)
	(envelope-from sullrich@palomine.net)
Received: (qmail 96388 invoked by uid 1004); 18 Jun 2003 17:05:19 -0000
Date: Wed, 18 Jun 2003 13:05:19 -0400
From: SKU <sku-dated-1055955589.pjemfhkk@palomine.net>
To: questions@freebsd.org
Message-ID: <20030618170519.GA96152@palomine.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: NATD will not start with punch_fw option
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2003 17:05:20 -0000

Greetings,

I am working with 2 different machines that refuse to start natd with the punch_fw option.   As of this morning, one machine is up to date 4.8 stable and the other has sources from 4.11.03.

The problem is very hard to figure out.   When starting natd like:

/sbin/natd -n sis0 -punch_fw 100:4

It simply does not fork to the background and start processing packets.  Top shows natd with a state of run but is using 90%+ processor.  Also, it refuses to move packets.

If I start natd like this:

/sbin/natd -n sis0

The above works fine.  It immediately forks to the background and gives the message:

Aug 12 20:43:23 natd[432]: Aliasing to 10.0.250.173, mtu 1500 bytes

I have tried blowing away my source tree 3 times and have been working on this silly issue since sunday.   Also, this has happened in the past but I have no idea how I fixed it.

So my question is, does anybody have a cluestick that they can hit me with a couple of times?   It's bizarre that punch_fw does not work.   I have tried every option that I can think of including -dynamic -s -m etc but punch_fw is the deal breaker each time.

Thanks in advance,

SKU