Big free us socks 5 and socks 4 list  

Автор allexe

75.30.115.38:51138
75.22.47.66:41352
75.212.7.91:57314
75.194.23.223:3572
75.192.104.224:3572
75.181.160.70:5335
75.176.186.144:64510
75.111.152.175:4285
75.10.33.44:53460
74.222.194.106:40467
74.131.135.181:40862
72.245.0.227:46822
72.241.176.63:57410
72.224.28.94:29349
72.185.226.250:50822
72.184.207.103:18951
71.84.236.108:31674
71.4.21.113:11921
71.234.20.223:54379
71.228.94.209:6343
71.206.81.186:27844
71.205.126.102:56956
71.203.231.251:34242
71.200.91.83:23581
...

12.180.54.219:1080
168.114.24.140:1080
209.10.181.175:1080
24.250.42.140:46605
38.113.24.205:1080
63.148.167.30:1080
66.142.208.3:1080
66.142.64.236:38535
66.163.36.35:1080
66.163.38.75:1080
66.163.38.79:1080
66.163.38.80:1080
67.151.147.66:1080
68.188.3.118:11737
69.204.235.17:51735
76.120.171.54:25552
99.161.154.161:14848
99.152.20.212:31217
99.147.109.182:7661
99.147.109.182:31217
99.141.9.192:49423
99.140.233.13:51471
99.140.224.231:51471
99.10.55.87:8988
98.240.111.226:48569
98.226.110.171:5763
98.224.193.189:28570
98.222.96.105:23263
98.221.56.125:53617
98.220.213.237:61504
98.218.215.79:51073
98.214.130.154:17099
98.207.248.178:47050
98.206.229.41:20649
98.206.17.138:629
98.206.113.140:28848
98.206.113.140:17472
98.206.113.140:10448
98.204.76.151:2286
98.204.185.243:46075
98.203.102.235:1024
98.198.192.164:9143
98.193.35.137:61131
97.96.49.224:18885
97.84.151.210:36259
97.82.241.15:51756
97.82.241.15:41744
97.81.72.152:16447
97.100.238.145:35179
96.25.26.2:34216
96.24.10.19:51177
96.18.2.51:20472
76.98.218.113:58842
76.89.96.32:26752
76.88.214.248:34555
76.28.73.89:9273
76.26.235.200:23651
76.25.12.141:45919
76.248.46.27:29522
76.244.7.23:49308
76.223.245.78:28249
76.212.185.249:63380
76.210.228.147:50554
76.21.129.220:9185
76.194.133.99:27317
76.187.142.189:36399
76.186.142.31:41695
76.18.250.91:36981
76.173.94.34:18971
76.121.145.124:3707
76.112.177.54:13801
76.112.134.177:3953
76.105.78.16:30156
76.104.80.67:34069
76.101.129.65:21422
76.100.48.72:164
75.72.95.244:49704
75.45.163.20:2841
75.30.115.38:51138
75.22.47.66:41352
75.212.7.91:57314
75.194.23.223:3572
75.192.104.224:3572
75.181.160.70:5335
75.176.186.144:64510
75.111.152.175:4285
75.10.33.44:53460
74.222.194.106:40467
74.131.135.181:40862
72.245.0.227:46822
72.241.176.63:57410
72.224.28.94:29349
72.185.226.250:50822
72.184.207.103:18951
71.84.236.108:31674
71.4.21.113:11921
71.234.20.223:54379
71.228.94.209:6343
71.206.81.186:27844
71.205.126.102:56956
71.203.231.251:34242
71.200.91.83:23581
71.199.138.110:38291
71.154.210.38:54613
71.113.139.209:38352
70.252.97.110:16726
70.251.186.36:42324
70.249.136.112:53888
70.243.222.64:49425
70.243.163.41:46159
70.173.57.211:4359
70.162.250.127:43559
70.160.14.164:26454
70.120.235.190:22903
70.115.221.220:14964
70.115.221.220:12764
69.76.49.234:14016
69.47.215.85:32921
69.254.223.231:33258
69.251.74.184:11387
69.245.183.157:25552
69.244.8.212:45261
69.230.63.114:23689
69.212.50.47:44600
69.202.90.26:28976
69.202.161.238:15461
69.180.51.152:29627
69.154.17.46:47981
69.142.176.137:28817
69.140.222.243:21177
69.133.78.246:12277
69.122.128.154:50314
69.121.68.144:47565
69.114.180.113:22223
69.113.228.109:55581
69.110.79.121:62674
68.73.147.248:36375
68.7.133.176:39719
68.63.8.248:41277
68.63.243.20:22167
68.61.47.170:31352
68.54.202.152:53643
68.52.92.166:24870
68.46.50.147:49006
68.45.201.118:16136
68.44.183.58:27038
68.44.155.167:28448
68.42.202.101:14648
68.41.98.230:60165
68.41.212.112:33319
68.41.212.112:23475
68.38.11.19:49974
68.33.98.239:20673
68.199.62.250:56275
68.197.240.89:11389
68.190.247.147:7009
68.189.147.31:6939
68.186.213.216:22721
68.13.237.120:6029
68.111.250.247:17737
68.111.228.55:25216
68.110.93.245:3715
68.109.205.63:53413
67.8.243.201:46216
67.189.72.39:9475
67.188.3.21:7591
67.185.245.120:36960
67.185.245.120:29900
67.185.187.235:64811
67.173.217.133:30135
67.171.229.37:44832
67.169.80.209:23563
67.163.166.202:49493
66.65.251.184:51895
66.56.32.245:61241
66.56.223.225:6667
66.30.98.134:64566
66.30.242.144:3837
66.182.239.159:35325
66.177.202.243:7883
66.176.19.174:10237
65.96.186.59:4208
64.170.211.130:36198
63.81.21.124:31336
4.224.207.211:40500
24.74.248.247:16467
24.62.77.52:56007
24.61.11.122:26873
24.58.61.206:10107
24.45.80.54:41502
24.45.168.72:32439
24.44.168.7:27345
24.254.24.144:11033
24.218.5.61:48962
24.218.171.240:13947
24.20.14.112:17235
24.161.201.104:6984
24.151.203.93:58397
24.131.63.168:58333
24.131.206.139:54454
24.130.211.159:53918
24.128.153.99:5538
24.128.121.71:39640
24.128.121.71:37800
24.127.147.184:16194
24.126.194.236:3912
24.12.98.205:41545
24.12.89.59:45549
24.118.54.115:45610
24.1.247.62:6965
24.0.73.147:23422
216.37.232.110:64749
216.254.68.198:42377
208.97.37.13:45499
208.65.8.69:21995
166.179.45.33:33878
12.206.127.100:23312
12.195.60.198:24769


