Problem with shared-network

robert at spotswood-computer.net robert at spotswood-computer.net
Fri Jun 5 15:39:30 UTC 2015


> On Thu, Jun 4, 2015 at 1:38 PM, <robert at spotswood-computer.net> wrote:
>
>> <aside>I use ignore rather than deny to keep my logs cleaner. Deny logs
>> every attempt. The ignore just ignores. And yes, I realize mac filtering
>> can be easily defeated by a knowledgeable opponent. A weak attempt at
>> security is not my purpose for using mac lists.</aside>
>>
>> I did not have pools. Now I do. Unfortunately, I still get the same
>> behavior. Just for kicks, I reversed the order of the subnets, and to my
>> surprise, still got the same behavior, except now the 192 subnet still
>> works. So the pools helped. This makes me believe the problem is the 10
>> subnet declaration.
>>
>> I removed the 192 subnet and the shared-network and just left the 10
>> subnet. When I attempted to restart the DHCP server, I got the no subnet
>> declaration for eth0 and it exited. Adding eth0:1 to both the command
>> line
>> and /etc/defaults/isc-dhcp-server did not change the result, only the
>> error message: "No subnet declaration for eth0:1 (No IPv4 addresses)"
>>
>> DHCP needs the 192 subnet to be defined.  It does not need to have a
> range, or any options, it can be an empty definition, but if it is not
> defined, it will ignore that interface.

<snip>

I agree that is the reason for the first error message (the eth0). But on
the second (before I removed the eth0:1 label), I specifically told the
server which interface (eth0:1, and not eth0), and it DOES have an IPv4
address. At the time (now changed), ONLY 10.111.111.1 was on eth0:1.



More information about the dhcp-users mailing list