This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
basic-static [2023/06/27 16:13] – [Configuring DHCP Reservations] -formatting hogwild | basic-static [2023/06/27 16:15] – [Security Limitations] -formatting-change to Head3 hogwild | ||
---|---|---|---|
Line 28: | Line 28: | ||
As mentioned earlier, DHCP Reservation offers the mapped IP address (and Hostname) to the MAC address you specified every time it offers a lease. DHCP Reservation does not prevent a different client from being configured with the same IP address. This is because DHCP Reservation only offers a static mapping to client devices which request a lease. If another device were self-configured with a (true) static IP, or if the router/DHCP were disabled, the other device could take that IP address. Similarly, if the first client for which DHCP Reservation were then self-configured with a static IP, it could claim a different IP address than the one in FreshTomato' | As mentioned earlier, DHCP Reservation offers the mapped IP address (and Hostname) to the MAC address you specified every time it offers a lease. DHCP Reservation does not prevent a different client from being configured with the same IP address. This is because DHCP Reservation only offers a static mapping to client devices which request a lease. If another device were self-configured with a (true) static IP, or if the router/DHCP were disabled, the other device could take that IP address. Similarly, if the first client for which DHCP Reservation were then self-configured with a static IP, it could claim a different IP address than the one in FreshTomato' | ||
- | Even if everything else were working properly, only DHCP lease //offers// are made static. The router' | + | Even if everything else were working properly, only DHCP lease //offers// are made static. The router' |
==== Inconsistent Terminology ==== | ==== Inconsistent Terminology ==== |