Read more...

Socks Faq  

Автор allexe

Question List (Last updated Apr 7, 1998):
What is SOCKS?
How is SOCKS V5 different from SOCKS V4?
Is SOCKS V5 interoperable with SOCKS V4?
Where can I get SOCKS?
Are there any SOCKS related mailing lists?
Can I use SOCKS with Windows?
...

Question List (Last updated Apr 7, 1998):
What is SOCKS?
How is SOCKS V5 different from SOCKS V4?
Is SOCKS V5 interoperable with SOCKS V4?
Where can I get SOCKS?
Are there any SOCKS related mailing lists?
Can I use SOCKS with Windows?
Can I use SOCKS with a Mac?
What do I have to do to modify programs to use SOCKS?
Does SOCKS handle UDP?
How does SOCKS interact with DNS?
What is a single-homed and multi-homed firewall?
Is there an RFC for SOCKS?
What does SOCKS stand for?
Why does the password echo when I run rftp?
How do you traverse multiple firewalls (socksified SOCKS server?)
Why do I see "inetd[]: socks/tcp server failing (looping)" in my logs?
Can I use SOCKS with a OS/2?
What causes the log message "incompatible version number: 71"?
Can I put my application server behind my SOCKS Server?
What causes the log message "Bind failed ... Address already in use"?
1. What is SOCKS?
SOCKS is a networking proxy protocol that enables hosts on one side of SOCKS server to gain full access to hosts on the other side of the SOCKS server without requiring direct IP reachability. SOCKS redirects connection requests from hosts on opposite sides of a SOCKS server. The SOCKS server authenticates and authorizes the requests, establishes a proxy connection, and relays data.

