Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Hi, I'm using Fedora Core 3 and installed a slmodem-2.9.10_netodragon driver for a Neto Dragon modem. The Problem is every time I boot, if I want to connect to internet, I must execute "/sbin/modprobe slamr", "/usr/sbin/slmodemd/slamr0" and "ln -s /dev/ttySL0 /dev/modem" (I always create the simbolic link and it always disappears when I boot). My question is how can I make all this process automatic, so I don't have to do it all the time I boot? Thanks in advance.
Hi, thanks for your help. I edited /etc/rc.d/rc.local and I rebooted to test it, but I had no results. When booting I saw "/usr/sbin/slmodemd /dev/slamr0" command and an error message, but the screen changed inmediatly, and I couldn't read the message. The lines I added to rc.local are:
I would eliminate the & as it's really unnecessary when loading at boot-time. If you execute these commands normally and they run, then running them from your rc.local at boot-time should work just fine.
I am confused as to why the symbolic link is dissappearing at boot. I'm also confused by you saying:
...I must execute "/sbin/modprobe slamr", "/usr/sbin/slmodemd/slamr0" and "ln -s /dev/ttySL0 /dev/modem" (I always create the simbolic link and it always disappears when I boot).
But then you say you've added the following lines to your rc.local:
"/usr/sbin/slmodemd/slamr0" shows that "slmodemd" is clearly a directory.
but you've issued "/usr/sbin/slmodemd /dev/slamr0 &" in your rc.local which shows that "slmodemd" is not a directory, but an executable binary.
Could you please clarify why it is that you've put this in your rc.local file or if this was a typo or what?
I'll try to help where I can.
Last edited by zr0gravity; 02-04-2005 at 12:04 PM.
The output of modprobe was a blank page (no errors, it seems). The output of slmodemd was the following:
error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
error: cannot setup device `/dev/slamr0'
The weird thing is that when I su and do it manually after boot, it does work. Besides, after editing rc.local I don't have to execute "/sbin/modprobe slamr" after boot, just the slmodemd command. By the way, there's a space between " /usr/sbin/slmodemd" and "/dev/slamr0"