SOCKS Proxy over DNS Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm 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
What initially awakened the Balrog?
Strange behavior of Object.defineProperty() in JavaScript
How did Fremen produce and carry enough thumpers to use Sandworms as de facto Ubers?
Why is it faster to reheat something than it is to cook it?
How long can equipment go unused before powering up runs the risk of damage?
What does Turing mean by this statement?
How to compare two different files line by line in unix?
Can a sorcerer use careful spell on himself?
How does the math work when buying airline miles?
Flash light on something
How to run automated tests after each commit?
The test team as an enemy of development? And how can this be avoided?
Intuitive explanation of the rank-nullity theorem
How do I find out the mythology and history of my Fortress?
Semigroups with no morphisms between them
Does the Mueller report show a conspiracy between Russia and the Trump Campaign?
The Nth Gryphon Number
Is multiple magic items in one inherently imbalanced?
Antipodal Land Area Calculation
In musical terms, what properties are varied by the human voice to produce different words / syllables?
How much damage would a cupful of neutron star matter do to the Earth?
Google .dev domain strangely redirects to https
What does it mean that physics no longer uses mechanical models to describe phenomena?
Maximum summed subsequences with non-adjacent items
SOCKS Proxy over DNS
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm 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;
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:
- User performs DNS request asking where is
example.com
- My DNS server responds "It is
<proxy-ip-address>
" - User then sends an HTTP/S request to the proxy's IP address, e.g.
GET /about.html HTTP/1.1
Host: example.com - 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
add a comment |
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:
- User performs DNS request asking where is
example.com
- My DNS server responds "It is
<proxy-ip-address>
" - User then sends an HTTP/S request to the proxy's IP address, e.g.
GET /about.html HTTP/1.1
Host: example.com - 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
add a comment |
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:
- User performs DNS request asking where is
example.com
- My DNS server responds "It is
<proxy-ip-address>
" - User then sends an HTTP/S request to the proxy's IP address, e.g.
GET /about.html HTTP/1.1
Host: example.com - 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
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:
- User performs DNS request asking where is
example.com
- My DNS server responds "It is
<proxy-ip-address>
" - User then sends an HTTP/S request to the proxy's IP address, e.g.
GET /about.html HTTP/1.1
Host: example.com - 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
iptables dnsmasq dante
asked Apr 14 at 6:34
omtinezomtinez
1133
1133
add a comment |
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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