From owner-freebsd-stable Wed Sep 22 6:54:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from crash.videotron.ab.ca (crash.videotron.ab.ca [206.75.216.220]) by hub.freebsd.org (Postfix) with ESMTP id B997C14BCA for ; Wed, 22 Sep 1999 06:54:11 -0700 (PDT) (envelope-from cwasser@v-wave.com) Received: from area51 (area51.v-wave.com [24.108.26.39]) by crash.videotron.ab.ca (8.9.2/8.9.2) with SMTP id HAA17064; Wed, 22 Sep 1999 07:53:58 -0600 (MDT) Message-ID: <000501bf0502$03439f20$271a6c18@vwave.com> From: "Chris Wasser" To: "Mikhail Teterin" , References: <199909220412.AAA26118@rtfm.newton> Subject: Re: ipnat's ftp proxying crashes -stable Date: Wed, 22 Sep 1999 07:54:38 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I originally had this problem using the ipnat that came with the FreeBSD kernel. Upgrade to 3.3.1+ and the problem will stop. ----- Original Message ----- From: Mikhail Teterin To: Sent: Tuesday, September 21, 1999 10:12 PM Subject: ipnat's ftp proxying crashes -stable > Hello! > > I'm trying to setup my dual interface machine to act as an ftp proxy for > my home LAN. > > The machine has two interfaces: ep0 (10.10.0.2/28) and ep1 (connected to > the cable-modem, with DHCP-obtained settings). > > It is a real shame, this part is so poorly documented, > but I did find the /usr/src/contrib/ipfilter/rules/ftp-proxy, > which was a little cryptic, but combining it with > http://www.dvl-software.com/freebsd/natrules.htm I setup the > /etc/natrules as follows: > > map ep1 0/0 -> 0.0.0.0/32 proxy port ftp ftp/tcp > > Ftp-ing to the server goes fine, I can log in. But whenever a data > connection is attempted -- say, for ``ls'', the nat-machine panics. > > The panics are different depending on whether the ftp-client is on the > same machine or on some other machine on the LAN. > > Actually, as I just found out, it can crash anytime after the rule above > is loaded -- I guess, any incoming attempt can trigger it :( > > I'm rebuilding the kernel without the omit-frame-pointer now, to get > meaningful information from the panic screen. But if you know what I'm > doing wrong -- just tell me now :) > > Thanks, > > -mi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message