A reliable socks4 server 1

[arlequin]

Hello...

I have a linux box acting as a http/proxy/smb/mail server and I want to add a socks4 server...
I've tried dante and nylon... I think I prefer the last one, because it's easier to configurate...
But when I run it from the command line

# /usr/local/bin/nylon -p 1080 -i eth0 -I eth1 -n 10 -f

I get the following message:

bind to address failed

I don't know what is this, I have three WinMe client PC running the MSN Messenger and I set up the SOCKS server to my linunx box IP and the port 1080, but sometimes the connection succeeds, sometimes it doesn't...

BTW, How can I set up the nylon command line to be ran in the sytstem start-up ? (I mean like squid or postfix...)

Thanks!! Arlequín
arlequin@montevideo.com.uy

http://www.arlequinadas.com

 

[ifincham]

Hi,

Not many people use SOCKS nowadays - can you not just use IP masquerading for the clients ? I believe most of the instant messaging stuff works with this although there may be some functionality that doesn't operate fully.

Incidentally, there is a Mandrake 'cooker' rpm of Dante --> ftp://rpmfind.net/linux/Mandrake-devel/contrib/RPMS/dante-1.1.11-0.3mdk.i586.rpm

On the start-up, if you don't want to create a sysv init script just put that one-liner into /etc/rc.d/rc.local .

Regards

 

[arlequin]

thanks, but I really prefer nylon,'cause it's easier to set up..

I only have problem with the 'bind' things... don't know what is it, and ICQ clients won't work :-(

How can I use IP masquerading, whatever... for the SOCKS clients? Arlequín
arlequin@montevideo.com.uy

http://www.arlequinadas.com

 

[ifincham]

Hi,



Bind is the 'Berkley Internet Name Daemon' (runs as 'named') and is 'the' dns server application thats probably runs on about 99% of all DNS servers throughout the internet. You don't need to get involved too much with that unless you wish to provide the name resolution for your domain(s) on your own system. Or did you mean bind in a different context - the word has other meanings..



IP masquerading is something similiar to proxying yet simpler because all the linux box does is alter the source address of a tcp packet to its own IP address (keeping a record), forwards it to the internet, then does the reverse when it gets a reply - i.e changes the destination address and forwards to the originating machine. Its all transparent to the client.



With Mandrake 8.1 (which I assume you are still using there) there is even a gui config within the control centre, i.e. 'internet connection sharing'. Mandrake 8.1 has a iptables based 'tiny' firewall and, I believe, the gui internet connection sharing just adds a masquerade to the firewall rules . If you want to try that config you first have to setup the tiny firewall iteself.



Otherwise, just put a couple of lines into your /etc/rc.d/rc.local file :



echo 1 >/proc/sys/net/ipv4/ip_forward

/sbin/modprobe ip_tables iptable_nat iptable_nat_ftp

/sbin/modprobe ip_conntrack ip_conntrack_ftp

/sbin/iptables -t nat -A POSTROUTING -o eth1 -s 10.0.0.0/8 -j MASQUERADE



(example where eth1 is the linux internet interface [change to whatever it actually is] and 10.0.0.0/8 is an example of a local lan subnet)



The clients just need :



(i) default gateway of linux box ip address

(ii) dns servers to be configured



Of course, if you are using dhcp thats easy to do via the dhcp lease.



Hope this helps

 

[arlequin]

ifincham

Thank you very much for the help!!
You are a great teacher !!

In fact, I know what 'bind' is, the named daemons....

I was talking about bind in the context of the SOCKS4 server nylon. The nylon man page

http://misc.eecs.umich.edu/cgi-bin/man2html?nylon+1

says that there are problems with binding and my ICQ running on a winME workstation can't connect thru nylon :-( Arlequín
arlequin@montevideo.com.uy

http://www.arlequinadas.com

 

[ifincham]

Hi,







Hmmmm ... thought as much after I wrote it. The bind you are talking about is the bind() library routine used in networked programs - see section 2 of the man pages : 'man 2 bind' . Also, you might be interested in the socks protocol write up here which explains how it works -->

http://www.socks.nec.com/protocol/socks4.protocol

On icq, did you follow the instructions here -->

http://www.icq.com/icqtour/firewall/socks4.html

Regards