From owner-freebsd-questions Sun May 18 12:01:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07158 for questions-outgoing; Sun, 18 May 1997 12:01:49 -0700 (PDT) Received: from aage.priv.no (birk04.studby.uio.no [129.240.214.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07153 for ; Sun, 18 May 1997 12:01:46 -0700 (PDT) Received: (from aagero@localhost) by aage.priv.no (8.8.5/sendmail95) id VAA17782; Sun, 18 May 1997 21:00:56 +0200 (CEST) Message-ID: <19970518210056.35179@aage.priv.no> Date: Sun, 18 May 1997 21:00:56 +0200 From: =?iso-8859-1?Q?=C5ge_R=F8bekk?= To: freebsd-questions@freebsd.org Subject: IPDIVERT and natd in FreeBSD-2.2.1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74e X-OS: FreeBSD 3.0-CURRENT Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone got natd in ports from -current working on FreeBSD 2.2.1, using IPDIVERT and IPFIREWALL in the kernel? I've been trying every possible approach to this problem but to no avail. This host is on an ethernet with two ethernet cards, 3c950 and 3c905. The sole purpose with this configuration is to allow hosts on the inside network to connect to the outside network. I've added IPDIVERT and IPFIREWALL as options i the kernel config file, and configured ipfw to divert incoming traffic to a chosen port and run natd on that particular port. natd -verbose doesn't say anything either, but inspecting the divert rule accounting figures with ``ipfw -a l'' after some time shows that the kernel diverting mechanisms really are working. I made a small program which basically did sock = socket(...,IPPROTO_DIVERT); bind(sock, ...); read(sock, buff, BUFSIZ); but no data was ever read from the socket. IP firewall divert rules were present. -aage