SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Network Interface problem: Sony Vaio VPCEG2DXF Running -13.37/x86_64 (3.2.7 kernel)
When this laptop is at a wifi hot spot and wicd is run, the eth0 interface is not brought down so all packets try using that interface without a cable. I have the problem isolated and need help in fixing the issue.
To understand the problem requires comparison with a working portable, my Dell Latitude E5410. When the Dell boots with no ethernet cable attached 'route -n' shows eth0 UP but not running with the static IP address of my office network.
Note that dhcpcd forks to the background and ntpd listens on wlan0 before deleting eth0.
The problem with the Sony is that ntpd is not called. After dhcpcd forks to the background, nothing happens. Both the Sony and the Dell run the same Slackware and wicd versions and the .conf files are the same. Because eth0 is still in the kernel routing table packets try to go over that interface rather than the wlan0 interface that's connected to the WAP.
What might cause the process to stop on the Sony while completing on the Dell?
I found this to work very early in the process of fixing the problem. It's not practical because I won't give root privileges to the user; it needs to be automated somehow, if that's possible.
More important is the question of why the Sony won't invoke ntpd to bring down eth0 after dhcpcd establishes a connection to the WAP while the Dell does. They both run the same distribution version, the same wicd version, and the only difference is the kernel (default in the Dell and 3.2.7 in the Sony to provide the ethernet driver for the newer network chip.
ifplugd <- 'ifplugd is a Linux daemon which will automatically configure your Ethernet device when a cable is plugged in and automatically un-configure it if the cable is pulled. This is useful on laptops with on-board network adapters, since it will only configure the interface when a cable is really connected. ifplugd interfaces with your distribution's native network configuration utilities.'
The above link and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!
onebuck: I installed ifplugd but found it worked only when the system booted with an ethernet cable attached. Then it would bring down eth0 when the cable was removed and bring up eth0 when the cable was re-inserted. If the system booted with no attached cable eth0 came up, along with wlan0. I probably need to look more closely at man ifplug and see if I missed something critical.
lazardo: I will look at /etc/wicd/scripts/ and see how to use the pre- and post- scripts to address the issue.
Thanks, both of you. I'll post what I learn from both suggestions.