From owner-freebsd-stable Mon Dec 4 18:41:15 2000 From owner-freebsd-stable@FreeBSD.ORG Mon Dec 4 18:41:11 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 7323E37B69C for ; Mon, 4 Dec 2000 18:41:09 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id NAA22141; Tue, 5 Dec 2000 13:41:03 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JXCICWSPR4EAFFW1@cim.alcatel.com.au>; Tue, 5 Dec 2000 13:40:59 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id eB52esK96410; Tue, 05 Dec 2000 13:40:54 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 05 Dec 2000 13:40:54 +1100 From: Peter Jeremy Subject: Re: Full size vlan packets. In-reply-to: <14865.20151.114515.408874@trooper.velocet.net>; from dgilbert@velocet.ca on Tue, Nov 14, 2000 at 09:39:51AM -0500 To: David Gilbert Cc: freebsd-stable@FreeBSD.ORG Mail-followup-to: David Gilbert , freebsd-stable@FreeBSD.ORG Message-id: <20001205134053.A95349@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <14865.20151.114515.408874@trooper.velocet.net> Sender: jeremyp@gsmx07.alcatel.com.au Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Catching up on old mail] On 2000-Nov-14 09:39:51 -0500, David Gilbert wrote: >I posted a request here some time ago about getting FreeBSD to do full >sized VLAN packets. I have boxes doing this running both -STABLE and -CURRENT (both somewhat old, but I'm in the process of upgrading the -STABLE machine). There are two major issues involved in getting this to work: 1) ifconfig on a vlan will set to the MTU to the MTU of the parent device - 4 unless the parent device's header length is the length of a VLAN header. This can be over-ridden by explicitly specifying the MTU in the ifconfig command. The header length (ifi_hdrlen) doesn't appear to be used elsewhere so it should also be possible to change the header length on the parent device, but my initial attempt to do this didn't work correctly. 2) The individual ethernet drivers need to be patched to support the larger packets. This is driver-dependent and varies from just changing the receive buffer size to playing with bits that are only documented under NDA. There are also assorted buglets in the general VLAN support: - kern/20611: VLAN parent device does not count VLAN output bytes - bin/21880: (libcap/tcpdump don't allow matching on VLAN packets) - kern/19436 (arp(8) doesn't support VLANs) At the device level, I have patches for tx (SMC 83c170), fxp (Intel 82559), xl (3Com 3c905B and later) and tl (TI ThunderLAN). (The latter two untested). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message