From owner-freebsd-net Fri Mar 12 13:50:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id D901F14CD4 for ; Fri, 12 Mar 1999 13:50:37 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id QAA06967; Fri, 12 Mar 1999 16:50:02 -0500 (EST) (envelope-from wollman) Date: Fri, 12 Mar 1999 16:50:02 -0500 (EST) From: Garrett Wollman Message-Id: <199903122150.QAA06967@khavrinen.lcs.mit.edu> To: "Lennart Blomstrom" Cc: Subject: vlan In-Reply-To: <001101be6cce$2d8f9580$44c0c6c3@k9d4.isdn-adv.telia.com> References: <000601be6a00$ecbce820$0102a8c0@milk.newtoy.com> <001101be6cce$2d8f9580$44c0c6c3@k9d4.isdn-adv.telia.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I've tried to use vlan (if_vlan.c ) on 3.0 and 3.1 release . > I've made a "hack" to set "parent" and "vlan#" via SIOCSETVLAN and I have > changed pci/id_de.c to accept mtu > 1500. Don't do this. Instead, increase the advertised header length by four. > Trap 12 > supervisor read, page not present. > Anybody got vlan working for TCP sessions ? There is nothing special about TCP as far as the network interface layer is concerned. You haven't come close to giving us enough information to debug this problem. For starters, how about a stack backtrace? Kernel configuration? Are you using BPF? (If so, there was a serious bug in the BPF handling of the vlan driver which may not be fixed in 3.x.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message