Well, it did not change anything :(
What is really strange is that "tun" is compiled in the kernel, but the module is started anyway ???
I had the same problem last year and solved it by removing
device tun from the kernel configuration file.
Yes, I though about it. But still, it is a strange bug and I cannot believe I (well, and you :) ) am the only one seeing this.
Thanks for the feedback....
Antoine
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
