Ah thank you I will be trying that. On Thu, Mar 11, 2010 at 5:48 PM, Martin Bochnig <mar...@martux.org> wrote:
> On Thu, Mar 11, 2010 at 6:39 PM, Antoine Benkemoun > <antoine.benkem...@gmail.com> wrote: > > Thank you for your help. > > > > Recompiling the driver from source fixed the problem. > > > > Antoine > > > Hello, > > next time you come into such trouble it should be enough, if you: > > > # update_drv -v tun > > (then hopefully it attaches again!) > > > > Rgds., > %martin > > > > > On Fri, Mar 5, 2010 at 11:55 AM, Giovanni Tirloni <gtirl...@sysdroid.com > > > > wrote: > >> > >> On Fri, Mar 5, 2010 at 6:32 AM, Antoine Benkemoun > >> <antoine.benkem...@gmail.com> wrote: > >>> > >>> Hello, > >>> > >>> I am new to OpenSolaris coming from a Linux background. I have really > >>> been enjoying OpenSolaris so far. I've almost always been able to find > my > >>> way out of different problems. This time I have got a seemingly harder > >>> problem. > >>> > >>> I have an OpenVPN installation that worked perfectly fine just > yesterday. > >>> This night my OpenSolaris Xen VM crashed and now OpenVPN doesn't work > >>> anymore. I fixed a few bugs that were due to relative/absolute paths > for > >>> certificates but I still have a bug concerning the tun module. > >>> > >>> When I start OpenVPN, I get the following message : > >>> > >>> Fri Mar 5 10:24:53 2010 Can't open /dev/tun: No such file or directory > >>> (errno=2) > >>> > >>> I have checked that the tun driver is loaded : > >>> > >>> ~# add_drv tun > >>> Driver (tun) is already installed. > >>> > >>> It shows up in /dev : > >>> > >>> ~# stat /dev/tun > >>> File: `/dev/tun' -> `../devices/pseudo/cl...@0:tun' > >>> > >>> The only problem is that the destination of the symbolic link does not > >>> exist. I have tried many things such as openvpn --mktun which is more > or > >>> less supposed to work on Linux but doesn't on OSol. I installed the tun > >>> package via the Blastwave utility pkgutil. > >>> > >>> Does anyone have any pointers for checking/correctly loading the the > tun > >>> module ? > >> > >> > >> Have you tried unloading and loading the tun driver again ? > >> > >> Were there any changes to the environment that a recompilation of the > >> driver would help ? > >> > >> This is how it looks here (b133, just compiled tun/tap driver): > >> > >> # ls -l /dev/tun > >> lrwxrwxrwx 1 root root 29 2010-03-05 07:50 /dev/tun -> > >> ../devices/pseudo/cl...@0:tun > >> > >> # ls -l /devices/pseudo/clo...@0:tun > >> crw------- 1 root sys 11, 292 2010-03-05 07:51 /devices/pseudo/cl...@0 > :tun > >> > >> # dmesg > >> [...] > >> Mar 5 07:50:52 osol-dev tun: [ID 654686 kern.notice] Universal TUN/TAP > >> device driver ver 1.1 03/05/2010 (C) 1999-2000 Maxim Krasnyansky > >> Mar 5 07:50:52 osol-dev pseudo: [ID 129642 kern.info] pseudo-device: > tun0 > >> Mar 5 07:50:52 osol-dev genunix: [ID 936769 kern.info] tun0 is > >> /pseudo/t...@0 > >> Mar 5 07:50:52 osol-dev tap: [ID 654686 kern.notice] Universal TUN/TAP > >> device driver ver 1.1 03/05/2010 (C) 1999-2000 Maxim Krasnyansky > >> Mar 5 07:50:52 osol-dev pseudo: [ID 129642 kern.info] pseudo-device: > tap0 > >> Mar 5 07:50:52 osol-dev genunix: [ID 936769 kern.info] tap0 is > >> /pseudo/t...@0 > >> > >> -- > >> Giovanni Tirloni > >> sysdroid.com > > > > > > _______________________________________________ > > opensolaris-discuss mailing list > > opensolaris-discuss@opensolaris.org > > >
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
