For When You Can't Have The Real Thing
[ start | index | login ]
start > Fedora > Workstation > 23 > DHCP Reservation Not Working

DHCP Reservation Not Working

Created by dave. Last edited by dave, 63 days ago. Viewed 1,330 times. #3
[diff] [history] [edit] [rdf]
labels
attachments

A: dhclient now supports RFC-4361!

(Please note that this is an answer to a question nobody asked.)

Q: My Fedora Core system won't pick up a DHCP lease reservation!

(Also: my dual-booting Fedora Core system won't pick up the same DHCP lease that the other OS on the same system does.)

A: By default, Fedora Core (21-22-23) use RFC-4361 to define host-IDs provided to DHCP servers. Most DHCP servers use this host-ID to decide what IP address they are going to give you. It is unfortunate for you that your DHCP server is not RFC-4361 compliant.

(Please note: by "most", we mean dhcp servers in the future. Windows servers as of 2K12R2 are not RFC-4361 compliant.)

Q: ???!!!

A: all right all right. You can force your dhclient to be non-compliant (ie compatible with everything else in the world) by adding:

send dhcp-client-identifier = hardware
...to the end of /etc/dhcp/dhclient.conf.

...but really what you should do is go into the future and use the undoubtedly-all-RFC-compliant DHCP servers that are running there rather than grubbing around here in the nasty present.

no comments | post comment

Virtual Dave Megaplex:

Internet Explorer 6 Users >>Click Here

(read this note about local search)

Logged in Users: (0)
… and 5 Guests.


Editing: snipsnap-help, Image Macro

(Et auditum est, et idcirco ego nunc simulare)

Installed 6 years and 218 days ago
Powered By >>SnipSnap Version 1.0b1-uttoxeter

This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.

Useful:


snipsnap.org | Copyright 2000-2002 Matthias L. Jugel and Stephan J. Schmidt