public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [IPFire Wiki] Page Changed: DHCP Server
Date: Mon, 29 May 2023 16:05:25 +0200	[thread overview]
Message-ID: <030314e3-3857-74d3-5ba0-e9a2721fe22a@ipfire.org> (raw)
In-Reply-To: <41aca374-a649-6129-073b-40446d3b02f9@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2712 bytes --]

Hi Adolf,

I restored "Screenshot_2022-01-31_18-19-50.png".

Best,
Matthias

On 29.05.2023 13:28, Adolf Belka wrote:
> 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-14T20:50:38.214499&b=2023-05-28T13:19:20.085084
>> 
>> ---
>> 
>> +++
>> 
>> @@ -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>**.
>> -![](./Screenshot_2022-01-31_18-19-50.png)
>> +![](./IPFire DHCP settings.png)
>>   
>>   ### 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.
>> 
> 


      reply	other threads:[~2023-05-29 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168527996017.155897.4963012508556784867.ipfire@ipfire.org>
2023-05-29 11:28 ` Adolf Belka
2023-05-29 14:05   ` Matthias Fischer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=030314e3-3857-74d3-5ba0-e9a2721fe22a@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox