Network Address getting assigned to client and ping not working (ver 4.2.2)

[Peter Rathlev]

On Tue, 2012-04-24 at 16:55 +0200, Peter Rathlev wrote:
> You don't have to exclude those addresses. We have many networks larger
> than /24 (typically /22) and we have had no problems with hosts being
> assigned .0 og .255. These hosts include Avaya 1220 and 1140E phones and
> Windows XP clients. The DHCP server will not automatically exclude those
> addresses, at least not the ISC DHCPd.

Examples for these:

>From 10.104.0.0/22 we have an Avaya 1140E running firware "0625C7M":

lease 10.104.1.0 {
  starts 2 2012/04/24 14:21:07;
  ends 3 2012/04/25 02:21:07;
  tstp 5 2012/04/20 05:00:30;
  tsfp 3 2012/04/25 08:21:07;
  atsfp 3 2012/04/25 08:21:07;
  cltt 4 2012/04/19 11:00:30;
  binding state active;
  next binding state expired;
  hardware ethernet 3c:b1:5b:53:06:a8;
  set commit-vendor-class = "Nortel-i2004-A";
  client-hostname "T3CB15B5306A8";
}

>From 10.22.72.0/22 we have a Windows XP client:

lease 10.22.74.0 {
  starts 2 2012/04/24 09:45:03;
  ends 2 2012/04/24 21:45:03;
  tstp 1 2012/04/23 15:45:00;
  tsfp 3 2012/04/25 03:45:03;
  atsfp 3 2012/04/25 03:45:03;
  cltt 0 2012/04/22 21:45:00;
  binding state active;
  next binding state expired;
  hardware ethernet 00:21:6a:20:e4:fc;
  uid "\001\000!j \344\374";
  set commit-vendor-class = "MSFT 5.0";
  client-hostname "A70219";
}

Plenty of Android devices, Juniper/Trapeze access points (MP-82 and
MP-522) and Linux Ubuntu or Fedora hosts besides these have had no
problems.

-- 
Peter