*** From dhcp-server -- To unsubscribe, see the end of this message. ***

I've been running 3.0-alpha-19990424 successfully for about 24 hours
now, but I noticed a bunch of irritating log messages like this:

Apr 27 16:04:02 arachne dhcpd: DHCPREQUEST for 192.168.1.3 from 00:60:97:a4:35:91 via 
eth0: ignored.

What bothers me is that 192.168.1.3 is not in any of the subnets I
have declared, witness my attached dhcpd.conf file. I would therefore
have expected dhcpd to NAK it instead of ignoring it. Btw, old leases
from a previously used address pool which I declared "deny all clients"
are NAKed alright.

I noticed a new dhcpd.conf option "authoritative" specifying whether
the server should NAK requests for addresses it knows nothing about,
but if I read the man page correctly it is on by default.

-------- dhcpd.conf --------
# DHCP Konfiguration fuer Hausnetz Koeln
# Autor: Tilman Schmidt <[EMAIL PROTECTED]>
# Stand: 1999-04-26 17:30

server-name "arachne";
option domain-name "sema.de";
option domain-name-servers arachne.sema.de;
option non-local-source-routing off;
deny bootp;

class "ras-clients" {
  match if substring (option dhcp-client-identifier, 0, 5) = 01:52:41:53:20;
}

# LAN Koeln
shared-network SEMACGN-ETHER {
  # general adress range, DHCP assigned
  subnet 192.168.70.0 netmask 255.255.254.0 {
    option subnet-mask 255.255.254.0;
    option routers 192.168.70.2;
    option static-routes
        10.0.0.0        192.168.70.3,
        192.9.200.0     192.168.71.252,
        2.0.0.0         192.168.71.254;
    option ntp-servers 192.168.70.10, 192.168.70.2;

    use-host-decl-names on;

    pool {
      deny members of "ras-clients";
      range 192.168.70.101 192.168.70.254;
    # range 192.168.71.101 192.168.71.199;
    }

    # clean up spurious leases from switchover
    pool {
      range 192.168.71.101 192.168.71.199;
      deny all clients;
    }

    default-lease-time 604800;  # 1 week
    max-lease-time 7862400;     # 3 months

    host dsun3 {
      hardware ethernet 00:40:61:00:20:58;
      fixed-address 192.168.70.1;
    }

[... some more fixed-address host declarations ...]

    host veris {
      # hardware ethernet ??:??:??:??:??:??;
      fixed-address 192.168.70.38;
    }
  }

  # project adress range
  subnet 10.30.12.64 netmask 255.255.255.192 {
    option subnet-mask 255.255.255.192;
    option routers 10.30.12.125;
  }

  # jail for rogue RAS clients
  subnet 192.168.0.0 netmask 255.255.255.0 {
    option subnet-mask 255.255.255.0;
    pool {
      allow members of "ras-clients";
      range 192.168.0.1 192.168.0.254;
    }
  }
}

-- 
Tilman Schmidt          E-Mail: [EMAIL PROTECTED] (office)
Sema Group Koeln, Germany       [EMAIL PROTECTED] (private)
"newfs leaves the filesystem in a well known state (empty)."
                                                - Henrik Nordstrom



------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED]   Please try to use the web
page first - it will take a long time for your request to be processed by hand.

Archives for this mailing list are available at 
http://www.webnology.com/list-archives/dhcp/dhcp-server

------------------------------------------------------------------------------

Reply via email to