SOCKS is commonly used as a network firewall that enables hosts behind a SOCKS server to gain full access to the Internet, while preventing unauthorized access from the Internet to the internal hosts.

There are two major versions of SOCKS: SOCKS V4 and SOCKS V5. David Koblas is the original author.

Refer to socks blog for more information.

2. How is SOCKS V5 different from SOCKS V4?
The main differences between SOCKS V5 and SOCKS V4 are:

SOCKS V4 does not support authentication. SOCKS V5 supports a variety of authentication methods.
SOCKS V4 does not support UDP proxy. SOCKS V5 does.

Refer to Introduction to SOCKS for additional information.

3. Does SOCKS V5 work with SOCKS V4?
The SOCKS V5 protocol does not include a provision to support SOCKS V4 protocol. NEC's socks5 implementation supports the SOCKS V4 protocol. The server supports SOCKS V5 and SOCKS V4 clients, and can communicate with other version 5 and 4 servers.

4. Where can I get SOCKS?
A SOCKS V4 implementation is available through anonymous socks see socks 4 list. NEC's implementation of SOCKS V5 (socks5) is available through http at socks 5 list.

Both packages include clients for telnet, ftp, finger, and whois. NEC's SOCKS5 implementation includes archie, ping, and traceroute.

Hewlett Packard provides an internal implementation of SOCKS, available at ftp://ftp.cup.hp.com/dist/socks/socks.tar.gz

Many commercial products also include built-in SOCKS protocol support.

5. Are there any SOCKS-related mailing lists?
Yes, there are three SOCKS related mailing lists: socks, socks5, and sockscap. To join the SOCKS mailing list, send an E-mail message to:
majordomo@socks.nec.com
with no subject line and a one line body:

subscribe

Correspond with members of the list by sending E-mail to:

@socks.nec.com
All three mailing lists are archived at socks blog

6. Can I use SOCKS with Windows?

A number of WinSock DLL extensions enable WinSock-based applications to use SOCKS:
SocksCap from NEC
AutoSOCKS from Aventail
Hummingbird's SOCKS Client from Hummingbird

There are also socksified WinSock Stacks, such as Peter Tattam's Trumpet WinSock at http://www.trumpet.com.au/wsk/winsock.htm.

Many commercial WinSock applications support SOCKS protocol.

7. Can I use SOCKS with a Mac?
Netscape's Navigator, NCSA's Mosaic, Fetch 3.0 (ftp client), Anarchie (archie/ftp client), Microsoft's Internet Explorer, and PointCast's client support SOCKS.

No dynamic SOCKS solutions (i.e. SocksCap, AutoSOCKS, and Hummingbird for Microsoft Windows) for the MacIntosh exist.

8. What do I have to do to modify programs to use SOCKS?
Refer to http://www.socks.nec.com/how2socksify.html for specific socksification details. You need to recompile the sources with pre-processor directives to intercept some calls such as bind(). The socks5 library can socksify TCP and UDP applications and the SOCKS V4 library can socksify TCP-based programs.

NEC's socks5 package includes some UNIX socks5 client shared libraries that can dynamically socksify programs without modifying or recompiling them. Refer to http://www.socks.nec.com/.

See also Question 6.

9. Does SOCKS handle UDP?
socks5 does, SOCKS4 does not. NEC's socks5 package includes a socksified archie client program that is a UDP application. The RealAudio Player works with runsocks (UNIX) and SocksCap (Windows).

10. How does SOCKS interact with DNS?
For SOCKS version 4.2 and earlier, SOCKS V4 clients MUST resolve local and internet host IP addresses. Configure DNS so that the SOCKS clients' resolver can resolve the addresses. Multiple DNS servers require special arrangements.

For the extended SOCKS version 4.3, SOCKS V4 clients can pass the unresolved addresses to the SOCKS V4 extended servers for resolution.

For SOCKS V5, the clients can pass unresolved host names to SOCKS V5 servers to resolve. SOCKS will work if the SOCKS V5 client or SOCKS V5 servers can resolve a host.

11. What is a single-homed and multi-homed firewall?
A multi-homed firewall has multiple network interfaces and does not forward packets. Single-homed firewalls have one network interface card. Use a single-homed firewall with a choke router that filters packets not originating from the SOCKS server.

