SOCKS Proxy over DNS The 2019 Stack Overflow Developer Survey Results Are In ...

does high air pressure throw off wheel balance?

University's motivation for having tenure-track positions

Road tyres vs "Street" tyres for charity ride on MTB Tandem

Can the DM override racial traits?

Why use ultrasound for medical imaging?

Take groceries in checked luggage

How is simplicity better than precision and clarity in prose?

Does Parliament need to approve the new Brexit delay to 31 October 2019?

First use of “packing” as in carrying a gun

Do warforged have souls?

Typeface like Times New Roman but with "tied" percent sign

I'm thinking of a number

Is this wall load bearing? Blueprints and photos attached

Why is superheterodyning better than direct conversion?

Mortgage adviser recommends a longer term than necessary combined with overpayments

Who or what is the being for whom Being is a question for Heidegger?

Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?

Did God make two great lights or did He make the great light two?

What is this lever in Argentinian toilets?

Program that generates brainfuck code that outputs given text

"... to apply for a visa" or "... and applied for a visa"?

How to split app screen on my Mac?

What do you call a plan that's an alternative plan in case your initial plan fails?

How to test the equality of two Pearson correlation coefficients computed from the same sample?



SOCKS Proxy over DNS



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!iptables - quick safety eval & limit max conns over timeFirewall still blocking port 53 despite listing otherwise?Setting up dante socks serverOnly allow HTTP(S) and DNS using iptablesiptables port redirection on UbuntuUFW/IPTables: how to securely allow authenticated git access with githubUbuntu SOCKS proxy setup with two interfaces - how to pass DNSTrying to make iptables stateless is causing unforeseen filteringFirewall rules for ssh, ftp and webappsdebian kvm server with iptables is dropping bridge packets





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I'm trying to implement something similar to the service provided by https://www.smartdnsproxy.com, where clients only need to change their DNS settings to connect to a HTTP/S or SOCKS5 proxy. I think I understand the individual components, but I'm having trouble putting it all together.



To achieve what I want, I need to provide the following services to clients:




  • DNS server, I'm using dnsmasq

  • SOCKS proxy, I'm using Dante


Then, once a client has set the DNS to my server and a request is sent, the goal is for the following to happen:




  1. User performs DNS request asking where is example.com

  2. My DNS server responds "It is <proxy-ip-address>"

  3. User then sends an HTTP/S request to the proxy's IP address, e.g.

    GET /about.html HTTP/1.1
    Host: example.com


  4. Proxy server handles the incoming request (likely in port 80 or 443) and returns result to the client


I was able to setup both services, and they appear to work well independently. I have configured dnsmasq to resolve all domains with the proxy's IP address, and I can setup a client just fine. I have configured dante to listen to port 1080, and I can verify that a client can use the proxy, tested with the handy socksify tool.



Then, to forward the incoming requests from the HTTP/S ports to the proxy itself, I'm using the following IPTABLES rules:



#!/bin/bash
# Create new chain
iptables -t nat -N SOCKSPROXY

# Ignore LANs and some other reserved addresses.
iptables -t nat -A SOCKSPROXY -d 0.0.0.0/8 -j RETURN
iptables -t nat -A SOCKSPROXY -d 10.0.0.0/8 -j RETURN
iptables -t nat -A SOCKSPROXY -d 127.0.0.0/8 -j RETURN
iptables -t nat -A SOCKSPROXY -d 169.254.0.0/16 -j RETURN
iptables -t nat -A SOCKSPROXY -d 172.16.0.0/12 -j RETURN
iptables -t nat -A SOCKSPROXY -d 192.168.0.0/16 -j RETURN
iptables -t nat -A SOCKSPROXY -d 224.0.0.0/4 -j RETURN
iptables -t nat -A SOCKSPROXY -d 240.0.0.0/4 -j RETURN

# Anything else should be redirected to port 1080
iptables -t nat -A SOCKSPROXY -p tcp -j REDIRECT --to-ports 1080

# Any tcp connection made by our user should be redirected
iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner $USER -j SOCKSPROXY

# Accept all HTTP and HTTPS connections
iptables -A INPUT -p tcp -m multiport --dports 80,443 -j ACCEPT
iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -j ACCEPT


But I'm seeing connection refused errors. Is iptables the right approach to forward the incoming connections to the proxy server? If so, what am I missing?









