hardware ethernet and option vendor-class-identifier
Sten Carlsen
stenc at s-carlsen.dk
Fri Oct 16 13:42:32 UTC 2015
It looks like you want to say that one particular host can only be
accepted if booted into windows but not when booted into linux?
Allow statements do not fit into a host declaration AFAIK.
You may consider having a class for windows and a class for linux, then
deny unknown hosts and allow the relevant class in each pool (one pool
for each class).
Then you can use subclass statements to select who is what based on
hardware.
On 16/10/2015 15:33, Patrick Trapp wrote:
> If you are specifying the fixed-address value based on the "hardware ethernet", why are you bothering with the class identifier. I would just specify that for a given hardware ethernet, assign a specific fixed address.
>
> Is there some circumstance when you think a given MAC address will qualify for different classes?
>
> ________________________________________
> From: dhcp-users-bounces at lists.isc.org [dhcp-users-bounces at lists.isc.org] on behalf of Rafal [golem at mtm-info.pl]
> Sent: Friday, October 16, 2015 7:32 AM
> To: dhcp-users at lists.isc.org
> Subject: hardware ethernet and option vendor-class-identifier
>
> Hello Dhcp-users,
>
> I want to make my dhcp server verify hardware and
> vendor-class-identifier to send reply.
>
> This is how I expected it :
>
>
> (not working example)
>
> ##########
> subnet 192.168.30.0 netmask 255.255.255.192 {
> option routers 192.168.30.1;
> }
>
> class "WINDOWS" {
> match if substring(option vendor-class-identifier, 0, 8) = "MSFT";
>
> }
>
> class "LINUX" {
> match if substring(option vendor-class-identifier, 0, 8) = "udhcp";
>
> }
>
> host windowspc {hardware ethernet 78:01:02:03:04:05; fixed-address 192.168.30.2; allow members of "WINDOWS";}
> host linuxpc {hardware ethernet 44:11:02:03:04:05; fixed-address 192.168.30.3; allow members of "LINUX";}
>
>
> #######
> So while dhcp server receive dhcp request, he checks hardware address and
> then vendor class identifier. If both match then he send reply.
>
> Allow members need to be defined inside pool however I need static
> IP configuration based on dhcp.
> My example doesn't work. Can anyone help me to make it working ?
>
> Thanks in advance.
>
>
> --
> Best regards,
> Ozga Rafal mailto:golem at mtm-info.pl
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20151016/1ac0bff4/attachment.html>
More information about the dhcp-users
mailing list