Loading a module and making it start on boot?

Altiris · 08-02-2015, 12:57 PM

According to virt-manager on Slackbuilds, http://slackbuilds.org/repository/14.../virt-manager/ I should have the tun module loaded to avoid possible networking problems. Doing lsmod does not show tun at all, doing modprobe tun returns no errors. Is it loaded? I know /etc/rc.d/rc.modules loads the modules as boot but how do I make it so itll load the tun module at boot?

Emerson · 08-02-2015, 01:35 PM

You do not need to load tun unless you use it, and you do not.

chris.willing · 08-02-2015, 06:42 PM

Quote:

Originally Posted by Altiris

According to virt-manager on Slackbuilds, http://slackbuilds.org/repository/14.../virt-manager/ I should have the tun module loaded to avoid possible networking problems.

That's not exactly what it says -

Code:

If you have networking problems, make sure you have the tun module loaded.

i.e. don't bother with loading the tun module yourself unless you find you have a networking with your VM and the tun module hasn't already been loaded automagically. Even then, its not guaranteed to solve the network problem, rather its one thing to try.

Quote:

Originally Posted by Altiris

Doing lsmod does not show tun at all, doing modprobe tun returns no errors. Is it loaded?

Run lsmod again after the modprobe - it should be listed after you load it, not before.

Quote:

Originally Posted by Altiris

I know /etc/rc.d/rc.modules loads the modules as boot but how do I make it so itll load the tun module at boot?

Near the end of rc.modules, you could add:

Code:

/sbin/modprobe tun

However the file that rc.modules is a symbolic link to will be changed at the next kernel package update and your addition will be lost. It may be simpler to add that change to rc.local instead.

chris

Altiris · 08-02-2015, 08:49 PM

Quote:

Originally Posted by chris.willing

That's not exactly what it says -

Code:

If you have networking problems, make sure you have the tun module loaded.

i.e. don't bother with loading the tun module yourself unless you find you have a networking with your VM and the tun module hasn't already been loaded automagically. Even then, its not guaranteed to solve the network problem, rather its one thing to try.

Run lsmod again after the modprobe - it should be listed after you load it, not before.

Near the end of rc.modules, you could add:

Code:

/sbin/modprobe tun

However the file that rc.modules is a symbolic link to will be changed at the next kernel package update and your addition will be lost. It may be simpler to add that change to rc.local instead.

chris

That was really good. Thanks. I will use it without tun for now I guess and then set it up if I run into problems. At least I know how to do it in the event I need to. Thank you!