This is a discussion on Slackware 10.0 and module init tools within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi all, after the upgrade to my workstation I did last month, yesterday I upgraded my home network server ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi all, after the upgrade to my workstation I did last month, yesterday I upgraded my home network server to Slackware 10.0. Since the workstation upgrade I found that the tun module wouldn't load automatically but I didn't really use it except for some testing and I did some heavy changes to modules.conf, so I didn't pay to attention to it. On the contrary my server has an application that uses tun as an interface acting as my default route and starts a dialup connection to my ISP when it sees packets to the outside world. This time I had to pay more attention because the usual access to /dev/net/tun wouldn't cause modprobe to load tun and my application couldn't work. I did some investigation and found nothing has changed in the application, in the kernel and in the startup sequence. I just went back to the module-init-tools of Slackware 9.1 (module-init-tools-0.9.14) and everythingh went back to normal. Anybody had the same problem with tun (or any other module) and can give a hint to a solution? Ciao Giovanni -- A computer is like an air conditioner, it stops working when you open Windows. Registered Linux user #337974 <http://counter.li.org/> |