)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000002,"name":"Gert Doering","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"b170cd5c6289e85de7fa7aeb5ec94d09d0c75b1e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cb6a73d3_2d41a281","updated":"2025-07-30 18:04:15.000000000","message":"This plays together with the code in tun.c that checks whether or not the TAP driver needs to be informed about DHCP options\n\n```\n    /* user-supplied DHCP options capability */\n    if (tt-\u003eoptions.dhcp_options)\n    {\n..\n            if (!DeviceIoControl(tt-\u003ehand, TAP_WIN_IOCTL_CONFIG_DHCP_SET_OPT,\n..\n```\n\n... so if we no longer flag these \"it can be done with DHCP or not\" options as \"well, if we have DHCP, we should set them!\" (DHCP_OPTIONS_DHCP_OPTIONAL), and we have no \"this can only be done with DHCP!\" options (DHCP_OPTIONS_DHCP_REQUIRED), then tun.c just assumes \"well, nothing required, nothing to set up\" and DNS will not work.\n\nI experienced the issue myself with 2.7_alpha2 and a setup that ended up using TAP and DHCP, and the explanation makes sense.","commit_id":"27dd365ad8c2db0c3e0b214d8c30077bb3856356"}]}
