Re: How does dhcp(d) choose an IP address?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Todd Zullinger wrote:
> Are you sure that there isn't another dhcp server running on the
> network?  Have you checked in /var/log/messages for dhcp logs from the
> time the ip was assigned to your laptop?

Thanks for the suggestion.
I see that the first mention of this address is on the laptop:
-----------------------------
Oct 12 16:29:43 elizabeth avahi-daemon[2454]: Network interface enumeration
completed.
Oct 12 16:29:44 elizabeth avahi-daemon[2454]: Registering new address record
for 192.168.2.101 on eth0.IPv4.
Oct 12 16:29:45 elizabeth avahi-daemon[2454]: Registering HINFO record with
values 'I686'/'LINUX'.
-----------------------------
So it seems that avahi chose this address, for some reason.

As far as I can see, once an address like this is given,
and a dhcp lease is assigned,
it is very difficult to lose the address.

>> I should say that WiFi works perfectly well with this wrong address.
>> But it has made me realize that I am very hazy about how dhcp works,
>> and how exactly dhcpd determines the addresses it will give out.  Is
>> there a reasonably clear account of this anywhere?
> 
> Maybe the DHCP FAQ will be useful?
> 
> http://www.dhcp-handbook.com/dhcp_faq.html

I'll study that.
Thanks for the pointer.

> I have my dhcp server give out specific addresses to some systems
> based on the mac address and that's worked well for me.

This has always worked perfectly for me, until now.

>> I saw incidentally that something or someone (I assume a yum update)
>> had moved /etc/dhclient.conf to dhclient.conf.bak
...
>> just leaving what looked like a fairly useless dhclient.conf.sample
>> , confirming my view that the people who write sample files for
>> Fedora are somewhat lacking in common sense.
> 
> If you're sure of that, please find out what overwrote the file and
> file a bug report.  Just taking stabs in the dark and saying someone
> else is lacking in common sense doesn't do anything to get real
> problems fixed. :-)

It happened last month, so I guess it was a dhcp update.
It isn't really important.

The sample file in question (don't know if everyone has it)
is absurdly complicated, as if the writer wanted to include
every option possible.

A sample file, in my view, should be a minimal working example.





-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux