11 Matching Annotations
  1. Sep 2021
    1. And the latter (DHCP server) is great because it means that all machines connecting to your router will now have their DNS requests routed through your Pi-Hole.
  2. Jun 2021
    1. When a router sends an RA with ‘O’ bit set, but does not set the ‘M’ bit, the client can do Stateless Address Autoconfiguration (SLAAC) to obtain its IPv6 address, and use DHCPv6 for obtaining additional information. (An example of additional information is DNS). This mechanism is well known as Stateless DHCPv6, because the DHCPv6 server does not need to keep track of the client address bindings.

      Explained how SLAAC works.

    1. Currently there are two option spaces defined for the DHCPv4 daemon: “dhcp4” (for the top-level DHCPv4 options) and “vendor-encapsulated-options-space”, which is empty by default but in which options can be defined.

      How about the option spaces for DHCPv6?

  3. datatracker.ietf.org datatracker.ietf.org
    1. local physical subnet

      how does the client know this "local physical subnet"?

    2. DHCP messages from a client to a server are sent to the 'DHCP server' port (67), and DHCP messages from a server to a client are sent to the 'DHCP client' port (68).

      DHCPv4 Ports of Server and Client

  4. datatracker.ietf.org datatracker.ietf.org
    1. Clients listen for DHCP messages on UDP port 546. Servers and relay agents listen for DHCP messages on UDP port 547.

      DHCPv6 Server and Client Ports.

    1. local physical subnet

      how is this physical subnet is defined or decided? for example, my docker container inet address of eth0 is How 172.17.0 is defined?

    1. Using Kea #1 - DHCP Fundamentals - Carsten Strotmann

      This series is very helpful to understand Kea and DHCP.

  5. Dec 2015
    1. operating frequencies, output power, modulation types or other radio frequency parameters

      Mitigation: IMHO, this section should be split into two, one stating the mission, and one suggesting mitigations in a "not limited to" format.

      In particular, I'd welcome mitigations such as

      • "For devices receiving their geographical location from a network service such as DHCP, the device shall used the specified country as the default location for which to set operating frequencies, output power, modulation types or other radio frequency parameters that are country-specific." and

      • "For all devices using location information to set RF parameters, the purchaser/operator shall be provided with a way of changing the location to the United States.

      • "For all devices where the location is not known, the device shall default to a constructed set of RF parameters that will be legal in at least the United States, and preferably in any country.