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.
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.
The 169.254 address range is used for some kind of intermediary step to the internet. The Speedtouch modem may always tell the computer that its ip address is in the 169.254 range because that range isn't used for the internet or for LANs, so it shouldn't conflict with anything.
That's just a guess. I don't know anything about those modems or much about the 169.254 addresses.
The range of 169.254.x.x has been reserved for this purpose. The idea is
that when DHCP fails, it still gives clients a way to communicate with
TCP/IP. It is, off course, not intended to production use, but it will give
the client a chance to use TCP/IP in order to recover. For example, on a
widely switched Ethernet backbone, it could enable the user to at least
e-mail MIS saying that their network connection is flaky.
But I'm not using DHCP, all my IP's are static.
One more thing, I cant delete it from the routing table.
NET not found is replied when i try to "route del 169.254.0.0", maybe I'm doing something wrong, but....
Well I'm not sure about the DHCP causing the route entry and subsequent address, but I have encountered it many times when I would configure an adapter for DHCP, but it failed to get an address so instead it would use the 169.254.0.0
Distribution: Just about anything... so long as it is Debain based.
APIPA is what the 169.254 address scheme is. Automatic Private IP Addressing is what it stands for. Micro$oft uses it to address a NIC when DHCP fails. It's kind of becoming a standard though not and RFC, at least not one I'm aware of.
There is no problem with it being in your routing table, it will not affect your IP routing.