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.

Sometimes I have an issue wherein nm-applet will say I'm connected with a "self-assigned address" if I try to connect by the ethernet port on my laptop. In those cases, I am NOT connected to the Internet. Doesn't matter how many times I restart the "networking", "dbus", "dhcdbd", "network-manager", or "network-manager-dispatcher" services, or in what order, I cannot get the darn thing connected. The only way to get connected is to reboot and hope that it doesn't glitch out again. This leads me to believe it is a problem with my boot order.

Looking at my daemon.log, here is some boot-process output which I only ever see when it has glitched out:

Not seeing the problem, unless you're not expecting a (perfectly valid) 10.x address?

When you get that problem, try running

Code:

dhclient eth0

So you're saying that the problem might be somewhere else in the boot process?

I just copied a big block of text from the log file, I don't know if it's all from the same boot (but I think it is, it's contiguous.) I thought maybe the problem had something to do with this message:

Well, it happened again. Dhclient did get me connected to the Internet though, so that's good. NM-applet still shows the other icon, but no biggie.

This has happened with multiple ethernet LANs so I think it's a software issue with my laptop.

Naturally, I know that Sid isn't supposed to be stable, and I've had plenty of experience to back that assertion up. But that doesn't meen it can't be fixed.

Thanks for posting, THANKS FOR THE DHCLIENT TIP!

EDIT: Yeah, so my cable got jostled loose (don't you just hate it when the little locking tab breaks off?) And for the life of me it would not re-connect. I would run "sudo dhclient", it would say "bound to 192.168.1.xxx, renewing in three thousand-odd seconds," but I would not be connected.

The icon in NM-applet for "self-assigned address" is a cable with a little triangle-exclamation point on it. But when I tried to reconnect after jostling the cable loose, the nm-applet didnt even get past the "green balls" stage. Killing NM-applet didn't work. So I wound up needing to restart anyway.

Sorry if this rough description is, uh, rough, but NM-applet is kinda sparse on information about what it's actually doing.

The dhclient program still lets me connect once, which is still a major improvement under circumstances where the locking tab is NOT broken. So it's still very helpful! (Yeah, the WiFi network at my school has been taken down since last year. Some kid with a virus connected and things kinda went downhill from there...)