From owner-freebsd-net@FreeBSD.ORG Fri Jan 2 10:27:06 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4682416A4CE for ; Fri, 2 Jan 2004 10:27:06 -0800 (PST) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 473AE43D46 for ; Fri, 2 Jan 2004 10:27:04 -0800 (PST) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 55999 invoked from network); 2 Jan 2004 18:42:14 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 2 Jan 2004 18:42:14 -0000 Received: (nullmailer pid 13523 invoked by uid 136); Fri, 02 Jan 2004 18:29:43 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: To: Stephane Raimbault Date: Fri, 2 Jan 2004 21:29:43 +0300 (MSK) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1073068183.380806.13522.nullmailer@cicuta.babolo.ru> cc: net@freebsd.org Subject: Re: VLAN MTU problem in 4.9 ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2004 18:27:06 -0000 > Setting the MTU to 1496 on the router vlan interfaces didn't seem to help > me... however put the MTU to 1496 on the servers on the VLAN itself seems to > resolve the problem. so in the current configuration the router vlan > interfaces are set to 1500 and the servers on those interfaces are set to > 1496. Seems to work for now. > > Now, this doesn't seem all that normal. Where can I go from here to > troubleshoot this more and provide more information that might be able to > resolve this problem... if it's a problem that is... You can't be free from tune all your net for vlan mtu: - all switches involved must be at least verifyed not to drop long frames or right route vlans if it can work with tag based vlans - all interfaces in selected vlan must support the same common mtu I know now, that xl interface can't pass 1504 frames and most 1G interfaces can don't know about another 100M interfaces