\begin{Ian Ward}
> > \begin{Ian Ward}
> > > I have VTUN operating between three servers, it works great.
> > > It needs the tun.o module loaded. Unfortunately, it does not do this
> > > itself.
> > if you run vtund without the tun.o module loaded, are there any
> > "can't find module xxx" modprobe/kerneld messages in the logs?
>
> Yep your right. This would seem the best approach. I get the following in
> the log:
>
> Apr 8 23:01:33 mail vtund[17395]: VTUN server ver 2.4 04/08/2001 (stand)
> Apr 8 23:02:11 mail vtund[17397]: Session m2s[61.9.136.175:1129] opened
> Apr 8 23:02:11 mail modprobe: modprobe: Can't locate module char-major-90
> Apr 8 23:02:11 mail last message repeated 2 times
> Apr 8 23:02:11 mail vtund[17397]: Can't allocate tun device. No such file
> or directory(2)
> Apr 8 23:02:11 mail vtund[17397]: Session m2s closed
>
> So I presume I need to add char-major-90 in with depmod ????? could it be
> that I just need to do a depmod -a and reboot (the system has not been
> rebooted since compiling and installing the tun package?
ahh, thats easy then. i hadn't realised it uses a character device.
all you need to do is add the line:
alias char-major-90 tun
to /etc/modules.conf (aka /etc/conf.modules if you have such a
thing). iirc, you don't even need to SIGHUP kerneld.
most modules are hooked in in this way. a generic name is looked up -
by character or block major number or network protocol family (and a
few other numbering schemes) - and then aliased to the specific module
that needs loading.
(if its a debian box, you'll want to create a file in /etc/modutils
with the above line and then run update-modules. then file a bug
against the vtund package for not doing so itself)
--
- Gus
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
