How to : DHCP option tag 201 – proxy

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #105092
    Avatarjfaure
    Participant
    • Total Post: 16
    • Regular Joe
    • ★★

    Hello,

     

    I find in release note for 8.6_303 the information as the proxy could be set in DHCP option tag :

    Ability to define the Wyse Management Suite Proxy information using DHCP options or DNS SRV records. See, Configuring the proxy settings.
    => There are no information anywhere on the official documentation on how to use the DHCP option tag 201 to configure the proxy in the DHCP.

    Can someone helps? I figure by myself that the option is the 201 looking at the Wyse GUI (8.6_606), but I want to know the syntax and docs on how it’s work.

     

    Thanks.

    #105093
    Avatarjfaure
    Participant
    • Total Post: 16
    • Regular Joe
    • ★★

    Just to inform that using the GUI / Network Setup / SOCK5 proxy, this is working fine.

    But we would like that the proxy is set up directly on DHCP option tag, because when the wyse is on a public internet (ie, homeoffice) if this parameters is completed, the wyse can’t connect to the WMS SaaS (the proxy doesn’t exist anymore, but the wyse don’t try to not use it).

    Hope I am clear, and someone will have a solution.

    If not, I will open a case at Dell.

    Thanks.

     

    #105119
    Avatarjfaure
    Participant
    • Total Post: 16
    • Regular Joe
    • ★★

    I have the return of the Dell support.

    Here the extract :

    DHCP option 201 and/or DNS TXT record _THINOS_PROXY._tcp.domain.com is used to provide ThinOS 8.6 the ability to get proxy setting.

    The whole proxy configuration string should be in format below:
    proxy1;proxy2;proxy3|applist
    Each proxy is separated by a ‘;’ and the ‘|’ is used to separate proxy field from app list field.
    The app list MUST be specified, otherwise proxy setting will not be applied.

    Example of proxy setting string on DHCP/DNS server:
    https://HMJEJFIECMMLJOHEBKGBOENBOGPEFOBC:HMJEJFIECMMLJOHEBKGBOENBOGPEFOBC@proxy1.domain.com:111;socks5://HMJEJFIECMMLJOHEBKGBOENBOGPEFOBC:HMJEJFIECMMLJOHEBKGBOENBOGPEFOBC@proxy2.domain.com:222|WMS;FR;RTME [proxy1.domain.com]

    Each proxy server should be defined in the format below
    [protocol://][enc_user:enc_password@]proxy.domain.com[:port]

    Examples of proxy server defination:
    proxy.domain.com (no protocol specified, it will be treated as a global type, http/https/socks5 are using the same one).
    https://proxy.domain.com:8080 [eur03.safelinks.protection.outlook.com] (No username/password required)
    socks5://HMJEJFIECMMLJOHEBKGBOENBOGPEFOBC:HMJEJFIECMMLJOHEBKGBOENBOGPEFOBC@proxy.domain.com:1080 (both username and  password are encrypted with AES tool)
    http://user:pass@proxy [proxy]. domain.com:8080 (username/password in clear text is also supported)
    It may help someone.

    Thanks!

     

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.