12. Is there an RFC for SOCKS?
There is no official RFC for Version 4 of the protocol. There are two documents describing Version 4: SOCKS V4 protocol and extension to SOCKS V4 protocol.

There are three RFCs for SOCKS V5 related protocols:
RFC1928 - Describes SOCKS Version 5 protocol, also known as Authenticated Firewall Traversal (AFT).
RFC1929 - Describes Username/Password authentication for SOCKS V5.
RFC1961 - Describes GSS-API authentication for SOCKS V5

13. What does SOCKS stand for?
SOCK-et-S - an internal development names that remained after release

14. Why does the password echo when I run rftp?
The password only echoes for anonymous ftp. This is considered a feature.

15. How do you traverse multiple firewalls (socksified SOCKS server?)
Using the socksified SOCKS V4 server, rsockd, included in the socks 4.3 beta release. See the README file in the release.

16. Why do I see "inetd[]: socks/tcp server failing (looping)" in my logs?
When the socks server running from inetd receives too many connection requests, it displays this message. Run the socks server as a standalone daemon to solve the problem.

17. Can I use SOCKS with a OS/2?
Warp 4.0 has SOCKS V4 support integrated in the TCP/IP stack.

18. What causes the log message "incompatible version number: 71"?
socks displays this log message when someone tries to use the SOCKS server as an HTTP proxy. Ascii code 71 is the letter "G", the first letter of an HTTP/1.0 request.

19. Can I put my application server behind my SOCKS Server?
Yes and No.

Yes. All internal clients can directly access the application server behind the SOCKS server. External clients that know about your SOCKS server may access the application server.

No. Public Internet web servers cannot be accessed by external clients that do not know about your SOCKS server.

20. What causes the log message "Bind failed ... Address already in use"?
This log message occurs when the SOCKS server tries to bind to a port that another process is using. Typically, another SOCKS daemon is already running or inetd is listening to the port. Use the "ps" command to find and kill the other process or check /etc/inetd.conf for a conflicting entry.


Read more...

05/21 socks proxy  

Автор allexe

68.42.202.101:43734 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
68.51.193.43:56524 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
66.30.98.134:62382 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
98.193.25.57:43182 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
98.206.113.140:40064 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
24.245.39.217:5321 United States NJ, NJ, 08054, Mount Laurel, 1800 Bishops Gate Boulevard
...

202.203.32.11:1080 China Room Room 224, Main Building Tsinghua University Beijing 10
124.128.224.2:1080 China No.7 No.77 Jingsan Road,Jinan,Shandong,P.R.China
218.24.180.146:8888 China No.1 No.156,Fu-Xing-Men-Nei Street, Beijing,100031,P.R.Chin
59.44.98.198:8888 China No.6 No.6,feiyun Road,hunnan District,Shenyang
125.32.154.162:1080 China No.1 No.156,Fu-Xing-Men-Nei Street, Beijing,100031,P.R.Chin
222.174.68.61:1080 China No.9 No.999, road Shunhua, Jinan, Shandong p
58.56.87.2:1080 China No.9 No.999, road Shunhua, Jinan, Shandong p
219.136.253.205:1080 China No.3 No.31 ,jingrong street,beijing 100032
218.25.90.55:1080 China No.1 No.156,Fu-Xing-Men-Nei Street, Beijing,100031,P.R.Chin
116.212.112.41:1080 Hong Kong 19/F 19/F, WORLD PEACE CTR, NO 55 ,WO TONG TSUI STREET,KWAI
210.219.220.194:1080 Korea (South) Choo Choongjungno3-Ka Seodaemoon-Gu
85.239.0.99:1080 Kuwait Sula Sulaibia Kuwait
84.31.50.174:15705 Netherlands Gyro Gyroscoopweg 90-92 1042 AX Amsterdam Netherlands
203.177.180.38:1080 Philippines 4/F 4/F Globe Tlecom Plaza Pioneer cor Madisons Sts. Manda
89.32.152.4:1080 Romania Eudo Eudoxiu Hurmuzachi Nr.6 Bl.6, Sc.B, Ap.31 Radauti Suce
68.42.202.101:43734 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
68.51.193.43:56524 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
66.30.98.134:62382 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
98.193.25.57:43182 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
98.206.113.140:40064 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
24.245.39.217:5321 United States NJ, NJ, 08054, Mount Laurel, 1800 Bishops Gate Boulevard
207.234.146.197:1080 United States FL, FL, 33309, Ft. Lauderdale, Corporate headquarters 3250
68.84.158.150:56851 United States NJ, NJ, 08054, Mt Laurel, 1800 Bishops Gate Blvd
..
same list
202.203.32.11:1080
124.128.224.2:1080
218.24.180.146:8888
59.44.98.198:8888
125.32.154.162:1080
222.174.68.61:1080
58.56.87.2:1080
219.136.253.205:1080
218.25.90.55:1080
116.212.112.41:1080
210.219.220.194:1080
85.239.0.99:1080
84.31.50.174:15705
203.177.180.38:1080
89.32.152.4:1080
68.42.202.101:43734
68.51.193.43:56524
66.30.98.134:62382
98.193.25.57:43182
98.206.113.140:40064
24.245.39.217:5321
207.234.146.197:1080
68.84.158.150:56851


