<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: bmobile Zoom! (+ E-Speed, DST Go!) Findings</title>
	<atom:link href="http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/</link>
	<description>http://blog.thewheatfield.org</description>
	<lastBuildDate>Wed, 15 Feb 2012 02:46:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: ardi angeles</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-3192</link>
		<dc:creator><![CDATA[ardi angeles]]></dc:creator>
		<pubDate>Mon, 13 Dec 2010 00:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-3192</guid>
		<description><![CDATA[where can i get a bmobile software for my pc? I lost my cd :c]]></description>
		<content:encoded><![CDATA[<p>where can i get a bmobile software for my pc? I lost my cd :c</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Md</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2967</link>
		<dc:creator><![CDATA[Md]]></dc:creator>
		<pubDate>Sun, 17 Oct 2010 01:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2967</guid>
		<description><![CDATA[hi thewheat,

is it any chance to running own server with Bmobile broadband, so far i cant access my site, even change from port 80 to 8000(router port forward). seem no ports can be used. well im using E220 Huawei broadband + Vigsys VD30 router + Bmobile broadband..do you have any solutions. 

Pinging www.darkcode31337.co.cc [202.93.215.91] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 202.93.215.91:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


here is netstat

C:\Users\Darkcode31337&gt;netstat -ano

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1384
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1748
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       3732
  TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1748
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       740
  TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1748
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       216
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       444
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       836
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       904
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING       548
  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       540
  TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       2076
  TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1384
  TCP    127.0.0.1:14147        127.0.0.1:49158        ESTABLISHED     1384
  TCP    127.0.0.1:49158        127.0.0.1:14147        ESTABLISHED     2272
  TCP    127.0.0.1:59359        127.0.0.1:59360        ESTABLISHED     3884
  TCP    127.0.0.1:59360        127.0.0.1:59359        ESTABLISHED     3884
  TCP    127.0.0.1:59361        127.0.0.1:59362        ESTABLISHED     3884
  TCP    127.0.0.1:59362        127.0.0.1:59361        ESTABLISHED     3884
  TCP    192.168.2.149:139      0.0.0.0:0              LISTENING       4
  TCP    192.168.2.149:60670    70.38.38.234:80        ESTABLISHED     3884
  TCP    192.168.2.149:60758    64.4.44.35:80          ESTABLISHED     3884
  TCP    192.168.2.149:60780    69.28.158.131:27038    TIME_WAIT       0
  TCP    192.168.2.149:60782    69.63.189.11:80        ESTABLISHED     3884
  TCP    192.168.2.149:60785    69.63.180.45:80        ESTABLISHED     3884
  TCP    192.168.2.149:60786    69.28.153.82:27038     TIME_WAIT       0
  TCP    192.168.2.149:60788    203.66.135.193:27030   ESTABLISHED     1876
  TCP    [::]:135               [::]:0                 LISTENING       740
  TCP    [::]:445               [::]:0                 LISTENING       4
  TCP    [::]:5357              [::]:0                 LISTENING       4
  TCP    [::]:49152             [::]:0                 LISTENING       444
  TCP    [::]:49153             [::]:0                 LISTENING       836
  TCP    [::]:49154             [::]:0                 LISTENING       904
  TCP    [::]:49155             [::]:0                 LISTENING       548
  TCP    [::]:49156             [::]:0                 LISTENING       540
  TCP    [::]:49157             [::]:0                 LISTENING       2076
  UDP    0.0.0.0:500            *:*                                    904
  UDP    0.0.0.0:3702           *:*                                    2964
  UDP    0.0.0.0:3702           *:*                                    2964
  UDP    0.0.0.0:4500           *:*                                    904
  UDP    0.0.0.0:5355           *:*                                    900
  UDP    0.0.0.0:63946          *:*                                    2964
  UDP    127.0.0.1:1900         *:*                                    2964
  UDP    127.0.0.1:62018        *:*                                    2964
  UDP    192.168.2.149:137      *:*                                    4
  UDP    192.168.2.149:138      *:*                                    4
  UDP    192.168.2.149:1900     *:*                                    2964
  UDP    192.168.2.149:62017    *:*                                    2964
  UDP    [::]:500               *:*                                    904
  UDP    [::]:3702              *:*                                    2964
  UDP    [::]:3702              *:*                                    2964
  UDP    [::]:4500              *:*                                    904
  UDP    [::]:5355              *:*                                    900
  UDP    [::]:63947             *:*                                    2964
  UDP    [::1]:1900             *:*                                    2964
  UDP    [::1]:62016            *:*                                    2964
  UDP    [fe80::90d5:c7c1:5be7:c905%11]:1900  *:*
     2964
  UDP    [fe80::90d5:c7c1:5be7:c905%11]:62015  *:*
      2964

if u have any solutions about that plz sent me an email plz...]]></description>
		<content:encoded><![CDATA[<p>hi thewheat,</p>
<p>is it any chance to running own server with Bmobile broadband, so far i cant access my site, even change from port 80 to 8000(router port forward). seem no ports can be used. well im using E220 Huawei broadband + Vigsys VD30 router + Bmobile broadband..do you have any solutions. </p>
<p>Pinging <a href="http://www.darkcode31337.co.cc" rel="nofollow">http://www.darkcode31337.co.cc</a> [202.93.215.91] with 32 bytes of data:<br />
Request timed out.<br />
Request timed out.<br />
Request timed out.<br />
Request timed out.</p>
<p>Ping statistics for 202.93.215.91:<br />
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),</p>
<p>here is netstat</p>
<p>C:\Users\Darkcode31337&gt;netstat -ano</p>
<p>Active Connections</p>
<p>  Proto  Local Address          Foreign Address        State           PID<br />
  TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1384<br />
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1748<br />
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       3732<br />
  TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1748<br />
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       740<br />
  TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1748<br />
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4<br />
  TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       216<br />
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING       4<br />
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       444<br />
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       836<br />
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       904<br />
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING       548<br />
  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       540<br />
  TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       2076<br />
  TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1384<br />
  TCP    127.0.0.1:14147        127.0.0.1:49158        ESTABLISHED     1384<br />
  TCP    127.0.0.1:49158        127.0.0.1:14147        ESTABLISHED     2272<br />
  TCP    127.0.0.1:59359        127.0.0.1:59360        ESTABLISHED     3884<br />
  TCP    127.0.0.1:59360        127.0.0.1:59359        ESTABLISHED     3884<br />
  TCP    127.0.0.1:59361        127.0.0.1:59362        ESTABLISHED     3884<br />
  TCP    127.0.0.1:59362        127.0.0.1:59361        ESTABLISHED     3884<br />
  TCP    192.168.2.149:139      0.0.0.0:0              LISTENING       4<br />
  TCP    192.168.2.149:60670    70.38.38.234:80        ESTABLISHED     3884<br />
  TCP    192.168.2.149:60758    64.4.44.35:80          ESTABLISHED     3884<br />
  TCP    192.168.2.149:60780    69.28.158.131:27038    TIME_WAIT       0<br />
  TCP    192.168.2.149:60782    69.63.189.11:80        ESTABLISHED     3884<br />
  TCP    192.168.2.149:60785    69.63.180.45:80        ESTABLISHED     3884<br />
  TCP    192.168.2.149:60786    69.28.153.82:27038     TIME_WAIT       0<br />
  TCP    192.168.2.149:60788    203.66.135.193:27030   ESTABLISHED     1876<br />
  TCP    [::]:135               [::]:0                 LISTENING       740<br />
  TCP    [::]:445               [::]:0                 LISTENING       4<br />
  TCP    [::]:5357              [::]:0                 LISTENING       4<br />
  TCP    [::]:49152             [::]:0                 LISTENING       444<br />
  TCP    [::]:49153             [::]:0                 LISTENING       836<br />
  TCP    [::]:49154             [::]:0                 LISTENING       904<br />
  TCP    [::]:49155             [::]:0                 LISTENING       548<br />
  TCP    [::]:49156             [::]:0                 LISTENING       540<br />
  TCP    [::]:49157             [::]:0                 LISTENING       2076<br />
  UDP    0.0.0.0:500            *:*                                    904<br />
  UDP    0.0.0.0:3702           *:*                                    2964<br />
  UDP    0.0.0.0:3702           *:*                                    2964<br />
  UDP    0.0.0.0:4500           *:*                                    904<br />
  UDP    0.0.0.0:5355           *:*                                    900<br />
  UDP    0.0.0.0:63946          *:*                                    2964<br />
  UDP    127.0.0.1:1900         *:*                                    2964<br />
  UDP    127.0.0.1:62018        *:*                                    2964<br />
  UDP    192.168.2.149:137      *:*                                    4<br />
  UDP    192.168.2.149:138      *:*                                    4<br />
  UDP    192.168.2.149:1900     *:*                                    2964<br />
  UDP    192.168.2.149:62017    *:*                                    2964<br />
  UDP    [::]:500               *:*                                    904<br />
  UDP    [::]:3702              *:*                                    2964<br />
  UDP    [::]:3702              *:*                                    2964<br />
  UDP    [::]:4500              *:*                                    904<br />
  UDP    [::]:5355              *:*                                    900<br />
  UDP    [::]:63947             *:*                                    2964<br />
  UDP    [::1]:1900             *:*                                    2964<br />
  UDP    [::1]:62016            *:*                                    2964<br />
  UDP    [fe80::90d5:c7c1:5be7:c905%11]:1900  *:*<br />
     2964<br />
  UDP    [fe80::90d5:c7c1:5be7:c905%11]:62015  *:*<br />
      2964</p>
<p>if u have any solutions about that plz sent me an email plz&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2442</link>
		<dc:creator><![CDATA[Eric]]></dc:creator>
		<pubDate>Wed, 17 Mar 2010 01:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2442</guid>
		<description><![CDATA[Patrick,

I guess they cannot afford to have 100% 3.5G coverage for all parts of Brunei, so maybe some areas like Sg. Liang may only be limited to 3G speeds.

In the past two months of testing the ZOOM! the best I&#039;ve got is about 500KB/s (3.9Mb/s) but its very rare to attain this speed. The advertised &#039;up to 7.2Mbps&#039; is really just a marketing gimmick.

I haven&#039;t had the chance to try out Win7 with ZOOM! yet but I doubt that it&#039;s due to the OS. I&#039;ve tried it on 1 desktop and 2 laptops running on XP and all exhibit the same problem (i.e. loss of connectivity after a while).]]></description>
		<content:encoded><![CDATA[<p>Patrick,</p>
<p>I guess they cannot afford to have 100% 3.5G coverage for all parts of Brunei, so maybe some areas like Sg. Liang may only be limited to 3G speeds.</p>
<p>In the past two months of testing the ZOOM! the best I&#8217;ve got is about 500KB/s (3.9Mb/s) but its very rare to attain this speed. The advertised &#8216;up to 7.2Mbps&#8217; is really just a marketing gimmick.</p>
<p>I haven&#8217;t had the chance to try out Win7 with ZOOM! yet but I doubt that it&#8217;s due to the OS. I&#8217;ve tried it on 1 desktop and 2 laptops running on XP and all exhibit the same problem (i.e. loss of connectivity after a while).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2439</link>
		<dc:creator><![CDATA[Patrick]]></dc:creator>
		<pubDate>Tue, 16 Mar 2010 09:02:31 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2439</guid>
		<description><![CDATA[I called up 177 and query about the tower in Sungai Liang since i have issued lately with espeed and bmobile which the speed reach maximum of 200kbps only since 9 of march.
Strangely, the staff told me the tower here is only capable of 3.5mbps however i insist explained that it never pass 1mbps for the last few years. The explanation is again, it&#039;s shared among all other user. 

@eric,
I do have that problem on random disconnect few years ago, but it seems resolve for me. Recently i install windows 7 and it&#039;s seem the bmobile never disconnected.]]></description>
		<content:encoded><![CDATA[<p>I called up 177 and query about the tower in Sungai Liang since i have issued lately with espeed and bmobile which the speed reach maximum of 200kbps only since 9 of march.<br />
Strangely, the staff told me the tower here is only capable of 3.5mbps however i insist explained that it never pass 1mbps for the last few years. The explanation is again, it&#8217;s shared among all other user. </p>
<p>@eric,<br />
I do have that problem on random disconnect few years ago, but it seems resolve for me. Recently i install windows 7 and it&#8217;s seem the bmobile never disconnected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2438</link>
		<dc:creator><![CDATA[Eric]]></dc:creator>
		<pubDate>Tue, 16 Mar 2010 05:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2438</guid>
		<description><![CDATA[Yea I agree with Patrick; location is the main issue here. At my office in KB, I can get very good speeds almost all day round without any disconnections. 

However, when I get back to my place at Panaga, eventhough the speeds are okay, I&#039;d get &#039;disconnected&#039; after between 30-60mins of downloads. The modem would state that it&#039;s still connected though, but there&#039;s no packets going in or out, so basically the line is dead. Only way to reconnect is to unplug and reconnect the modem physically. It&#039;s a real hassle having to do that every 30-60mins. 

Called 177 and the technician told me that the Panaga area is very congested and from what I can see, it would take a long time before they can resolve the issue as they have not set up any extra transmission towers to date.

To sum up, I would keep the ZOOM! if:

1. I stayed in KB...or
2. The connection would stay connected at Panaga.]]></description>
		<content:encoded><![CDATA[<p>Yea I agree with Patrick; location is the main issue here. At my office in KB, I can get very good speeds almost all day round without any disconnections. </p>
<p>However, when I get back to my place at Panaga, eventhough the speeds are okay, I&#8217;d get &#8216;disconnected&#8217; after between 30-60mins of downloads. The modem would state that it&#8217;s still connected though, but there&#8217;s no packets going in or out, so basically the line is dead. Only way to reconnect is to unplug and reconnect the modem physically. It&#8217;s a real hassle having to do that every 30-60mins. </p>
<p>Called 177 and the technician told me that the Panaga area is very congested and from what I can see, it would take a long time before they can resolve the issue as they have not set up any extra transmission towers to date.</p>
<p>To sum up, I would keep the ZOOM! if:</p>
<p>1. I stayed in KB&#8230;or<br />
2. The connection would stay connected at Panaga.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2437</link>
		<dc:creator><![CDATA[Patrick]]></dc:creator>
		<pubDate>Tue, 16 Mar 2010 03:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2437</guid>
		<description><![CDATA[My Experience with Zooom! is that it depends on where you stay. As for myself, I tested it in sungai liang, no matter how i tweaked it, my speed can reach maximum 1mbps which is way below the subscribe 3.5speed. 
When i tested the same modem in Kuala Belait, the speed can reach 200kbps like how eric has tested it.
If you have problem on torrenting with Zoom!, it is most probably due to the incoming port issue. However, in Zoom! there is no way you can port forward for your torrent port, since i think bmobile basically block it anyway.
No doubt, you can try to open port with your firewall, just to be in the same side that sometime my bmobile port is open, and sometime it&#039;s closed....]]></description>
		<content:encoded><![CDATA[<p>My Experience with Zooom! is that it depends on where you stay. As for myself, I tested it in sungai liang, no matter how i tweaked it, my speed can reach maximum 1mbps which is way below the subscribe 3.5speed.<br />
When i tested the same modem in Kuala Belait, the speed can reach 200kbps like how eric has tested it.<br />
If you have problem on torrenting with Zoom!, it is most probably due to the incoming port issue. However, in Zoom! there is no way you can port forward for your torrent port, since i think bmobile basically block it anyway.<br />
No doubt, you can try to open port with your firewall, just to be in the same side that sometime my bmobile port is open, and sometime it&#8217;s closed&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thewheat</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2436</link>
		<dc:creator><![CDATA[thewheat]]></dc:creator>
		<pubDate>Sun, 14 Mar 2010 14:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2436</guid>
		<description><![CDATA[@ahjohnlah 3.5G &lt;a href=&#039;http://en.wikipedia.org/wiki/3.5G&#039; rel=&quot;nofollow&quot;&gt;typically goes up to 7.2Mbps&lt;/a&gt; (7.2Mbps is the maximum advertised bandwidth so anything faster on the modem side probably won&#039;t help anyway) and &lt;a href=&quot;http://en.wikipedia.org/wiki/3.75G&quot; rel=&quot;nofollow&quot;&gt;3.75G&lt;/a&gt; seems to be focused on upload rather than download, so I would say no.]]></description>
		<content:encoded><![CDATA[<p>@ahjohnlah 3.5G <a href='http://en.wikipedia.org/wiki/3.5G' rel="nofollow">typically goes up to 7.2Mbps</a> (7.2Mbps is the maximum advertised bandwidth so anything faster on the modem side probably won&#8217;t help anyway) and <a href="http://en.wikipedia.org/wiki/3.75G" rel="nofollow">3.75G</a> seems to be focused on upload rather than download, so I would say no.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ahjohnlah</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2433</link>
		<dc:creator><![CDATA[ahjohnlah]]></dc:creator>
		<pubDate>Sun, 14 Mar 2010 00:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2433</guid>
		<description><![CDATA[halo...now i using zooom 3.5g modem.if i change to 3.75g modem is it faster surfing n downloading????or is the same as usual.]]></description>
		<content:encoded><![CDATA[<p>halo&#8230;now i using zooom 3.5g modem.if i change to 3.75g modem is it faster surfing n downloading????or is the same as usual.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OMNI upgrade prices for existing E-Speed subscribers &#171; The Wheat Field</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2408</link>
		<dc:creator><![CDATA[OMNI upgrade prices for existing E-Speed subscribers &#171; The Wheat Field]]></dc:creator>
		<pubDate>Thu, 18 Feb 2010 01:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2408</guid>
		<description><![CDATA[[...] is a mixed bag of goodness and annoyance as mentioned in my previous findings but for $20/month on top of an existing eSpeed Value Surf subscription, I have to say that OMNI is [...]]]></description>
		<content:encoded><![CDATA[<p>[...] is a mixed bag of goodness and annoyance as mentioned in my previous findings but for $20/month on top of an existing eSpeed Value Surf subscription, I have to say that OMNI is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blog.thewheatfield.org/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2370</link>
		<dc:creator><![CDATA[Eric]]></dc:creator>
		<pubDate>Mon, 18 Jan 2010 06:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://thewheat.wordpress.com/2010/01/16/bmobile-zoom-e-speed-dst-go-findings/#comment-2370</guid>
		<description><![CDATA[Hi there,

utorrent has no problems with the incoming/outgoing connections; only ZOOM! has that problem so I guess they may have blocked the ports on their router.

Will continue to use it for another week or so before I make the final decision. I really wish I can keep it though :)]]></description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>utorrent has no problems with the incoming/outgoing connections; only ZOOM! has that problem so I guess they may have blocked the ports on their router.</p>
<p>Will continue to use it for another week or so before I make the final decision. I really wish I can keep it though :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

