From owner-freebsd-security Mon Oct 29 0:58:15 2001 Delivered-To: freebsd-security@freebsd.org Received: from mine.kame.net (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id 3D74B37B403 for ; Mon, 29 Oct 2001 00:58:12 -0800 (PST) Received: from localhost ([3ffe:501:4819:1000:260:1dff:fe21:f766]) by mine.kame.net (8.11.1/3.7W) with ESMTP id f9T9BvH68358; Mon, 29 Oct 2001 18:11:57 +0900 (JST) To: jus@security.za.net Cc: freebsd-security@freebsd.org Subject: Re: Upgrade to 4.4-STABLE introduces IPSec problems..? In-Reply-To: Your message of "Mon, 29 Oct 2001 08:02:15 +0200 (SAST)" References: X-Mailer: Cue version 0.6 (011026-1440/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20011029175748V.sakane@kame.net> Date: Mon, 29 Oct 2001 17:57:48 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20000228(IM140) Lines: 9 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Recently I upgraded my workstation from 4.2-STABLE to 4.4-STABLE. I left > my ipsec.conf's as they were, expecting all would continue as before.. but > I seem to have hit a snag. Ever since the upgrade, I have either been > unable to transfer data in sizeable quantities (more than a few KB) or at > all between my server or my workstation either direction, whether by ftp, > scp, http, etc.. upon flushing all IPSec rules, however, things return to > normal. did you configure that there was no inbound security policy both side ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message