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.
I noticed that every time I connect to the company network I get a new fresh IP address from our dhcp server.
I am the only mepis user in the lab, and the only machine that has this behavior is my pc ...
my sysadmin noticed that the dhcp server offered me my old address but my client has refused it and that's why I got a new one every time.
Does anyone knows what may be wrong ?
I am running promepis 2005.b4 fully updated with apt-get till today (kernel 2.6.10, kde 3.3.2 ...).
Netwroking is ethernet 100, no wireless.
Originally posted by Brian Knoblauch Sounds like a security feature rather than a "bug"/problem. Is there some particular reason why this is not acceptable?
it's annoying that other machines can't rely on mine having a constant IP.
well the sysadmin now grabbed my mac address and has overcome the problem by force, still I'd like to understand what setting is wring so that I may be able to fix things gracefully
I understand some objections on the usefulness of keeping the IP
still, the lease settings normally allow anyone to get a random IP *the first time* they conect to a netwrok,
and then on they typically keep getting the same one day after day.
why am I different ;-) ?
I think it must be some client setting but so far no-one has come up with an answer, and my sysadmin has tied one IP to my MAC address - it just wasn't necessary with the other clients.