From owner-freebsd-current@FreeBSD.ORG Wed Nov 10 21:32:51 2004 Return-Path: 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 4953F16A4CE for ; Wed, 10 Nov 2004 21:32:51 +0000 (GMT) Received: from mailhost.schluting.com (schluting.com [131.252.214.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 131DE43D39 for ; Wed, 10 Nov 2004 21:32:51 +0000 (GMT) (envelope-from charlie@schluting.com) Received: from localhost (localhost [127.0.0.1]) by mailhost.schluting.com (Postfix) with ESMTP id 848D4244A for ; Wed, 10 Nov 2004 13:32:50 -0800 (PST) Received: from mailhost.schluting.com ([127.0.0.1]) by localhost (schluting.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61747-09 for ; Wed, 10 Nov 2004 13:32:42 -0800 (PST) Received: from [131.252.209.122] (smelly.cat.pdx.edu [131.252.209.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhost.schluting.com (Postfix) with ESMTP id 6CA7F21E3 for ; Wed, 10 Nov 2004 13:32:42 -0800 (PST) Message-ID: <419288F9.2050405@schluting.com> Date: Wed, 10 Nov 2004 13:32:41 -0800 From: Charlie Schluting User-Agent: Mozilla Thunderbird 0.6 (X11/20040519) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by your mom at schluting.com Subject: Re: em0, VLAN and bpf(?) trouble w/RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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 Nov 2004 21:32:51 -0000 Robert Watson wrote: > So I did a little local experimentation; I didn't run into the precise > problem you saw, instead getting ENOBUFS on sending. I think compiled > "device vlan" into the kernel to make debugging easier, and the problem > magically vanished. I'm going to keep trying to reproduce it, but for > grins, could you tell me if you're running with vlan support compiled in > or loaded, and if loaded, try compiling it in? A weird thing about that.. I compiled it in, "device vlan" ..but the modules is loaded. And when I boot, I see it trying to load the kernel module again after its loaded. If you can suggest why the module is loading, I'll fix it, and restart my bpf process to see if I can reproduce. I have nothing telling it to do this.. except in rc.conf I have: cloned_interfaces="vlan2" ifconfig_xl0="DHCP" ifconfig_fxp0="10.1.0.5 netmask 255.255.255.0" ifconfig_vlan2="inet 192.168.0.10 netmask 255.255.255.192 vlan 2 vlandev fxp0" dmesg shows: ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled IPsec: Initialized Security Association Processing. IP Filter: v3.4.31 initialized. Default = block all, Logging = enabled GEOM: create disk ad0 dp=0xc2d4a560 ad0: 6187MB [13410/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a IP Filter: already initialized <-- weird x2 IP Filter: already initialized module_register: module if_vlan already exists! <-- ? Module if_vlan failed to register: 17 dmz# kldstat Id Refs Address Size Name 1 2 0xc0400000 4678e4 kernel 2 1 0xc2e60000 4000 if_vlan.ko ...confused. -Charlie