<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The Legendary Great Firewall of China</title>
	<link>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china</link>
	<description>Angry rants on this unjust world</description>
	<pubDate>Fri, 16 May 2008 03:27:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Steve&#8217;s Thought &#187; 香港的GFW﹗？</title>
		<link>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-3308</link>
		<dc:creator>Steve&#8217;s Thought &#187; 香港的GFW﹗？</dc:creator>
		<pubDate>Sun, 24 Sep 2006 16:30:23 +0000</pubDate>
		<guid>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-3308</guid>
		<description>[...] 今次 packet 19 收到 RST packet，真係有啲古怪。但係同其他遇到  GFW 嘅人唔同，可以參考 spacehunt.info，明天再繼續分析。 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 今次 packet 19 收到 RST packet，真係有啲古怪。但係同其他遇到  GFW 嘅人唔同，可以參考 spacehunt.info，明天再繼續分析。 [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spacehunt</title>
		<link>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-2721</link>
		<dc:creator>spacehunt</dc:creator>
		<pubDate>Thu, 17 Aug 2006 16:37:48 +0000</pubDate>
		<guid>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-2721</guid>
		<description>&lt;blockquote&gt;
iptables solve the problem if used on both sides.
&lt;/blockquote&gt;

That's exactly what we tried. Sure, the connection doesn't drop, but there's still the transparent proxy to deal with.</description>
		<content:encoded><![CDATA[<blockquote><p>
iptables solve the problem if used on both sides.
</p></blockquote>
<p>That&#8217;s exactly what we tried. Sure, the connection doesn&#8217;t drop, but there&#8217;s still the transparent proxy to deal with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: well at least</title>
		<link>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-2718</link>
		<dc:creator>well at least</dc:creator>
		<pubDate>Thu, 17 Aug 2006 13:46:24 +0000</pubDate>
		<guid>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-2718</guid>
		<description>you are right about the Man-in-the-middle.
Give this a look
http://www.lightbluetouchpaper.org/2006/06/27/ignoring-the-great-firewall-of-china/

iptables solve the problem if used on both sides.</description>
		<content:encoded><![CDATA[<p>you are right about the Man-in-the-middle.<br />
Give this a look<br />
<a href="http://www.lightbluetouchpaper.org/2006/06/27/ignoring-the-great-firewall-of-china/" rel="nofollow">http://www.lightbluetouchpaper.org/2006/06/27/ignoring-the-great-firewall-of-china/</a></p>
<p>iptables solve the problem if used on both sides.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Sheed</title>
		<link>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-2449</link>
		<dc:creator>Lawrence Sheed</dc:creator>
		<pubDate>Wed, 26 Jul 2006 16:47:15 +0000</pubDate>
		<guid>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-2449</guid>
		<description>Ok, I'm seeing this now.

We setup a service on port 26 for clients to send mail through with SMTP AUTH
(port 25 is spam filtered with a bunch of rbl's now, and we're seeing plenty collateral damage blocking)

If clients were blocked, we told them change over to port 26.  (I would normally tell people use SSL / port 587, but we find that incurs the wrath of connection reset^H^H the firewall in spades, so i don't even bother)

Problem was that they still couldn't send mail.

A check on the server showed that everything was coming in ok except for the DATA.
Somewhere along the line the 'china proxy' was dropping that.

I did some logging myself as this was replicatable, and lo and behold, I was seeing similar to you - what I was sending was not what I was receiving.

Logging them off / on ADSL solved this for me. Probably something like - new ip address, new session with proxy server. 

Makes running mail services here such fun, sigh...</description>
		<content:encoded><![CDATA[<p>Ok, I&#8217;m seeing this now.</p>
<p>We setup a service on port 26 for clients to send mail through with SMTP AUTH<br />
(port 25 is spam filtered with a bunch of rbl&#8217;s now, and we&#8217;re seeing plenty collateral damage blocking)</p>
<p>If clients were blocked, we told them change over to port 26.  (I would normally tell people use SSL / port 587, but we find that incurs the wrath of connection reset^H^H the firewall in spades, so i don&#8217;t even bother)</p>
<p>Problem was that they still couldn&#8217;t send mail.</p>
<p>A check on the server showed that everything was coming in ok except for the DATA.<br />
Somewhere along the line the &#8216;china proxy&#8217; was dropping that.</p>
<p>I did some logging myself as this was replicatable, and lo and behold, I was seeing similar to you - what I was sending was not what I was receiving.</p>
<p>Logging them off / on ADSL solved this for me. Probably something like - new ip address, new session with proxy server. </p>
<p>Makes running mail services here such fun, sigh&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#8220;Man-in-the-Middle&#8221; is an understatement at spacehunt.info</title>
		<link>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-1590</link>
		<dc:creator>&#8220;Man-in-the-Middle&#8221; is an understatement at spacehunt.info</dc:creator>
		<pubDate>Fri, 09 Jun 2006 10:09:12 +0000</pubDate>
		<guid>http://spacehunt.info/2006/06/09/the-legendary-great-firewall-of-china#comment-1590</guid>
		<description>[...] Blog        &#171; The Legendary Great Firewall of China [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Blog        &laquo; The Legendary Great Firewall of China [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
