Support for vendor options is currently broken in MS dhcp provider:
- Vendor options have to be created before they can be assigned
values. We create vendor classes if they don’t exist, but don’t do the
same for options. - A lesser problem is the way we name vendor classes in MS dhcp
differs from how we do the same in isc dhcp, it’s possible to end up
with multiple vendor classes representing the same set of vendor
options.
Both of these can be fixed, but how important is support for
sun-specific vendor options, esp. in Windows environments? I haven’t
seen complains regarding issue #1, which probably means that vendor
options can be dropped altogether on Windows.
Thoughts or concerns?
Cheers,
-Dmitri