From owner-freebsd-current@FreeBSD.ORG Wed Aug 10 16:03:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6317016A41F for ; Wed, 10 Aug 2005 16:03:06 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id F135C43D46 for ; Wed, 10 Aug 2005 16:03:05 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so163613wra for ; Wed, 10 Aug 2005 09:03:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GIzPHL7tvypixhNm6UF7oVbv8/9kEmcl2/xVS8An1MWRwK0BFtI6CDN8LexwMaXzi9N182DF5ZyFaO2V17MrCwjdo2sAqvxay54tTTWKLQwOHQiZl6nxUJrCVzP5pQ2BFpNdDj7jCGTabjvDF443uU4xXJkw0TjXEyGEs2vUho0= Received: by 10.54.151.4 with SMTP id y4mr550330wrd; Wed, 10 Aug 2005 09:03:05 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Wed, 10 Aug 2005 09:03:05 -0700 (PDT) Message-ID: <790a9fff05081009035e400cb0@mail.gmail.com> Date: Wed, 10 Aug 2005 11:03:05 -0500 From: Scot Hetzel To: "David J. Orman" In-Reply-To: <20050809213656.GA90417@corenode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050809213656.GA90417@corenode.com> Cc: freebsd-current@freebsd.org Subject: Re: strange mtu warnings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 16:03:06 -0000 On 8/9/05, David J. Orman wrote: > Hi again, >=20 > This problem only started happening since upgrading from 5.4-p6 to > 6-beta2 on one of my test firewalls. >=20 > Aug 9 11:25:46 firewall1 kernel: bridge0: MTU mismatch, frame length > 1514 exceeds 1500 on sis1 > Aug 9 11:26:14 firewall1 last message repeated 223 times > Aug 9 11:26:14 firewall1 kernel: bridge0: MTU mismatch, frame length > 1514 exceeds 1500 on sis0 > Aug 9 11:26:15 firewall1 kernel: bridge0: MTU mismatch, frame length > 1514 exceeds 1500 on sis1 >=20 > All three are MTU 1500, so is this a bug or? Any possible solutions? >=20 Don't know if it is a bug, but you could try setting the mtu to 1514 and see if this fixes the problem. --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.