Questions[dante](server)

I have a Dante server on a host with multiple public ip addresses but it is unable to bind to the ips of the host. The ips are pingable, I have another service listening on each of them (different port) which works so I know the ips work. On my test server which has 10 public addresses it works with no issues but not on this one which has hundreds. The error:

debug: sockaddr2ifname(): address 138.xxx.93.2.51002 does not belong to interface

Here's my config:

logoutput: /dev/stdout
debug: 1

internal: 138.xxx.93.2 port = 51002
external 138.xxx.93.2

external.rotation: same-same

socksmethod: username none
clientmethod: none

user.privileged: root
user.notprivileged: nobody

client pass {
        from: 45.xxx.56.91/32 to: 138.xxx.93.2/32
        log: error
}

socks pass {
        from: 0/0 to: 0/0
        session.state.key: from
        session.state.max: 100
        session.state.throttle: 10/2
}

I setup a SOCKSv5 server (Dante) on Ubuntu with two ethernet interfaces:

• eth0 is connected to my WAN with a static routable IP
• eth1 is connected to my LAN with a private IP

I have a client connected on the LAN, and I'm able to ping the LAN port of the proxy using its IP address. However, I'm not able to resolve DNS names from that computer. The default gateway for my client points to the LAN of the proxy.

When I do a wireshark trace on the proxy, I see the DNS request coming in on eth1, but I don't see anything coming out of eth0. If I enable ip_forward on the proxy, then I see the DNS coming out of eth0 but the source iP is the private IP, which isn't routable. Is there any way for the proxy to handle DNS?

I just set up my dante socks proxy and it works just fine without authentication. Now I want only certain users to be able to use it tho. Preferably only those users that are in the passwd. What would you guys recommend me using? Can I somehow use PAM and link it to my passwd? What other authentication is there and how would they work? For example would an authentication window pop up, before the user would be able to browse?

I'm trying to set up a simple SOCKS proxy on Amazon EC2, but I'm not able to figure out the documentation and configuration file for dante. For now i've been able to set up a proxy without authentication (which i took offline immediately after verifying that it worked).

What i want to achieve is a single user proxy for myself with simple plaintext login. I assume i should use the username method in danted.conf but no matter what i try i cant figure it out.

Here is the current config without any authentication since i cant get it to work.

logoutput: /var/log/danted
internal: eth0 port = 1080
external: eth0
method: username none

user.privileged: root
user.notprivileged: nobody
user.libwrap: nobody
client pass {
    from: 0.0.0.0/0 port 1-65535 to: 0.0.0.0/0
}

pass {
     from:  0.0.0.0/0 to: 0.0.0.0/0
     protocol: tcp udp
}

I'm trying to set up a SOCKS proxy using dante for testing purposes. However, I can't even get it to work with a web browser, after looking at several tutorials on how to do that.

I've tried in both IE and Firefox, in both cases, using "Manual proxy configuration", leave everything blank except for SOCKS host, and then put in the IP of my proxy and the port number (1080). I just get "Server not found" / "Problems loading this page" and don't see anything in danted, even running in debug mode.

If I do a "telnet 10.0.0.40 1080" I do see the connection open in danted debug output, so I know that much is working.

Here's my config:

logoutput: stdout /var/log/danted/danted.log
internal: eth0 port = 1080
external: eth0
method: username none #rfc931

user.privileged: proxy
user.notprivileged: nobody
user.libwrap: nobody

connecttimeout: 30   # on a lan, this should be enough if method is "none".

client pass {
        from: 10.0.0.0/8 port 1-65535 to: 0.0.0.0/0
}

client pass {
        from: 127.0.0.0/8 port 1-65535 to: 0.0.0.0/0
}

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
}

pass {
        from: 10.0.0.0/8 to: 0.0.0.0/0
        protocol: tcp udp
}

pass {
        from: 127.0.0.0/8 to: 0.0.0.0/0
        protocol: tcp udp
}

block {
        from: 0.0.0.0/0 to: 0.0.0.0/0
        log: connect error
}

I'm sure I'm probably missing something simple, but I'm lost. I haven't even thought about SOCKS since the late 90's.