Generally, since this is also handled by nf, the access file, the modifier field is set to 0.0.0.0. This entry has the same three fields as in nf, identifier, address and modifier. There are three entries:ĭeny tells SOCKS when to reject a request. Of course you do not need SOCKS to talk to yourself. It defines 127.0.0.1, the loopback, automatically. It has a direct connection in via Ethernet. For instance, in our network, 192.168.1.3 will not need to use socks to talk with 192.168.1.1, firewall. The routing file is there to tell the SOCKS clients when to use socks and when not to. I say "poorly named" because it is so close to the name of the access file that it is easy to get the two confused. The routing file in SOCKS is poorly named "nf". Not all systems support ident, including Trumpet Winsock, so I will not go into it here. Specific users can also be granted or denied access. All 0's is the norm because it is easy to type. With a modifier of 0.0.0.0, the IP address field does not matter. Notice the first "0.0.0.0" in the deny line. To allow everyone in the domain 192.168.1.xxx, the lines: So, first permit every address you want to permit, and then deny the rest. One should not have the line:Īs this will permit every address, regardless. Will permit every number within group 192.168.1.0 through 192.168.1.255, the whole C Class domain. It will permit only the IP address that matches every bit in 192.168.1.23, eg, only 192.168.1.3. If the bit is a 1, the corresponding bit of the address that it is checking must match the corresponding bit in the IP address field. Envision this number to be 32 bits (1s or 0s). The address modifier is also a typical IP address four byte number.
The IP address holds a four byte address in typical IP dot notation. You should have both a permit and a deny line. With socks4.2 Beta, the access file is called "nf".It should contain 2 lines, a permit and a deny line. The DOS and, presumably, Macintosh computers will do their own routing. The routing file should be housed on every UNIX machine. The access file should be housed on the server. One to tell the access allowed, and one to route the requests to the appropriate proxy server. The SOCKS program needs two separate configuration files. To tell the server to run when requested. Socks stream tcp nowait nobody /usr/local/etc/sockd sockd One important thing to note is that the proxy server needs to be added to /etc/nf. Make sure that your Makefiles are correct.
PROXIE SOCKS HOW TO
Uncompressed and untar the files into a directory on your system, and follow the instructions on how to make it. Firewall and Proxy Server HOWTO: The SOCKS Proxy Server Next Previous Contents
0 kommentar(er)
