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.
can anyone help me with a slack 8 question? after running insmod tulip to install my nic driver, i do ifconfig eth0 192.168.0.1 and then dhcpcd -d eth0, but dhcpcd puts in syslog that it timed out waiting for DHCP server.. im using a linksys lne100tx fast ethernet card, and it is recognized at boot.. this method has worked for me before, but now it is not.. i haven't made any changes to any config files, except /etc/inetd.conf since it stopped working.. i don't understand.. any help?
Hmm.. It's weird, I got it to work that way yesterday, after messing with it a little, ifconfig eth0 up and dhcpcd worked.. but now its not.. I've tried cycling my modem also, no luck.. Thre reason I use insmod is basically the same as the reason you use modprobe.. its what I've always used.. Thanks for the help..
did you reboot? that would kill the driver and the daemon, and the ethernet device connection until you set everything up again (or automated it to start on boot). you can also use plain "ifconfig" to get the status of your ethernet interfaces. you should have an eth0 and a lo, both up.
once you have it figured out and working, add the modprobe to the /etc/rc.d/rc.modules file (using the format in the file, e.g., /sbin/modprobe tulip -- or whatever driver works) so it will load at boot and allow your interfaces to come up and get connected. if it worked once and you had a connection, i don't see why it wouldn't work again.
yea, i did reboot.. and i knew it would kill the connection and everything.. but i tried all that after i rebooted, exactly what you typed, and it still says it timed out waiting for a valid dhcp server response... i know its weird that it was working at one time, now its not.. i dont know what the deal is. i think im just going to format and install redhat 9..
I may be off in the wrong direction but.... I had a similar problem on Slack 9 with a linksys card. It just wouldn't hold its config. I simply ran the command netconfig and configured the card through Slack wizard type thingy. Worked solid ever since.