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 <FUJITSU MPD3064AT> [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. -CharlieReceived on Wed Nov 10 2004 - 20:32:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:21 UTC