share





























    0















    I'm trying to implement something similar to the service provided by https://www.smartdnsproxy.com, where clients only need to change their DNS settings to connect to a HTTP/S or SOCKS5 proxy. I think I understand the individual components, but I'm having trouble putting it all together.



    To achieve what I want, I need to provide the following services to clients:




    • DNS server, I'm using dnsmasq

    • SOCKS proxy, I'm using Dante


    Then, once a client has set the DNS to my server and a request is sent, the goal is for the following to happen:




    1. User performs DNS request asking where is example.com

    2. My DNS server responds "It is <proxy-ip-address>"

    3. User then sends an HTTP/S request to the proxy's IP address, e.g.

      GET /about.html HTTP/1.1
      Host: example.com


    4. Proxy server handles the incoming request (likely in port 80 or 443) and returns result to the client


    I was able to setup both services, and they appear to work well independently. I have configured dnsmasq to resolve all domains with the proxy's IP address, and I can setup a client just fine. I have configured dante to listen to port 1080, and I can verify that a client can use the proxy, tested with the handy socksify tool.



    Then, to forward the incoming requests from the HTTP/S ports to the proxy itself, I'm using the following IPTABLES rules:



    #!/bin/bash
    # Create new chain
    iptables -t nat -N SOCKSPROXY

    # Ignore LANs and some other reserved addresses.
    iptables -t nat -A SOCKSPROXY -d 0.0.0.0/8 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 10.0.0.0/8 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 127.0.0.0/8 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 169.254.0.0/16 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 172.16.0.0/12 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 192.168.0.0/16 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 224.0.0.0/4 -j RETURN
    iptables -t nat -A SOCKSPROXY -d 240.0.0.0/4 -j RETURN

    # Anything else should be redirected to port 1080
    iptables -t nat -A SOCKSPROXY -p tcp -j REDIRECT --to-ports 1080

    # Any tcp connection made by our user should be redirected
    iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner $USER -j SOCKSPROXY

    # Accept all HTTP and HTTPS connections
    iptables -A INPUT -p tcp -m multiport --dports 80,443 -j ACCEPT
    iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -j ACCEPT


    But I'm seeing connection refused errors. Is iptables the right approach to forward the incoming connections to the proxy server? If so, what am I missing?









    share

























      0












      0








      0








      I'm trying to implement something similar to the service provided by https://www.smartdnsproxy.com, where clients only need to change their DNS settings to connect to a HTTP/S or SOCKS5 proxy. I think I understand the individual components, but I'm having trouble putting it all together.



      To achieve what I want, I need to provide the following services to clients:




      • DNS server, I'm using dnsmasq

      • SOCKS proxy, I'm using Dante


      Then, once a client has set the DNS to my server and a request is sent, the goal is for the following to happen:




      1. User performs DNS request asking where is example.com

      2. My DNS server responds "It is <proxy-ip-address>"

      3. User then sends an HTTP/S request to the proxy's IP address, e.g.

        GET /about.html HTTP/1.1
        Host: example.com


      4. Proxy server handles the incoming request (likely in port 80 or 443) and returns result to the client


      I was able to setup both services, and they appear to work well independently. I have configured dnsmasq to resolve all domains with the proxy's IP address, and I can setup a client just fine. I have configured dante to listen to port 1080, and I can verify that a client can use the proxy, tested with the handy socksify tool.



      Then, to forward the incoming requests from the HTTP/S ports to the proxy itself, I'm using the following IPTABLES rules:



      #!/bin/bash
      # Create new chain
      iptables -t nat -N SOCKSPROXY

      # Ignore LANs and some other reserved addresses.
      iptables -t nat -A SOCKSPROXY -d 0.0.0.0/8 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 10.0.0.0/8 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 127.0.0.0/8 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 169.254.0.0/16 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 172.16.0.0/12 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 192.168.0.0/16 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 224.0.0.0/4 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 240.0.0.0/4 -j RETURN

      # Anything else should be redirected to port 1080
      iptables -t nat -A SOCKSPROXY -p tcp -j REDIRECT --to-ports 1080

      # Any tcp connection made by our user should be redirected
      iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner $USER -j SOCKSPROXY

      # Accept all HTTP and HTTPS connections
      iptables -A INPUT -p tcp -m multiport --dports 80,443 -j ACCEPT
      iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -j ACCEPT


      But I'm seeing connection refused errors. Is iptables the right approach to forward the incoming connections to the proxy server? If so, what am I missing?









      share














      I'm trying to implement something similar to the service provided by https://www.smartdnsproxy.com, where clients only need to change their DNS settings to connect to a HTTP/S or SOCKS5 proxy. I think I understand the individual components, but I'm having trouble putting it all together.



      To achieve what I want, I need to provide the following services to clients:




      • DNS server, I'm using dnsmasq

      • SOCKS proxy, I'm using Dante


      Then, once a client has set the DNS to my server and a request is sent, the goal is for the following to happen:




      1. User performs DNS request asking where is example.com

      2. My DNS server responds "It is <proxy-ip-address>"

      3. User then sends an HTTP/S request to the proxy's IP address, e.g.

        GET /about.html HTTP/1.1
        Host: example.com


      4. Proxy server handles the incoming request (likely in port 80 or 443) and returns result to the client


      I was able to setup both services, and they appear to work well independently. I have configured dnsmasq to resolve all domains with the proxy's IP address, and I can setup a client just fine. I have configured dante to listen to port 1080, and I can verify that a client can use the proxy, tested with the handy socksify tool.



      Then, to forward the incoming requests from the HTTP/S ports to the proxy itself, I'm using the following IPTABLES rules:



      #!/bin/bash
      # Create new chain
      iptables -t nat -N SOCKSPROXY

      # Ignore LANs and some other reserved addresses.
      iptables -t nat -A SOCKSPROXY -d 0.0.0.0/8 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 10.0.0.0/8 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 127.0.0.0/8 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 169.254.0.0/16 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 172.16.0.0/12 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 192.168.0.0/16 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 224.0.0.0/4 -j RETURN
      iptables -t nat -A SOCKSPROXY -d 240.0.0.0/4 -j RETURN

      # Anything else should be redirected to port 1080
      iptables -t nat -A SOCKSPROXY -p tcp -j REDIRECT --to-ports 1080

      # Any tcp connection made by our user should be redirected
      iptables -t nat -A OUTPUT -p tcp -m owner --uid-owner $USER -j SOCKSPROXY

      # Accept all HTTP and HTTPS connections
      iptables -A INPUT -p tcp -m multiport --dports 80,443 -j ACCEPT
      iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -j ACCEPT


      But I'm seeing connection refused errors. Is iptables the right approach to forward the incoming connections to the proxy server? If so, what am I missing?







      iptables dnsmasq dante





      share












      share










      share



      share










      asked 4 mins ago









      omtinezomtinez

      1083




      1083






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "2"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962961%2fsocks-proxy-over-dns%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962961%2fsocks-proxy-over-dns%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

          Список ссавців Італії Природоохоронні статуси | Список |...

          Українські прізвища Зміст Історичні відомості |...