Re: Polishing touch
here what is (probably) going on. when system starts up you have no tap0 interface. ifconfig(8) can not find tap0 interface and hmmm, dunno, long before ifconfig I get : tap0: bpf attached now the thing about tap(4) (and tun(4)) interfaces is that they are *virtual*, i.e. in order to create interface one need to open corresponding character device first, i.e. /dev/tapX (or /dev/tunX). yip; NB, I think we should concentrate on tun0 anyway, since device tun is in GENERIC, whilst tap0 is a hack of mine ... Arno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Polishing touch
Hello, just in case re@ or a maintainer finds this worhtwhile : from my /etc/rc.conf : ifconfig_tap0=lladdr 00:90:27:3f:12:9f apm_enable=YES apmd_enable=YES This gives me in dmesg-a (today's CVS) : 1) Setting hostname: M. module_register: module if_tap already exists! Module if_tap failed to register: 17 can't re-use a leaf (if_tap_debug)! tap0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:90:27:3f:12:9f bit I just compiled if_tap into my kernel, and I nowehere asked explicitly for kldloading if_tap (IIRC) 2) NFS access cache time=2 Starting usbd. Starting apm. Starting apm. Starting apmd. I somehow twice get 'Starting apm' ; voila, Arno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Polishing touch
On Sunday 01 June 2003 18:45, [EMAIL PROTECTED] wrote: Hello, Hi Arno just in case re@ or a maintainer finds this worhtwhile : 1) Setting hostname: M. module_register: module if_tap already exists! Module if_tap failed to register: 17 can't re-use a leaf (if_tap_debug)! tap0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:90:27:3f:12:9f bit I just compiled if_tap into my kernel, and I nowehere asked explicitly for kldloading if_tap (IIRC) I don't exactly know why it tries to load if_tap when it is already present, but FreeBSD should not allow it to be double-linked into the kernel. I created a patch that (hopefully ;) disallows this. You can find it at : http://hobbes.bsd-dk.dk/~npp/kern_linker.patch I would appreciate if you have the time to test this to see if it aborts the loading correctly. I know it's not exactly the real fix but it should stop some panics. Could you also test if unloading the if_tap module panic's the system ? This should ofcourse be tested without my patch and preferably when a tap device is in use. voila, Arno Best regards, Nicolai Petri catpipe Systems ApS Ps. If any commiter reads this and would help getting this into the tree please let me know. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Polishing touch
On Sunday 01 June 2003 18:45, [EMAIL PROTECTED] wrote: module_register: module if_tap already exists! Module if_tap failed to register: 17 can't re-use a leaf (if_tap_debug)! FWIW, same thing happens for if_tun. -- | Michael Nottebrock| KDE on FreeBSD | ,ww | | [EMAIL PROTECTED] | --- | ,wWWCybaWW_) | | --- | http://freebsd.kde.org | free `WSheepW'| | http://tigress.com/lofi | --- | node II II | pgp0.pgp Description: signature
Re: Polishing touch
Hello, just in case re@ or a maintainer finds this worhtwhile : from my /etc/rc.conf : ifconfig_tap0=lladdr 00:90:27:3f:12:9f apm_enable=YES apmd_enable=YES This gives me in dmesg-a (today's CVS) : 1) Setting hostname: M. module_register: module if_tap already exists! Module if_tap failed to register: 17 can't re-use a leaf (if_tap_debug)! tap0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:90:27:3f:12:9f bit I just compiled if_tap into my kernel, and I nowehere asked explicitly for kldloading if_tap (IIRC) here what is (probably) going on. when system starts up you have no tap0 interface. ifconfig(8) can not find tap0 interface and tries to kldload(8) if_tap(4) module. since you already have if_tap(4) compiled into the kernel you get these messages. now the thing about tap(4) (and tun(4)) interfaces is that they are *virtual*, i.e. in order to create interface one need to open corresponding character device first, i.e. /dev/tapX (or /dev/tunX). i'm not sure why do you need to ifconfig tap0 interface in system startup script. the application that *uses* tap0 interface is supposed to do that. thanks, max __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Polishing touch
module_register: module if_tap already exists! Module if_tap failed to register: 17 can't re-use a leaf (if_tap_debug)! tap0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 ether 00:90:27:3f:12:9f bit I just compiled if_tap into my kernel, and I nowehere asked explicitly for kldloading if_tap (IIRC) I don't exactly know why it tries to load if_tap when it is already present, but FreeBSD should not allow it to be double-linked into the kernel. I created a patch that (hopefully ;) disallows this. You can find it at : http://hobbes.bsd-dk.dk/~npp/kern_linker.patch I would appreciate if you have the time to test this to see if it aborts the loading correctly. I know it's not exactly the real fix but it should stop some panics. more or less : Setting hostname: M. linker_file_register_modules: Cannot load module if_tap.ko. linker_file_register_modules: Module if_tap is already loaded. linker_load_file: register_modules_failed linker_file_register_modules: Cannot load module if_tap.ko. linker_file_register_modules: Module if_tap is already loaded. linker_load_file: register_modules_failed tap0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 Could you also test if unloading the if_tap module panic's the system ? This should ofcourse be tested without my patch and preferably when a tap device is in use. no more panic. thanx, Arno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
