Passing DHCP option 160 to end users

[mortaaay]

Hi All, I am having an issue of passing option 160 to end users on our network connected end points for our Software Phone (SIP) configuration. I have tried DHCP from our AD DHCP server which works without issue on local endpoint, but does not seem to pass through to VPN. I have tried DHCP via the Pulse Secure device - vast majority of IP scope is given, all seems to work except option 160. Have attempted with Pulse Secure Client - Which always says DHCP is disabled on the endpoint even though the endpoint gets address. Have attempted with Net-Connect Client - Which does not pass option 160 either but does say DHCP is enabled. Thanks for you replies.

[[email protected] · Accepted solution]

@mortaaay Unsupported use case. VPN server being acting as a relay agent, would only pass the IP address, netmask (if it's the same range as the internal port), DNS & WINS (configurable option).

In an advanced context, we can pass options to the DHCP server from the VPN server (DHCP relay) as part of the DHCP Discover, however the otherway (DHCP server >> DHCP relay >> DHCP client) is not supported.