Responding to option 161 requests in heterogeneous byod-allowed network
jw354 at cornell.edu
Fri Feb 6 18:23:35 UTC 2015
Anyone have experience to share supporting thin clients with option 161
responses throughout a heterogeneous net? Is there a useful way to
the response to current and future thin client models that use it
in its current sense?
We've always used classes to target these sorts of functions to
clients but in googling option 161, I've found very little about what
are doing. Obviously something both specific to the relevant thin
and unlikely to be used for anything else is what would have some value.
Cornell University IT
More information about the dhcp-users