Date: Mon, 29 Mar 2004 09:36:49 -0800 From: "Jacob S. Barrett" <jbarrett@amduat.net> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: freebsd-net@FreeBSD.org Subject: Re: Disabling VLAN_HWTAGGING Message-ID: <200403290936.49345.jbarrett@amduat.net> In-Reply-To: <20040329081224.GC70021@ip.net.ua> References: <200403251118.40718.jbarrett@amduat.net> <200403270848.37996.jbarrett@amduat.net> <20040329081224.GC70021@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 29 March 2004 12:12 am, Ruslan Ermilov <ru@FreeBSD.org> wrote: > No, this is not of course expected. Can you add some debug printfs > in the ng_vlan.c:ng_vlan_rcvdata() and see if it ever receives the > VLAN tag, and if so, print its value (perhaps the tag is entered by > a driver in a network byte order). Bingo... I will dig around in if_nge.c to figure out where to swap the bytes. > Well, for IP/TCP/UDP checksumming, it's possible to switch the > corresponding bit in the interface's enabled capabilities field. > OTOH, switching VLAN stripping on/off requires reprogramming of > the hardware. > > Generally, if the hardware supports IP/TCP/UDP checksumming and > or VLAN tag removal/insertion, it's better to use it. We'd > better find the root of the problem and fix it. ;) I agree, so now that we have found it I will try to fix it. Thanks for your help. -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403290936.49345.jbarrett>