Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Hi , I'm running Slackware 9.1 and I'm using webmin 1.150 . I found that I cannot ping my ip address (192.168.0.1) or my host name. Then I opened webmin in mozilla and saw that under networking/network configuration/network interfaces that only lo (loopback) was active although Under "interfaces activated at boot time" it says eth0 (Ethernet) and lo (loopback)
This PC isn't connected to a network.
How do I test if my network card works? , Why isn't eth0 active ? How can I fix this problem?
Slackware 10.2 uses dhcpcd during boot to resolve network configurations, I don't know if this is the case with 9.1.
The thing with dhcpcd is that if it cannot aquire the configurations from the DHCP server within a time period (if it times out), it will bring the interface down for which it was ran. This is why you do not see eth0 up after boot, given that its not connected to a network.
Why is the loopback device not enough if you are not connected to a network?
Having an extra, essentially useless driver loaded will only waste memory.
But if you must have eth0 up, run:
modprobe <DRIVER_MODULE_FOR_YOUR_CARD> # Usually this step can be skipped
ifconfig eth0 up
ifconfig eth0 inet 10.0.0.1
eth0 now has the IP of 10.0.0.1 and should respond at that address (given that no firewalls running and route was automatically added - usually the case)
To bring eth0 down, run:
ifconfig eth0 down
/etc/rc.d/rc.inet1.conf (in Slackware 10.2 at least) has the boot-time configuration settings for eth0. You may modify it to make the start up script assign a static IP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.