Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
uname -a
Linux server 2.6.18-028stab067.4 #1 SMP Thu Jan 14 17:06:11 MSK 2010 x86_64 x86_64 x86_64 GNU/Linux
What version of RedHat are you using? And what 'tun' do you mean? The "Tun" emulator? Or the one for bridging? Asking a complete question with useful information, will get you help faster.
I've done a bit of netsearching and it seems that CentOS 5.4 by default has a tun loadable module so it's surprising that /sbin/modprobe tun doesn't work, doesn't find the tun.ko file. Let's see if it exists. Please try
For logon shells it is normally done in /etc/profile, for root at least.
In a script you can use export PATH="$PATH:/sbin".
You may also want /usr/local/sbin and /usr/sbin.
I'm not sure of the usefulness of the links regards getting tun support into the kernel which is your current stumbling block. I confess to not reading the big one past the second page but there was no mention of having to do anything special to do so. This confirms the earlier research that suggested tun support is there by default. Has the kernel been rebuilt since installation? Clearly tun.ko is not present and the fix for that is to build a new kernel -- or reinstall to get it back to default which I believe includes it.
The part that begins with if [ "$EUID" = "0" ]; then adds the sbin directories when running as root; they're not much use for other users because the commands in the sbin directories mostly need to be run as root. If you still want them for a non-root user then better to do it on a per-user basis rather than system-wide so better set PATH in ~/.bash_profile for login shells and ~/.bashrc for non-login shells.
Linux is designed so you can build a new kernel without erasing anything and choose between old and new kernels at boot time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.