4 ms·

In this specific case, the DHCP server configuration under Windows makes it abundantly clear though that you need to make your DHCP server authoritative by addi

by pilif 9y ago

In this specific case, the DHCP server configuration under Windows makes it abundantly clear though that you need to make your DHCP server authoritative by adding a warning icon and presenting a warning dialog when it's not running in authoritative mode. Making it authoritative is then to just press a button in that dialog. Yes. You have to know that you have to open the GUI for DHCP server configuration in order to configure the DHCP server, but that's really all you need to know to prevent the issue described here. isc-dhcpd that's often used under linux doesn't even warn to syslog when it's not authoritative. All indication for doing so is given in the sample config file using # network, the authoritative directive should be uncommented. #authoritative; It doesn't however explain to you why you should or shouldn't do that and, again, it starts up just fine without this uncommented. Case in point: Back when I was learning about all of this my Windows-based DHCP servers were all authoritative, whereas none of my Linux or FreeBSD based DHCP servers were.

ntnn 9y ago
From when and which distro is that default config file? I remember having a text next to it saying 'Enable this, if this is the only DHCP server on this network' or something along the lines of that with a pointer to the documentation for an explanation.
- tolien 9y ago
  The current isc-dhcp-server package in Debian testing has that comment, although there’s a line missing… # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. From that, it’s a little more clear that you should be uncommenting that option.
dspillett 9y ago
> the DHCP server configuration under Windows Though for the opening to the current discussion that is a moot point - this is not relevant to either OS on the desktop.
- johncolanduoni 9y ago
  Neither Windows nor Linux desktops buck the trends (with respect to documentation and user expectations) that their server counterparts follow.
  - _jal 9y ago
    And dump truck gearing patterns are kind of similar to manual transmission car patterns. Complaints about the difficulty of driving a dump truck remains irrelevant to cars.
    - johncolanduoni 9y ago
      "Kind of similar" is very different from "arranged by the same people following the same processes with many packages being identical". We're talking about comparing transmissions from the same manufacturers with a lot of shared parts.

by pilif 9y ago

ntnn 9y ago

From when and which distro is that default config file? I remember having a text next to it saying 'Enable this, if this is the only DHCP server on this network' or something along the lines of that with a pointer to the documentation for an explanation.

tolien 9y ago
The current isc-dhcp-server package in Debian testing has that comment, although there’s a line missing… # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. From that, it’s a little more clear that you should be uncommenting that option.

dspillett 9y ago

> the DHCP server configuration under Windows Though for the opening to the current discussion that is a moot point - this is not relevant to either OS on the desktop.

johncolanduoni 9y ago
Neither Windows nor Linux desktops buck the trends (with respect to documentation and user expectations) that their server counterparts follow.
- _jal 9y ago
  And dump truck gearing patterns are kind of similar to manual transmission car patterns. Complaints about the difficulty of driving a dump truck remains irrelevant to cars.
  - johncolanduoni 9y ago
    "Kind of similar" is very different from "arranged by the same people following the same processes with many packages being identical". We're talking about comparing transmissions from the same manufacturers with a lot of shared parts.