From owner-freebsd-questions@FreeBSD.ORG Fri Apr 1 14:27:09 2005 Return-Path: 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 5B9BF16A4CE for ; Fri, 1 Apr 2005 14:27:09 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA02643D1F for ; Fri, 1 Apr 2005 14:27:08 +0000 (GMT) (envelope-from pergesu@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so872126wri for ; Fri, 01 Apr 2005 06:27:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iJR0Pdm98zUcdZ6r0Vl721Q2ltSdTEo9alupN9FEiu7yW84OEToxYEgLjR1ovJSHuSGg6NRI+TmMlFqeSmgjLh0qTvbGv0AocQ85kg5UJsElJxYcGH9kCkrJJbK0oh3rgK20K0K7tGDLDUU/aYvvV0vrFo7fq8tS+gNTGuwWDsY= Received: by 10.54.14.75 with SMTP id 75mr778609wrn; Fri, 01 Apr 2005 06:25:00 -0800 (PST) Received: by 10.54.42.28 with HTTP; Fri, 1 Apr 2005 06:24:58 -0800 (PST) Message-ID: <810a540e0504010624372e13e0@mail.gmail.com> Date: Fri, 1 Apr 2005 07:24:58 -0700 From: Pat Maddox To: FreeBSD Questions In-Reply-To: <8664z79ejp.fsf@amidala.datadok.no> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <810a540e05033109303d0d2ba4@mail.gmail.com> <8664z79ejp.fsf@amidala.datadok.no> Subject: Re: Problem with PF X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pat Maddox List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2005 14:27:09 -0000 I found it out, just didn't have pf.ko loaded up. On Mar 31, 2005 11:50 PM, Peter N. M. Hansteen wrote: > Pat Maddox writes: > > > FreeBSD 5.3-RELEASE-p5. I'm not sure how to check the pf version. > > One possible source of trouble is running pf from ports on 5.3-release > or newer. That could happen if you were running, say, 5.2.something with > the port, upgraded your system to 5.3 but left the port in place. > > > I just started getting this error a couple days ago, and I've got > > absolutely no clue why. I don't recall making any significant changes > > to the box. > > That probably takes care of the incompatible port theory, then. > Strange. The error message looks like the network interface has not > been properly configured. > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ > "First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >