Tunneling Through a Firewall

Matir · 09-20-2005, 01:29 PM

Then you should be able to start it with no problem. What indications are you seeing that it is not working or not running properly?

Jubalint · 09-20-2005, 01:37 PM

The program is installed and when I do "sockd -v" to check my config it checks out (it didn't a couple times when i had to fix my config, so I know it's working). However when I just put in "sockd" or "sockd -D" it doesn't start. I check with ps and grep and it's not there. Also when I try to start it with webmin it returns:
Start not successful
Error: 0, message: 256
Any ideas what that means?

And then if I go into my init.d and try to start dsocksify it says:
[root@localhost ~]# /etc/init.d/dsocksify
/etc/init.d/dsocksify: line 11: config:: command not found
Warning: your installation is faulty.
/etc/init.d/dsocksify: line 19: stop: command not found

Those are the indications. That's why I asked about if it's possible to do a total clean uninstall of dante. I oriignally tried to install it some time ago and felt I might have screwed something up then.

Matir · 09-20-2005, 01:48 PM

I've never seen dsocksify as the script, but I could be wrong.

Try:

Code:

sockd -D -f /etc/sockd.conf

where /etc/sockd.conf is your dante config.

Jubalint · 09-21-2005, 04:21 PM

Sorry for the late reply

.

This is what I get:

Code:

Sep 21 17:18:17 (1127337497) sockd[0]: socks_seteuid(): old: 0, new: 0
Sep 21 17:18:17 (1127337497) sockd[0]: socks_reseteuid(): current: 0, new: 0
Sep 21 17:18:17 (1127337497) sockd[0]: socks_seteuid(): old: 0, new: 0
Sep 21 17:18:17 (1127337497) sockd[0]: socks_reseteuid(): current: 0, new: 0
Sep 21 17:18:17 (1127337497) sockd[0]: fixsettings(): setting the unprivileged uid to 0 is not recommended
Sep 21 17:18:17 (1127337497) sockd[0]: fixsettings(): setting the libwrap uid to 0 is not recommended
Sep 21 17:18:17 (1127337497) sockd[26495]: serverinit(): bind(154.37.2.122.22): Address already in use (errno = 98)
Sep 21 17:18:17 (1127337497) sockd[26495]: sockdexit(): terminating

Matir · 09-22-2005, 12:55 PM

Something else already seems to be running on the socks port.

Jubalint · 09-23-2005, 06:47 PM

Code:

Sep 23 19:43:57 (1127519037) sockd[0]: socks_seteuid(): old: 0, new: 0
Sep 23 19:43:57 (1127519037) sockd[0]: socks_reseteuid(): current: 0, new: 0
Sep 23 19:43:57 (1127519037) sockd[0]: socks_seteuid(): old: 0, new: 0
Sep 23 19:43:57 (1127519037) sockd[0]: socks_reseteuid(): current: 0, new: 0
Sep 23 19:43:57 (1127519037) sockd[0]: fixsettings(): setting the unprivileged uid to 0 is not recommended
Sep 23 19:43:57 (1127519037) sockd[0]: fixsettings(): setting the libwrap uid to 0 is not recommended

I had one running, that's my own dumb fault. I get this when I turn it off.