Read more...

SOCKS from Wiki  

Автор allexe

SOCKS is an Internet protocol that allows client-server applications to transparently use the services of a network firewall. SOCKS is an abbreviation for "SOCKetS".

Clients behind a firewall, needing to access exterior servers, may connect to a SOCKS proxy server instead. Such proxy server controls the eligibility of the client to access the external server and passes the request on to the server. SOCKS can also be used in the opposite way, allowing the clients outside the firewall ("exterior clients") to connect to servers inside the firewall (internal servers).
...

SOCKS is an Internet protocol that allows client-server applications to transparently use the services of a network firewall. SOCKS is an abbreviation for "SOCKetS".

Clients behind a firewall, needing to access exterior servers, may connect to a SOCKS proxy server instead. Such proxy server controls the eligibility of the client to access the external server and passes the request on to the server. SOCKS can also be used in the opposite way, allowing the clients outside the firewall ("exterior clients") to connect to servers inside the firewall (internal servers).

The protocol was originally developed by David Koblas, a system administrator of MIPS Computer Systems. After MIPS was taken over by Silicon Graphics in 1992, Koblas presented a paper on SOCKS at that year's Usenix Security Symposium and SOCKS became publicly available. The protocol was extended to version 4 by Ying-Da Lee of NEC.

The SOCKS reference architecture and client are owned by Permeo Technologies, (note that Permeo Technologies has been bought out by Blue Coat Systems ) a spin-off from NEC.[4]

SOCKS performs at Layer 5 of the OSI model - the Session Layer (an intermediate layer between the presentation layer and the transport layer).

SOCKS 4 protocol

A typical SOCKS 4 connection request looks like this (each number is one byte):

Client to SOCKS Server:
field 1: SOCKS version number, 1 byte, must be 0x04 for this version
field 2: command code, 1 byte:
0x01 = establish a TCP/IP stream connection
0x02 = establish a TCP/IP port binding
field 3: network byte order port number, 2 bytes
field 4: network byte order IP address, 4 bytes
field 5: the user ID string, variable length, terminated with a null (0x00)

Server to SOCKS client:
field 1: null byte
field 2: status, 1 byte:
0x5a = request granted
0x5b = request rejected or failed
0x5c = request failed because client is not running identd (or not reachable from the server)
0x5d = request failed because client's identd could not confirm the user ID string in the request
field 3: 2 arbitrary bytes, that should be ignored
field 4: 4 arbitrary bytes, that should be ignored

Example:

This is a SOCKS 4 request to connect Fred to 66.102.7.99:80, the server replies with an "OK".
Client: 0x04 0x01 0x00 0x50 0x42 0x66 0x07 0x63 0x46 0x72 0x65 0x64 0x00
The last field is 'Fred' in ASCII, followed by a null byte.
Server: 0x00 0x5a 0xXX 0xXX 0xXX 0xXX 0xXX 0xXX
0xXX can be any byte value. The Socks 4 protocol specifies the values of these bytes should be ignored.

