No subnet declaration; Can't open /var/lib/dhcp/dhcpd.leases for append

[Bill Shirley]

This is all kinds of confusing.  You're configuring DHCP on a machine
named 'yellow' who's address is 10.1.1.2 and has a gateway of 10.1.1.1.
Yet 'yellow' has a WAN connection?

You've configured DHCP for subnet 10.1.1.0/24 which is on interface
'enp4s5' which IS NOT UP.  Can you ping anything on the LAN?

Is 'yellow' the internet gateway?

Also your DHCP configuration:
        host yellow {
             hardware ethernet f0:7d:24:c2:c4:13;
             fixed-address 10.1.1.1;
         }
^^You're defining 'yellow' (which is the DHCP server!!) and it has a
different address that the one you defined in /etc/network/interfaces!!
iface enp4s5 inet static
     address 10.1.1.2/24

Don't define host 'yellow' in the DHCP configuration.  Add a comment if
you like.

You need to figure out which 10.1.1.0/24 address 'yellow' is supposed to
have and bring up interface 'enp4s5'.

Is 'yellow' the gateway for 10.1.1.0/24?  Your 'option routers 10.1.1.1'
says it's not.

Bill

On 1/27/2018 5:57 AM, Simon Hobson wrote:
> A <publicface at bak.rr.com> wrote:
>
>>> Also in your first post:
>>> subnet 10.1.1.0 netmask 255.255.255.0 {
>>>          interface wlp2s0;
>>>          option domain-name-servers 10.1.1.1;
>>>          max-lease-time 7200;
>>>          default-lease-time 600;
>>>          range 10.1.1.10 10.1.1.250;
>>>          option subnet-mask 255.255.255.0;
>>>          option broadcast-address 10.1.1.255;
>>>          option routers 10.1.1.1;
>>>
>>> As far as I know there is no interface directive.  Plus wlp2s0 is the wrong
>>> interface.  You should remove that line.
>>   Wrong name for the device?  Or just shouldn't be the wireless interface?  Why is it wrong?
> There is no instruction in dhcpd.conf called "interface". The example you found probably had it as a comment to help the person keep track of what is where.
>
>> If that's not how to specify the interface for that subnet, then what is the proper way please?
> You don't ! It happens automagically, and bear in mind that a subnet served by a DHCP server does NOT have to be directly connected - it can come via a relay agent.
> The server uses the IP address(es) of the interface for directly connected clients, or the Gateway Interface Address (GIAddr) field inserted by a relay agent if the client is remote (the other side of a router). That address is used to determine which subnet a client is connected to.
>
>
>>> What does 'ip -4 -o addr' show?
>>>
>> # ip -4 -o addr
>> 1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
>> 3: enp6s0    inet xx.xx.xx.xx/20 brd 255.255.255.255 scope global enp6s0\       valid_lft forever preferred_lft forever
> OK, you do not have IPv4 addresses on any internal interface ! it isn't going to work like that. Or have you deleted lines from that output thinking they aren't relevant ?
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20180127/e4ba0ee9/attachment.html>