|
|
openvpn does NOT support the listing of numerical DHCP fields. That could easily be added, I guess. However, it all depends on which client you are using: I've read numerous reports that Windows clients simply do not honour DHCP option 119. Thus, it would be possible to add this option to the openvpn software but the handling of particular DHCP option is done by Windows, AFAIK. HTH, JJK Matt Clauson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Rob MacGregor wrote: > | I think the problem is that the DOMAIN option specifies the client's > | DNS domain, and it can only have one. You probably need to push the > | option specified in RFC3397, option 119. > | > | A quick Google for "dhcp option 119" turned up the following which may > help you: > | > | http://www.velocityreviews.com/forums/t42351-dhcp-attribute-119.html > | > http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2005q2/000231.html > > I was kind of thinking the same thing. However, the documentation for > OpenVPN is unclear as to whether you can push specific numbered options > as opposed to the keywords. Clarification? > > - --mec > ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2008-01/msg00083.html on line 210 Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2008-01/msg00083.html on line 210 |