iGFW

你好我现在转成ipv6了，怎样转回ipv4呢

Tuinslak/GFW-URL-checker – GitHub
https://github.com/Tuinslak/GFW-URL-checker
“Chinese firewall blocked url tester “;25,6 MB;
“GFW-URL-checker /
name age
history
message
directory hosts/ Wed May 18 09:41:48 -0700 2011 ytimg [Tuinslak]
directory testResults/ Wed May 18 21:05:58 -0700 2011 nl check @ 03:30:01 19-05-2011 (UTC) [gfw@vm1.rootspirit.com]
file .gitignore Sun Jan 23 15:54:49 -0800 2011 renames [Tuinslak]
file README.md Mon Mar 07 14:34:07 -0800 2011 readme [Tuinslak]
file checkHosts.sh Wed Mar 16 15:22:52 -0700 2011 removed threading for tests [Tuinslak]
file cleanHost.sh Thu Mar 10 07:05:48 -0800 2011 host cleaner [Tuinslak]
file country.sh.example Sat Mar 12 14:39:25 -0800 2011 increased wget tries & timeout [Tuinslak]
file sortHosts.sh Sat Feb 12 17:58:57 -0800 2011 hosts + tolower() [Tuinslak]
file update.sh Tue Mar 08 13:22:57 -0800 2011 asynchrous wget + check if done before continuing [Tuinslak]
README.md
List of URLs blocked by the Great Firewall of China (Golden Shield Project)
… or at least, an attempt to create a list.
Checks once a day if the hosts (URLs) in the hosts directory are accessible and commits the output in three files (testResults/).
results_ok.csv => list of hosts accessible (header 200 OK reply)
results_nok.csv => list of hosts unaccessible (no reply)
results.csv => list of all hosts
Mind that it only check HTTP header responses, and doesn’t actually check the content of the returned page (e.g. altered page content)
It’s currently running and checking from 3 locations; Belgium, The Netherlands, and China. If you want additional countries to be monitored, I will need access to a shell (see below).
Submit URLs
Submit URLs, IPs or domains to gfw@tuinslak.be. I’ll probably create some small submit page in the future.
Alternatively, you can create a ticket (https://github.com/Tuinslak/GFW-URL-checker/issues) on Github.
Shells wanted
I’m looking for additional Unix/Linux shells all around the world (but preferably countries that apply censorship). All I need is wget, git and cron installed, 10ish mb quota, and a bit of your CPU time and networking. Contact me on the e-mail above. These can be ARM shells (such as Guruplug/Sheevaplug).”
“Why ?
I got annoyed not being able to share certain sites with people residing in China.
I then decided to find simple ways to by-pass the GFW using OpenVPN + Squid proxy and a PAC file redirecting only blocked URLs through the proxy. But I didn’t have a complete list of blocked URLs and wasn’t able to find one on the net, so I tried to populate my own.
Knowledge is power.”
“Techniques used
Chinese gov blocks sites using several methods,
IP and/or DNS blocking
Incorrect DNS replies (solvable by using different DNS server, such as 85.12.6.171)
URL filtering (Wikipedia for example)
Packet filtering (plain HTTP only? FTP seems to work) > snif content on certain keywords (e.g. try downloading Alexa 1m list: http://yeri.be/j1 – conn. reset at certain byte)
Connection RST (reset) > different host replies RST packet, making your PC believe you are unable to connect (most common)
Maintained by Yeri Tiete (aka Tuinslak)
Blog: http://yeri.be”

翻墙相关

http://sourceforge.net/projects/jsocks/
“SOCKS Server and Library for Java. Support for versions 4 and 5 of SOCKS protocol. Designed to be easily expandable to support different encryption/authentication/authorization methods. Sample server and client are available.”
http://sourceforge.net/projects/jsocks/files/
“jsocks.jar 2011-03-19 394.5 KB”
http://jsocks.sourceforge.net/

“你好”

1.http://sourceforge.net/projects/proxpy/
“Proxpy is a TCP proxy and debugging tool. It runs on Windows, Linux, Unix and any other system that supports java. Uses are for debugging TCP communications, tunneling over SSL, converting SSL to non-SSL, forwarding traffic.”
http://sourceforge.net/projects/proxpy/files/1.00/
“proxpy-1.00-source.zip 2010-05-16 30.0 KB
proxpy-1.00-binary.zip 2010-05-16 21.2 KB”
http://proxpy.sourceforge.net/usage.html
“Peter Bennett’s General Purpose Proxy and debug tool
This has been used in development environments, it works for proxying all types of TCP traffic. It can be used to bypass firewall restrictions, for logging messages for debug purposes, and to add SSL to a non SSL connection for debug or other purposes. It is fully multi threaded so it may be able to handle high volumes. It runs on unix or windows, wherever there is a java environment.
Usage:
java -jar proxy.jar xxxx.properties
java -jar proxy.jar xxxx.properties closeDown
If logging is turned on in the property file you may want to redirect the output to a file. Also you may want to put & on the end under unix so it runs in a separate process.
Parameter file:
closedownport=25999 (available port # used for shutting down the proxy)
truststore= (keystore – optional – only used for SSL)
logging= (true / false default = false, for logging all messages)
inport1= (required – assign a port number)
inaddress1= (optional – only if need to restrict to an ip address)
inssl1= (true / false default = false, specify true if ssl is used and logging of decrypted messages)
inkeystore1= (required if inssl1 is true)
inkeypasswd1= (required if inkeystore1 provided)
outport1= (required – assign a port number)
outaddress1= (required – where to proxy to)
outssl1= (true / false default = false, specify true if ssl is used at destination)
outkeystore1= (optional – only if 2-way cert needed for SSL)
outkeypasswd1=(required if outkeystore1 provided)

The ones with ‘1’ at the end can be repeated as many times as desired with numbers from 2 up.
SSL Options:
If input and output are both ssl and logging is false you can use inssl1 and outssl1 both false. The ssl will proxy straight through. If logging is true in this case then encrypted messages would be logged. That is not useful.
2. If input and output are both ssl and logging is true you must use inssl1 and outssl1 both true. You must have a certificate and keystore for inkeystore, the originator will see that certificate. for 1 way SSL you do not need outkeystore. For 2way SSL you need outkeystore with a certificate. The server will see that certificate.
3. You can convert non SSL to SSL. If sender does not want to use SSL but receiver uses SSL leave inssl1 as false but specify outssl1 as true. You do not need a keystore unless the receiver uses 2 way SSL. In that case specify outkeystore and the receiver will see this certificate.
4. You can convert SSL to non SSL. If sender uses SSL but receiver does not, set inssl true and outssl false. You need inkeystore and sender will see this certificate. If two way SSL is used, we will not check The sender’s certificate.
5. You can set up a SSL tunnel for non SSL users by using proxy on the sending machine and on the receiving machine with appropriate options and a keystore on the receiving machine.
Requirements
(1) One of the following:
Windows (Windows XP, 2000, 98, ME, etc.)
Linux
Macintosh
Solaris SPARC
Solaris x86
Any Machine that supports Java 6
(2) Java Runtime Environment version 6 or higher. This is a free download from http://www.java.com. ”

2.http://sourceforge.net/projects/assh/
“Assh (Anonymous Secure SHell) establishes an anonymous connection to ssh servers, using SSL proxies”
http://sourceforge.net/projects/assh/files/
http://assh.sourceforge.net/
“Download
This tarball compiles under Linux and Mac OS X.
version 2.3 (2010/07/09): assh-2.3.tgz (patch)
version 2.2 (2010/04/01): assh-2.2.tgz
Introduction
Assh (Anonymous Secure SHell) is a ssh client which uses SSL proxies to establish anonymous connections. This tool can be usefull for people who want to keep anonymity when they connect to public servers or, for people who work on restricted LAN networks that do not authorize connection to destination port tcp/22 (for example, behind a firewall). See README included in the tarball file for further details.
The Anonymous Secure SHell program has been made under GPL licence and use a Corckscrew module.
Installation
Download the last version from http://assh.sf.net.
$ gzip -dc assh-.tgz | tar xf – ; cd assh-
$ make
Once compiled, to copy both assh and corkscrew binary files into /usr/bin/, type “make install” as root user.
Usage
Before connecting to ssh servers, you will need to make Assh retrieve and build a list of working SSL proxies, this is called the initialization mode (“-i” option). After this step, you will be able to connect servers anonymously by using common OpenSSH options, this is called the connection mode. Those two modes are described bellow:
Initialization mode
To generate a list of working proxies, assh will parse this web page and try a CONNECT resquest on each proxies. On request success, proxy’s ip and port will be stored in a configuration file (~/.assh/proxy.lst). For example, if you type:
$ assh -i hostname
Assh parses proxies from a list retrieved from Internet, check them with a CONNECT hostname:22 request and store the proxies that authorize such request.
If you already have your own proxies informations stored in a file ( “ip_address:port” per line), you can tell assh to check this list better than parsing the default url as above. This can be done by typing:
$ assh -i -f your_own_proxy_file.txt hostname
To fill the file “your_own_proxy_file.txt”, you can manualy copy a lot of proxy informations from this link and then paste them into your file. Keep in mind that this file must respect a specific format, one couple “ip_address:port” per line. The required “hostname” argument must be a server that run sshd and it is not necessary that you have a shell account on it. It is only used in CONNECT requests during proxies checking. So it can be your own ip address or any server on Internet that provides sshd service. But to preserve anonymity, this must not be the ssh server you want to connect to !
Connection mode
Anonymous connection to sshd servers can be done by using common OpenSSH options. The difference is that assh will transparently use a SSL proxy randomly choosen from your proxies configuration file (previoulsy generated during initialization mode).
For example, to get connected anonymously on host.domain.com, where sshd service is listening on port 2222, use:
$ assh -4x -p2222 host.domain.com
Note: If you want to pass a “-o” parameters, remind that the double quotes character (“) must be replaced by \” in Assh.
For example, the ssh command:
$ ssh -4 -o “StrictHostKeyChecking no” remote.hostname.com
will become for Assh:
$ assh -4 -o \”StrictHostKeyChecking no\” remote.hostname.com
Comments
Feel free to send any comments or bugs to authors: vladz and Lorenzzz ”

“你好”