DISCOVERs from "unkown network segment" - suppress log messages?

[Simon]

Christina Siegenthaler <tina at ieu.uzh.ch> wrote:

> Since I know that the rogue client is supposed to get a fixed IP address (and which one), I added a pool to that subnet declaration containing just this one IP, plus a host declaration for the rogue client with a „fixed-address“ statement giving it the fixed IP it’s supposed to get from the other DHCP server, plus, just to be safe, an "ignore booting" statement as well.
> 
> 
> Looks like this:
> 
> 
> ####################
> # Ignore these
> ####################
> 
> subnet 10.65.xx.0 netmask 255.255.254.0 {
>        pool { range 10.65.xx.61 10.65.xx.61;
>                ignore booting; }
> }
> 
> host ignore_me_1 { hardware ethernet 00:07:32:xx:xx:xx; ignore booting; fixed-address 10.65.xx.61; }

Being pedantic, you don’t need the pool - and in the general case, you should NOT have any fixed-address assignment which is also in any pool. If you do, then it’s entirely possible to hand out the address dynamically to one client, and also via the host declaration to another - causing some “interesting” effects in the network.

This should be sufficient :
subnet 10.65.xx.0 netmask 255.255.254.0 {
  ignore booting;
}
host ignore_me_1 { hardware ethernet 00:07:32:xx:xx:xx; ignore booting; fixed-address 10.65.xx.61; }


Simon