Dear All,
A change was made to the DHCP Server wiki page changing the domain suffix from pluto.disney.org on the basis that it is not correct and it has been replaced by localdomain.
If the user had obtained the domain pluto.disney.org or had a Dynamic Dns to a domain from the DDNS provider then you might not want localdomain as the Domain Suffix.
The bigger problem for me is that then the screenshot has been replaced with the following change and this comes from prior to Core Update 154 as it is missing the Deny Known Clients checkbox which is then talked about later in the existing text but no longer shown in the screenshot.
I logged in to the wiki and tried to restore the change back with a comment about the domain name and the missing Deny Known Clients checkbox but I received a
Error 403 oops, something went wrong
message. I tried three times and each time the same message.
Could someone who has the permissions restore that wiki page back to the version where the screenshot has the Deny Known Clients checkbox.
If it is agreed that the Domain Suffix shouldn't have been something like pluto.disney.org but should be localdomain or the earlier domain suffix from sept 2021 which was schuh-tv.at then let me know.
I will then create a new screenshot of the dhcp page with the Deny Known Clients checkbox and whatever appropriate wording is required for the Domain Suffix entry.
Regards, Adolf.
On 28/05/2023 15:19, IPFire Project wrote:
Hey,
the wiki page has been changed by Trash Trash. Check out the current version at https://wiki.ipfire.org/configuration/network/dhcp.
Old screenshot was wrong, at "Domain name suffix" pluto.disney.org is not the suffix.
You can see what has changed here:
https://wiki.ipfire.org/configuration/network/dhcp?action=diff&a=2023-05...
+++
@@ -10,7 +10,7 @@
## Example configuration In this example we will configure a standard IPFire installation to serve an internal network for the **<span style="color:green">Green Interface</span>**. - +
### Blue Interface Enabled If the Blue Interface has been enabled ensure that the MAC Filtering has been configured on the [Blue Access](/configuration/firewall/accesstoblue) page.