From owner-freebsd-net@FreeBSD.ORG Thu Jul 29 09:05:13 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5558316A4CE for ; Thu, 29 Jul 2004 09:05:13 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF36E43D39 for ; Thu, 29 Jul 2004 09:05:12 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 6CDD41FFDD4; Thu, 29 Jul 2004 11:05:07 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 8CD6E1FF931; Thu, 29 Jul 2004 11:05:05 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 033C915389; Thu, 29 Jul 2004 09:02:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id EC1BC15384; Thu, 29 Jul 2004 09:02:56 +0000 (UTC) Date: Thu, 29 Jul 2004 09:02:56 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Poul-Henning Kamp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD net mailing list Subject: multi-instance natd problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 09:05:13 -0000 Hi, I started using the multi instance natd feature and running into problems. Every morning when the IP on the dialup interface with the default route (tun0) changes I need to re-start the natd. Else I am getting: natd[88668]: failed to write packet back (Permission denied) looks like natd deosn't get the IP change and still aliases packets to the old IP and the packets then get rejected by ipfw rules ? I would see this on the other interfaces too I think but though they are online they are idle and only used to see that the login is able to get in and for sporadic tests; will have to check tomorrow morning if needed. is anyone else seeing this behavior ? --- config extract --- log_denied log_ipfw_denied log deny_incoming #verbose globalport natd instance default interface tun0 port 8670 instance tun1 interface tun1 port 8671 ... --- end --- -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT