Francis Dupont writes: > yes, you either need a big "or" or to wait for the shared network feature (we > are discuting about it but it is in still in requirement/ early design phase > so won't be available soon).
Ok, this should still be doable. If not I know I could always look at the older ISC DHCP platform as well, we just started with Kea because it seemed to be recommended for newer deployments even though it isn't quite as fully featured yet. > equal is == (vs =) and the hexadecimal value of the option matches better a > hexadecimal litteral so it is more "option[55].hex == 0x0103072B". Yes I mistyped earlier with the single =. This was exactly right as "test": "option[55].hex == 0x0103060F1F212B2C2E2F79F9FC" matches a Windows machines. Unfortunately, it matches too much Microsoft stuff as they seem to use all of the same Vendor ID and Option 55 requests for everything they make now. I think at some point down the road we're going to have to look into something like Infoblox or another DDI solution that keeps and maintains a client classification database based on DHCP and Netflow so we can better identify some of these client types. > you can debug the classification evaluation. Thanks for the tip, that helped tremendously. Thanks, Jason Salmans _______________________________________________ Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