From this point on any data sent from the SOCKS client to the SOCKS server will be relayed to 66.102.7.99 and vice versa.

The command field can be 0x01 for "connect" or 0x02 for "bind". "bind" allows incoming connections for protocols like active FTP.

[edit]
SOCKS 4a protocol

SOCKS 4a is a simple extension to SOCKS 4 protocol that allows a client that cannot resolve the destination host's domain name to specify it.

The client should set the first three bytes of DSTIP to NULL and the last byte to a non-zero value (This corresponds to IP address 0.0.0.x, with x nonzero, an inadmissible destination address and thus should never occur if the client can resolve the domain name). Following the NULL byte terminating USERID, the client must send the destination domain name and terminate it with another NULL byte. This is used for both "connect" and "bind" requests.

Client to Socks Server:
field 1: SOCKS version number, 1 byte, must be 0x04 for this version
field 2: command code, 1 byte:
0x01 = establish a TCP/IP stream connection
0x02 = establish a TCP/IP port binding
field 3: network byte order port number, 2 bytes
field 4: deliberate invalid IP address, 4 bytes, first three must be 0x00 and the last one must not be 0x00
field 5: the user ID string, variable length, terminated with a null (0x00)
field 6: the domain name of the host we want to contact, variable length, terminated with a null (0x00)

Server to SOCKS client:
field 1: null byte
field 2: status, 1 byte:
0x5a = request granted
0x5b = request rejected or failed
0x5c = request failed because client is not running identd (or not reachable from the server)
0x5d = request failed because client's identd could not confirm the user ID string in the request
field 3: network byte order port number, 2 bytes
field 4: network byte order IP address, 4 bytes

A server using protocol 4A must check the DSTIP in the request packet. If it represents address 0.0.0.x with nonzero x, the server must read in the domain name that the client sends in the packet. The server should resolve the domain name and make connection to the destination host if it can.

SOCKS 5 protocol

The SOCKS 5 protocol, an extension of the SOCKS 4 protocol that offers more choices of authentication, is defined in RFC 1928. The initial handshake now consists of the following:
Client connects and sends a greeting which includes a list of authentication methods supported.
Server chooses one (or sends a failure response if none of the offered methods are acceptable).
Several messages may now pass between the client and the server depending on the authentication method chosen.
Client sends a connection request similar to SOCKS 4.
Server responds similar to SOCKS 4.

The authentication methods supported are numbered as follows:
0x00 - No authentication
0x01 - GSSAPI
0x02 - Username/Password
0x03-0x7F - methods assigned by IANA
0x80-0xFE - methods reserved for private use

The initial greeting from the client is:
field 1: SOCKS version number (must be 0x05 for this version)
field 2: number of authentication methods supported, 1 byte
field 3: authentication methods, variable length, 1 byte per method supported

The server's choice is communicated:
field 1: SOCKS version, 1 byte (0x05 for this version)
field 2: chosen authentication method, 1 byte, or 0xFF if no acceptable methods were offered

The subsequent authentication is method-dependent.

The client's connection request is:
field 1: SOCKS version number, 1 byte (must be 0x05 for this version)
field 2: command code, 1 byte:
0x01 = establish a TCP/IP stream connection
0x02 = establish a TCP/IP port binding
0x03 = associate a UDP port
field 3: reserved, must be 0x00
field 4: address type, 1 byte:
0x01 = IPv4 address
0x03 = Domain name
0x04 = IPv6 address
field 5: destination address of
4 bytes for IPv4 address
1 byte of name length followed by the name for Domain name
16 bytes for IPv6 address
field 6: port number in a network byte order, 2 bytes

Server response:
field 1: SOCKS protocol version, 1 byte (0x05 for this version)
field 2: status, 1 byte:
0x00 = request granted
0x01 = general failure
0x02 = connection not allowed by ruleset
0x03 = network unreachable
0x04 = host unreachable
0x05 = connection refused by destination host
0x06 = TTL expired
0x07 = command not supported / protocol error
0x08 = address type not supported
field 3: reserved, must be 0x00
field 4: address type, 1 byte:
0x01 = IPv4 address
0x03 = Domain name
0x04 = IPv6 address
field 5: destination address of
4 bytes for IPv4 address
1 byte of name length followed by the name for Domain name
16 bytes for IPv6 address
field 6: network byte order port number, 2 bytes

There are client programs that "socksify", which allows adaptation of any networked software to connect to external networks via SOCKS.
http://en.wikipedia.org/wiki/SOCKS


Read more...

05/20 US socks 4 socks 5 list  

Автор allexe

68.114.250.242:29483
76.110.97.218:59933
98.218.215.79:12057
221.174.22.7:1080
76.104.218.228:19271
76.237.200.189:29532
74.140.180.142:48390
72.175.77.164:50501
98.192.208.205:48393
71.153.55.227:54295
68.82.209.214:44705
...

209.254.15.131:80
69.125.162.166:14217
202.147.189.250:1080
121.52.155.50:1080
116.212.112.41:1080
70.135.15.137:36395
68.229.42.45:17866
58.56.87.2:1080
66.30.98.134:60655
200.217.233.210:1080
218.94.130.107:1080
221.12.147.80:1080
121.22.20.202:1080
98.199.190.188:15878
67.82.123.50:24155
67.171.229.37:36705
210.219.220.194:1080
207.255.18.52:22380
222.174.68.61:1080
210.41.224.237:1080
24.16.151.220:30577
4.178.189.120:23982
125.32.154.162:1080
124.128.224.2:1080
76.187.216.94:56434
71.202.170.117:4813
99.135.164.195:52365
70.248.133.161:35223
202.203.32.11:1080
67.84.106.45:48865
222.161.3.31:1080
68.114.250.242:29483
76.110.97.218:59933
98.218.215.79:12057
221.174.22.7:1080
76.104.218.228:19271
76.237.200.189:29532
74.140.180.142:48390
72.175.77.164:50501
98.192.208.205:48393
71.153.55.227:54295
68.82.209.214:44705
68.12.7.68:6335


Read more...

05/18 usa socks 5 list  

Автор allexe

209.30.37.158:14890 0 b/s United United States TX, 75075, Plano, Alma
75.33.107.224:12634 0 b/s United United States TX, 75080, Richardson, 2701 N. Central Ex
75.80.82.253:9345 0 b/s United United States VA, 20171, Herndon, 13241 Woodland Park R
24.236.193.201:46766 0 b/s United United States MO, 63131, St. Louis, 12405 Powerscourt D
...

68.96.113.89:48329 0 United United States GA, 30319, Atlanta, 1400 Lake Hearn Dr
24.3.15.50:29102 0 b/s United United States NJ, 08002, Cherry Hill, 3 Executive Campu
67.171.229.37:56539 0 United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
70.162.250.127:40854 0 b/s United United States GA, 30319, Atlanta, 1400 Lake Hearn Dr.
76.98.132.34:20646 0 United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
24.45.156.103:22616 0 b/s United United States NY, 11801, Hicksville, 111 New South Road
69.228.129.199:15156 0 United United States CA, 94107, San Francisco, Private Address
76.125.89.134:25552 0 b/s United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
67.169.127.210:12686 0 United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
71.224.131.67:17438 0 United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
71.58.43.209:15206 0 United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
207.234.146.197:1080 0 United United States FL, 33309, Ft. Lauderdale, Corporate head
75.139.190.90:22341 0 b/s United United States MO, 63131, St. Louis, 12405 Powerscourt D
209.30.37.158:14890 0 b/s United United States TX, 75075, Plano, Alma
75.33.107.224:12634 0 b/s United United States TX, 75080, Richardson, 2701 N. Central Ex
75.80.82.253:9345 0 b/s United United States VA, 20171, Herndon, 13241 Woodland Park R
24.236.193.201:46766 0 b/s United United States MO, 63131, St. Louis, 12405 Powerscourt D
98.206.113.140:24384 0 b/s United United States NJ, 08054, Mt Laurel, 1800 Bishops Gate B
68.101.164.100:30129 0 b/s United United States GA, 30313, Atlanta, 1400 Lake Hearn Drive
74.140.180.142:61957 0 United United States KY, 40223, Louisville, 10200 Linn Station
70.240.221.239:6208 0 United United States TX, 75080, Richardson, 2701 N. Central Ex


Read more...