public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: Testing required for modified dhcp.cgi file related to bug 10743
Date: Mon, 16 Nov 2020 14:00:57 +0100	[thread overview]
Message-ID: <trinity-1fb9dead-1239-4f7c-bfc4-8b9f1375857d-1605531657523@3c-app-gmx-bap20> (raw)
In-Reply-To: <a1fa200b-cbe4-d1eb-e65e-008a3477aa10@gmail.com>

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

Hi,

just another thing I noticed in testing your .cgi.
The definitions for DNS server etc. should be outside the pool definition. They should be used by the fixed leases also.

Regards,
Bernhard

> Gesendet: Samstag, 14. November 2020 um 23:13 Uhr
> Von: "Adolf Belka" <ahb.ipfire(a)gmail.com>
> An: "Matthias Fischer" <matthias.fischer(a)ipfire.org>, "IPFire: Development-List" <development(a)lists.ipfire.org>
> Betreff: Re: Testing required for modified dhcp.cgi file related to bug 10743
>
> Hi Matthias,
>
> I have added your feedback into bugzilla.
>
> After I read your input and looked at my changes I had one of those
> "Duh, that's so obvious, why on earth did I do that"
> moments. I know the error I made and I have a reasonable idea of how I can fix it.
>
> Will send out a diff once I have made and tested the changes.
> Thanks very much for the help, much appreciated.
>
> Regards,
> Adolf.
>
>
> On 14/11/2020 17:26, Matthias Fischer wrote:
> > Hi,
> >
> > Tested - sorry, didn't work - 'dhcp' wouldn't start. Perhaps my fault. I
> > have suspected something like this for my machine.
> >
> > /var/log/messages tells me:
> >
> > ...
> > Nov 14 16:36:27 ipfire dhcpd: /etc/dhcp/dhcpd.conf line 16: Pool
> > declaration with no address range.
> > Nov 14 16:36:27 ipfire dhcpd:      }
> > Nov 14 16:36:27 ipfire dhcpd:       ^
> > Nov 14 16:36:27 ipfire dhcpd: Pool declarations must always contain at least
> > Nov 14 16:36:27 ipfire dhcpd: one range statement.
> > Nov 14 16:36:27 ipfire dhcpd: /etc/dhcp/dhcpd.conf line 30: Pool
> > declaration with no address range.
> > Nov 14 16:36:27 ipfire dhcpd:      }
> > Nov 14 16:36:27 ipfire dhcpd:       ^
> > Nov 14 16:36:27 ipfire dhcpd: Pool declarations must always contain at least
> > Nov 14 16:36:27 ipfire dhcpd: one range statement.
> > Nov 14 16:36:27 ipfire dhcpd: Configuration file errors encountered --
> > exiting
> > ...
> >
> > And...yes... [Hrm!]...I'm running 'dhcpd' on GREEN and BLUE with NO
> > address pools. Only fixed leases.
> >
> > Anything I can do to test this without address ranges?
> >
> > Best,
> > Matthias
> >
> > On 14.11.2020 13:29, Adolf Belka wrote:
> >> Hi all,
> >>
> >> I created a modified dhcp.cgi file for bug 10743. This gives the opportunity to add deny unknown-clients or deny known-clients to the dhcpd.conf file for the green and blue subnets.
> >>
> >> Unfortunately one of the bug originators has decided to move away from IPFire and will not carry out any testing of this modification to confirm it works before I create a patch and submit it.
> >>
> >> The modification provides a radio button set to green and blue that offers:-
> >>
> >> allow all clients
> >> deny unknown-clients
> >> deny known-clients
> >>
> >> The allow all clients option gives the same setup as currently and is the default setting for the radio button set.
> >>
> >> The modified dhcp.cgi file is attached. I would appreciate it if you could test this out and let me know if there are any unexpected outcomes.
> >>
> >> Regards,
> >>
> >> Adolf.
> >>
> >
>

  reply	other threads:[~2020-11-16 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 12:29 Adolf Belka
2020-11-14 16:26 ` Matthias Fischer
2020-11-14 16:40   ` Adolf Belka
2020-11-14 22:13   ` Adolf Belka
2020-11-16 13:00     ` Bernhard Bitsch [this message]
2020-11-16 13:14     ` Adolf Belka
2020-11-17  2:56       ` Tom Rymes
2020-11-18 11:39         ` Adolf Belka

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=trinity-1fb9dead-1239-4f7c-bfc4-8b9f1375857d-1605531657523@3c-app-gmx-bap20 \
    --to=bernhard.bitsch@gmx.de \
    --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