From owner-freebsd-questions Tue Feb 17 21:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23559 for freebsd-questions-outgoing; Tue, 17 Feb 1998 21:36:49 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23544 for ; Tue, 17 Feb 1998 21:36:24 -0800 (PST) (envelope-from font@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (font@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA00468 for ; Tue, 17 Feb 1998 23:36:20 -0600 (CST) Received: from localhost (font@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id XAA10233 for ; Tue, 17 Feb 1998 23:36:19 -0600 (CST) Date: Tue, 17 Feb 1998 23:36:19 -0600 (CST) From: Font To: questions@FreeBSD.ORG Subject: natd oddness in a recent SNAP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just thought I'd report an anomaly I found in 980119-SNAP. I upgraded a machine I was using for a firewall to this SNAP and found that my -redirect_port flag to natd was no longer working. I copied the natd binary over from 971030-SNAP (the release the firewall had previously) and functionality resumed. (I don't know if this is a recommended procedure, but it did work for me, this time.) I know that things aren't guaranteed to work in SNAPs (or anywhere), so I thought I'd report it here, since I assume many people would be using versions beyond 2.2.5-RELEASE due to the netatalk and printing problems in that one. If I should be reporting this somewhere else, please feel free to adjust my head. Hopefully this note will save someone an hour of work somewhere. :-) A bug in my MUA causes news.announce.newusers font to be sent to beneficiaries and senders of UCE/SPAM. @ mcs.net Wishes are like dishes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message