riven1128
asked on
Socks5 interface binding issue using Dante on Debian
Background:
I have a VPN connection set up on debian using ppptp, the interface is ppp0 and I've tested it, it works fine.
I am trying to set up a socks5 proxy to listen on eth1 and go out ppp0, this way I can optionally browse via that VPN connection if I wish to from anywhere on the network.
With that having been said.. I tried tsocks but I didn't see any method for routing that socks proxy out ppp0.
I installed Dante and it looks like it has exactly what I need, there is an internal parameter that I have set to eth1, and an external parameter that has been set to ppp0 but no matter what I do, when I launch the proxy and connect it still routes traffic through eth0 which is my standard internet connection.
I'm running debian and dante v1.1.19, which is the latest debian version.. The dante config is attached, and there's nothing unusual in the dante log files.. no errors
So the questions I have:
1. Am I doing something wrong?
2. Is this a bug in the dante version that comes with debian?
3. Is there an alternative socks5 proxy for debian that will accomplish this interface binding?
The only thing I want to make sure I can do as well is have DNS look ups routed through the VPN as well.. I know Socks supports this.
Thanks!
I have a VPN connection set up on debian using ppptp, the interface is ppp0 and I've tested it, it works fine.
I am trying to set up a socks5 proxy to listen on eth1 and go out ppp0, this way I can optionally browse via that VPN connection if I wish to from anywhere on the network.
With that having been said.. I tried tsocks but I didn't see any method for routing that socks proxy out ppp0.
I installed Dante and it looks like it has exactly what I need, there is an internal parameter that I have set to eth1, and an external parameter that has been set to ppp0 but no matter what I do, when I launch the proxy and connect it still routes traffic through eth0 which is my standard internet connection.
I'm running debian and dante v1.1.19, which is the latest debian version.. The dante config is attached, and there's nothing unusual in the dante log files.. no errors
So the questions I have:
1. Am I doing something wrong?
2. Is this a bug in the dante version that comes with debian?
3. Is there an alternative socks5 proxy for debian that will accomplish this interface binding?
The only thing I want to make sure I can do as well is have DNS look ups routed through the VPN as well.. I know Socks supports this.
Thanks!
logoutput: stderr /var/log/danted.log
internal: eth1 port = 1080
external: ppp0
method: username none
user.privileged: root
user.libwrap: proxy
user.notprivileged: nobody
extension: bind
client pass {
from: 192.168.0.124/0 port 1-65535 to: 0.0.0.0/0
}
pass {
from: 192.168.0.0/24 to: 0.0.0.0/0
command: bind
log: connect error
}
pass {
from: 192.168.0.0/24 to: 0.0.0.0/0
protocol: tcp udp
}
client block {
from: 0.0.0.0/0 to: 0.0.0.0/0
log: connect error
}
block {
from: 0.0.0.0/0 to: 127.0.0.0/8
log: connect error
}
block {
from: 0.0.0.0/0 to: 172.16.0.0/12
log: connect error
}
block {
from: 0.0.0.0/0 to: 0.0.0.0/0
command: bind
log: connect error
}
block {
from: 0.0.0.0/0 to: 0.0.0.0/0
log: connect error
}
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.