a while ago, I wrote about a problem I was having with a proxy server setup. I had two networks 192.168.1.0 and 192.168.2.0 joined by a router. The proxy server was 192.168.1.1 and though I could ping, telnet on both networks to the other, the proxy server would only work on the 1.0 network.
It turns out that for a SOCKS 4 client to work it must be able to resolve DNS names, the machines on the 1.0 network could get to the DNS servers through a gateway to the net. But the machines on the 2.0 network could not get to the DNS server. My solution was to install a caching DNS server on the network and point all machines to it. Now both networks can use the proxy server with no problem.
I hope this helps someone with a similar problem.
Bill
Original Letter--------------------------------------------------------------------------------------------------------
Hello again,
I have a problem. I have two networks 192.168.1.0
and 192.168.2.0,
they have a router joining them. What I want to do is put a proxy
server on one network (192.168.1.0) and have machines on both networks
have access to the Internet.
Can anyone tell me which proxy server to use. I've
tried using SOCKS
and it lets the machines on the 192.168.1.0 network communicate with
the
internet, but machines on the other network do not get out. I get
messages like:
Sep 30 14:09:26 debian sockd[5075]: Error in socks_GetDst: No such file
or directory; from host 192.168.2.2
Sep 30 14:10:07 debian sockd[5076]: connected -- Connect from
SSL(unknown)@192.168.2.2 to debian.bermudez (1080)
Sep 30 14:10:07 debian sockd[5077]: error -- wrong version (0x47) from
host debian.bermudez.
Sep 30 14:10:07 debian sockd[5076]: terminated -- Connect from
SSL(unknown)@192.168.2.2 to debian.bermudez (1080).
Sep 30 14:10:07 debian sockd[5076]: 414 bytes from 192.168.2.2, 0 bytes
from debian.bermudez
However I can ping and telnet from network to the other. The 192.168.1.0
network can get mail and all other net services I need but nada from
the
192.168.2.0 network.
Socks route file - router are at x.x.x.13
# routes for sockd
#
# IP of interface destination netmask for destination
# eg: 10.0.0.254 10.0.0.28 255.255.255.255
#new lines
192.168.1.1 192.168.2.13 255.255.255.255
192.168.1.13 192.168.2.13 255.255.255.0
#original line added first
192.168.1.1 0.0.0.0 0.0.0.0
Socks conf file
# Replace 'my.domain' below with your own domain name before using.
# Make sure you retain the leading period.
#deny ALL 0.0.0.0 .my.domain 0.0.0.0
#permit my.domain 0.0.0.0 ALL 0.0.0.0
permit ?=n 192.168.0.0 255.255.0.0 ALL 0.0.0.0
Thanks all
Bill
ps I think that route file looks fishy
