Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1358174 - dhcpd reports client as unknown when on wrong subnet
Summary: dhcpd reports client as unknown when on wrong subnet
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dhcp
Version: 7.4
Hardware: All
OS: Mac OS
low
low
Target Milestone: rc
: ---
Assignee: Pavel Zhukov
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 1339857 1348355
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2016-07-20 08:53 UTC by Pavel Šimerda (pavlix)
Modified: 2017-11-01 11:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1348355
Environment:
Last Closed: 2017-11-01 11:14:22 UTC


Attachments (Terms of Use)

Comment 6 Pavel Zhukov 2017-11-01 11:14:22 UTC
dhcp-4.2.5-58.el7.x86_64

config [1].
Host 192.168.174.1/192.168.175.1 is a router/dhcrelay. client2 is in 174 network, server and client1 are in 175 network.

Nov 01 12:09:08 server.example.com dhcpd[10683]: DHCPREQUEST for 192.168.174.100 from 52:54:00:64:43:e3 (client2) via 192.168.175.1: wrong network.



[1]
authoritative;

update-static-leases on;
use-host-decl-names on;

ignore bootp;
option domain-name    "example.com";

subnet 192.168.175.0 netmask 255.255.255.0 {
  allow client-updates;
  allow unknown-clients;
  ddns-updates on;
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.175.255;
  option routers 192.168.175.1;
  option domain-name-servers 192.168.175.1;

  pool {
    max-lease-time 10; # 1 minute
    range 192.168.175.100 192.168.175.128;
  }

}
subnet 192.168.174.0 netmask 255.255.255.0 {
  allow client-updates;
  allow unknown-clients;
  ddns-updates on;
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.174.255;
  option routers 192.168.174.1;
  option domain-name-servers 192.168.174.1;

  pool {
    max-lease-time 10; # 1 minute
    range 192.168.174.100 192.168.174.128;
  }

}
    host vm01 {
        hardware ethernet 52:54:00:64:43:e3;
        fixed-address 192.168.175.3;
        option host-name "client2.example.com";
        option subnet-mask 255.255.255.0;
    }


Note You need to log in before you can comment on or make changes to this bug.