<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Re: New Firmware?  Cellpipe&#x27; in forum &#x27;TekSavvy&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27912575</link>
<description></description>
<language>en</language>
<pubDate>Fri, 24 May 2013 17:25:39 EDT</pubDate>
<lastBuildDate>Fri, 24 May 2013 17:25:39 EDT</lastBuildDate>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913969</link>
<description><![CDATA[JMJimmy posted : I discovered part of the problem:  Enabling DMZ caused the NAT issues.  When I disabled it and switched to port forwarding... poof, XBL NAT errors vanished.<br><br>Go figure.<br><br>Thanks to Phil for providing a more permanent solution!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913969</guid>
<pubDate>Tue, 15 Jan 2013 13:46:56 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913738</link>
<description><![CDATA[JMJimmy posted : <div class="bquote"><said>said by <a href="/profile/273051" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=273051');">HiVolt</a>:</said><p>Well i suggest you check what linksys router you have, it may be possible to load 3rd party firmware on it like Tomato or DD-WRT.<br> </p></div>I've had back luck with Linksys and 3rd party software... bricked 2-3 of them.  If I had the ability to JTAG I'd be more inclined but I don't at the moment.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913738</guid>
<pubDate>Tue, 15 Jan 2013 12:48:39 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913674</link>
<description><![CDATA[TSI PhilR posted : Check your IMs]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913674</guid>
<pubDate>Tue, 15 Jan 2013 12:38:07 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913623</link>
<description><![CDATA[HiVolt posted : Well i suggest you check what linksys router you have, it may be possible to load 3rd party firmware on it like Tomato or DD-WRT.<br><small>--<br>F**K THE NHL. Go Blue Jays 2013!!!<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913623</guid>
<pubDate>Tue, 15 Jan 2013 12:26:38 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913586</link>
<description><![CDATA[JMJimmy posted : Using it as the primary - my router was a linksys which with the zero day exploit in the wild I pulled it.<br><br>I just ran that xbox test again... NAT Error this time<br><br>W: 0000 - 000B<br>X: 0000 - F001<br>Y: 20A8 - 48E0<br>Z: 0000 - 0000<br>ID: 0007 - 0002<br>L: 8015 - 100C<br>Q: 8015 - 100C<br><br>Whatever that means.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913586</guid>
<pubDate>Tue, 15 Jan 2013 12:14:37 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913503</link>
<description><![CDATA[HiVolt posted : Are you using the Cellpipe as your main router for wired & wiress, or only as a bridge device?<br><br>If so, perhaps you should consider a separate router, or perhaps TekSavvy can swap the modem to a Sagemcom which is more modern.<br><small>--<br>F**K THE NHL. Go Blue Jays 2013!!!<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913503</guid>
<pubDate>Tue, 15 Jan 2013 11:54:14 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913462</link>
<description><![CDATA[JMJimmy posted : It's not just to Xbox - websites are sluggish, P2P is having the drop outs at the same time as the xbox disconnects.  It's intermittent and other than that the xbox recovers right away so it's hard to pin down.<br><br>I've pulled everything off the network except 1 new Win8 laptop and the Xbox, directly wired... beyond that I'm not sure how I can log this problem in a meaningful way.<br><br>I ran the "Test Xbox LIVE Connection", without knowing what W/X/Y/Z/ID/L/Q (and corresponding codes) mean it doesn't give any meaningful information.  T = Type, tells me it's wired.  A/G/D is just Gateway/IP/DNS info.  It says I'm "moderate" NAT, however, the IP is in the DMZ so it should be wide open.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913462</guid>
<pubDate>Tue, 15 Jan 2013 11:44:42 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913296</link>
<description><![CDATA[TSI PhilR posted : Well, I'm not really seeing anything in the logs that'd cause this.. I took a look at your line stats and again there I'm not seeing anything wrong either.. <br>Have you tried pings and or traceroutes to XB?<br><br>I found this on another forum (not an Xbox gamer myself so I had to use the google machine)<br><br><i>Xbox with no Disc in it. Once you're in the menu select "Settings" then go to "Network" under this menu it has an option to connect to Xbox Live. Since everything is already working fine and you can play without any problems, go ahead and let it run the Auto-Detecting tests and go through its little processes.<br><br>Once the test finishes (Successfully), press "Y" and see what comes up. It should have a "hidden' type menu that will come up where you can measure your ping and packetloss as well as what NAT type you have.</i><br><small>--<br>TSI PhilR - TekSavvy Solutions Inc.<br>Manager, Escalations, Errors & Recovery<br>Authorized TSI employee ( &raquo;<A HREF="/faq/teksavvy">TekSavvy FAQ</A> &raquo;<A HREF="/faq/14672#14672">Official support in the forum</A> )</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913296</guid>
<pubDate>Tue, 15 Jan 2013 10:58:53 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913200</link>
<description><![CDATA[HiVolt posted : GUI info this firmware is version 1.0.4.4R8-wh<br><br>Looks like you're on the good firmware that was released last year to fix the reboot issues...<br><small>--<br>F**K THE NHL. Go Blue Jays 2013!!!<br></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913200</guid>
<pubDate>Tue, 15 Jan 2013 10:38:06 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913160</link>
<description><![CDATA[TSI PhilR posted : Thanks JMJimmy, taking a look over the log now.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913160</guid>
<pubDate>Tue, 15 Jan 2013 10:26:17 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913099</link>
<description><![CDATA[JMJimmy posted : <div class="bquote"><said>said by <a href="/profile/1615429" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1615429');">TSI PhilR</a>:</said><p>Morning,<br><br>I've reached out to one of my contacts at Bell inquiring about any recent updates to the Cellpipe line, I should hear something back shortly.<br><br>Also, you could check the system log in the cellpipe and see if there are any indications in the log about an update as well.<br><br>If you'd like to make a post in the private forum, and post the log file, I don't mind checking it over for you either.<br> </p></div>Errors/Warnings:<br><br> 	2013-01-14M20:51:25 	PPPOE 	warn 	[PPP35]Couldn't increase MRU to 1500<br>  	2013-01-14M20:52:29 	PPPOE 	warn 	[PPP35]Couldn't increase MTU to 1500<br>  	2013-01-14M20:52:29 	PPPOE 	warn 	[PPP35]Couldn't increase MRU to 1500<br>  	2013-01-14M20:52:40 	VDSL 	notice 	Detect VDSL Link UP...<br>  	2013-01-14M20:52:51 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M20:52:52 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M20:52:52 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M20:52:53 	TR-069 	warn 	acs connectReq: ip=69.196.176.19, port=58603<br>  	2013-01-14M21:01:28 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M21:01:28 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M21:11:16 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M21:11:16 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M21:39:19 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M21:59:38 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M23:01:24 	VDSL 	notice 	Detect VDSL Link UP...<br>  	2013-01-14M23:01:35 	PPPOE 	warn 	[PPP35]Couldn't increase MTU to 1500<br>  	2013-01-14M23:01:35 	PPPOE 	warn 	[PPP35]Couldn't increase MRU to 1500<br>  	2013-01-14M23:03:14 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M23:03:15 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M23:03:16 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M23:03:17 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M23:03:21 	TR-069 	warn 	acs connectReq: ip=75.119.234.24, port=58603<br>  	2013-01-14M23:03:28 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M23:12:19 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M23:12:40 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-14M23:55:00 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-14M23:55:01 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-15T00:04:09 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-15T00:28:39 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-15T00:47:46 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-15T01:30:06 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-15T04:16:40 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714<br>  	2013-01-15T04:16:40 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-15T04:16:41 	UPnP 	err 	Action "GetSpecificPortMappingEntry" invoked, error code 714<br>  	2013-01-15T05:37:36 	UPnP 	err 	Action "DeletePortMapping" invoked, error code 714 <br><br>Info (UPnP & DHCP filtered out)<br><br> 	2013-01-14M20:51:25 	PPPOE 	warn 	[PPP35]Couldn't increase MRU to 1500<br>  	2013-01-14M20:51:25 	PPPOE 	info 	[PPP35]LCP down<br>  	2013-01-14M20:51:31 	PPPOE 	info 	[PPP35]No response from ISP.<br>  	2013-01-14M20:51:31 	PPPOE 	info 	[PPP35]Connection terminated.<br>  	2013-01-14M20:51:32 	PPPOE 	info 	[PPPoE35]Wait for PADT timeout<br>  	2013-01-14M20:51:32 	PPPOE 	info 	[PPPoE35]Sending PADT<br>  	2013-01-14M20:51:33 	PPPOE 	info 	[PPPoE35]Wait for PADT timeout<br>  	2013-01-14M20:51:33 	PPPOE 	info 	[PPP35]Modem hangup<br>  	2013-01-14M20:52:29 	PPPOE 	info 	[PPPoE35]Waiting for PADS packet(timeout=1 secs)<br>  	2013-01-14M20:52:29 	PPPOE 	info 	[PPPoE35]Received PADS packet[len=56]<br>  	2013-01-14M20:52:29 	PPPOE 	info 	[PPPoE35]PPP session is 4142<br>  	2013-01-14M20:52:29 	PPPOE 	info 	[PPP35]Connect: ppp0 <--> eth1.35<br>  	2013-01-14M20:52:29 	PPPOE 	warn 	[PPP35]Couldn't increase MTU to 1500<br>  	2013-01-14M20:52:29 	PPPOE 	warn 	[PPP35]Couldn't increase MRU to 1500<br>  	2013-01-14M20:52:30 	PPPOE 	info 	[PPP35]LCP up<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]PAP authentication succeeded<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]auth_withpeer_success<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]peer from calling number 00:90:1A:A2:44:DE authorized<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]IPCP nak option 3<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]IPCP nak option 129<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]IPCP nak option 131<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]IPCP up<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]local IP address 69.196.176.19<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]remote IP address 0.0.0.0<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]primary DNS address 206.248.154.22<br>  	2013-01-14M20:52:36 	PPPOE 	info 	[PPP35]secondary DNS address 206.248.154.170<br>  	2013-01-14M20:52:40 	VDSL 	notice 	Detect VDSL Link UP...<br>  	2013-01-14M20:52:43 	TR-069 	info 	cwmpc start<br>  	2013-01-14M20:52:43 	TR-069 	info 	randomTime=13436<br>  	2013-01-14M20:52:46 	DNSMASQ 	info 	using nameserver 206.248.154.22#53<br>  	2013-01-14M20:52:53 	TR-069 	info 	Setting cipher list to RSA:DES:SHA+RSA:RC4:SAH+MEDIUM<br>  	2013-01-14M20:52:53 	TR-069 	info 	SSL: Found certificate file or path: /etc/cert, size=109<br>  	2013-01-14M20:52:53 	TR-069 	warn 	acs connectReq: ip=69.196.176.19, port=58603<br>  	2013-01-14M20:53:00 	TR-069 	info 	SSL: connected<br>  	2013-01-14M20:53:00 	TR-069 	info 	InformResponse<br>  	2013-01-14M20:53:00 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M20:53:00 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M20:53:00 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M20:53:01 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M20:53:01 	TR-069 	info 	next inform after 3297 sec<br>  	2013-01-14M21:10:02 	PPPOE 	info 	[PPP35]LCP: missing 1 Echo Replies<br>  	2013-01-14M21:29:36 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-14M21:29:36 	WLAN 	info 	wlan_statistic_tcp_conns : 125<br>  	2013-01-14M21:29:36 	WLAN 	info 	wlan_statistic_udp_conns : 162<br>  	2013-01-14M21:33:02 	PPPOE 	info 	[PPP35]LCP: missing 1 Echo Replies<br>  	2013-01-14M21:45:32 	PPPOE 	info 	[PPP35]LCP: missing 1 Echo Replies<br>  	2013-01-14M21:48:13 	TR-069 	info 	SSL: connected<br>  	2013-01-14M21:48:14 	TR-069 	info 	InformResponse<br>  	2013-01-14M21:48:14 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M21:48:14 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M21:48:14 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M21:48:14 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M21:48:14 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M21:48:15 	TR-069 	info 	next inform after 86383 sec<br>  	2013-01-14M22:14:02 	PPPOE 	info 	[PPP35]LCP: missing 1 Echo Replies<br>  	2013-01-14M22:29:37 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-14M22:29:37 	WLAN 	info 	wlan_statistic_tcp_conns : 114<br>  	2013-01-14M22:29:37 	WLAN 	info 	wlan_statistic_udp_conns : 191<br>  	2013-01-14M22:52:13 	Ethernet 	info 	Link 2 Down - Autonegotiation Enabled<br>  	2013-01-14M22:52:23 	Ethernet 	info 	Link 2 Up - 100Base-TX Full Duplex<br>  	2013-01-14M22:59:44 	GUI 	info 	##### Reboot via GUI ######  // Note at this point laptops worked fine but a directly wired xbox could not connect despite repeated attempts/rebooting the xbox.  Upon doing the manual reboot the Xbox could connect again (for a time).  <br>  	2013-01-14M22:59:04 	WLAN 	info 	Wireless is enabled<br>  	2013-01-14M22:59:19 	GUI 	info 	this firmware is version 1.0.4.4R8-wh<br>  	2013-01-14M22:59:28 	Ethernet 	info 	Link 2 Up - 100Base-TX Full Duplex<br>  	2013-01-14M22:59:28 	Ethernet 	info 	Link 3 Up - 100Base-TX Half Duplex<br>  	2013-01-14M23:01:24 	VDSL 	notice 	Detect VDSL Link UP...<br>  	2013-01-14M23:01:34 	PPPOE 	info 	[PPP35]Looking for the PPPoE connection<br>  	2013-01-14M23:01:35 	PPPOE 	info 	[PPPoE35]Waiting for PADS packet(timeout=1 secs)<br>  	2013-01-14M23:01:35 	PPPOE 	info 	[PPPoE35]Received PADS packet[len=56]<br>  	2013-01-14M23:01:35 	PPPOE 	info 	[PPPoE35]PPP session is 6333<br>  	2013-01-14M23:01:35 	PPPOE 	info 	[PPP35]Connect: ppp0 <--> eth1.35<br>  	2013-01-14M23:01:35 	PPPOE 	warn 	[PPP35]Couldn't increase MTU to 1500<br>  	2013-01-14M23:01:35 	PPPOE 	warn 	[PPP35]Couldn't increase MRU to 1500<br>  	2013-01-14M23:01:35 	PPPOE 	info 	[PPP35]LCP up<br>  	2013-01-14M23:01:41 	PPPOE 	info 	[PPP35]PAP authentication succeeded<br>  	2013-01-14M23:01:41 	PPPOE 	info 	[PPP35]auth_withpeer_success<br>  	2013-01-14M23:01:41 	PPPOE 	info 	[PPP35]peer from calling number 00:90:1A:A2:44:DE authorized<br>  	2013-01-14M23:01:41 	PPPOE 	info 	[PPP35]IPCP nak option 3<br>  	2013-01-14M23:01:41 	PPPOE 	info 	[PPP35]IPCP nak option 129<br>  	2013-01-14M23:01:41 	PPPOE 	info 	[PPP35]IPCP nak option 131<br>  	2013-01-14M23:01:42 	PPPOE 	info 	[PPP35]IPCP up<br>  	2013-01-14M23:01:42 	PPPOE 	info 	[PPP35]local IP address 75.119.234.24<br>  	2013-01-14M23:01:42 	PPPOE 	info 	[PPP35]remote IP address 0.0.0.0<br>  	2013-01-14M23:01:42 	PPPOE 	info 	[PPP35]primary DNS address 206.248.154.22<br>  	2013-01-14M23:01:42 	PPPOE 	info 	[PPP35]secondary DNS address 206.248.154.170<br>  	2013-01-14M23:01:49 	TR-069 	info 	cwmpc start<br>  	2013-01-14M23:01:49 	TR-069 	info 	randomTime=19588<br>  	2013-01-14M23:01:51 	DNSMASQ 	info 	using nameserver 206.248.154.22#53<br>  	2013-01-14M23:03:21 	TR-069 	info 	Setting cipher list to RSA:DES:SHA+RSA:RC4:SAH+MEDIUM<br>  	2013-01-14M23:03:21 	TR-069 	info 	SSL: Found certificate file or path: /etc/cert, size=109<br>  	2013-01-14M23:03:21 	TR-069 	warn 	acs connectReq: ip=75.119.234.24, port=58603<br>  	2013-01-14M23:03:24 	TR-069 	info 	SSL: connected<br>  	2013-01-14M23:03:24 	TR-069 	info 	InformResponse<br>  	2013-01-14M23:03:25 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M23:03:25 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M23:03:25 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M23:03:25 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M23:03:25 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M23:03:25 	TR-069 	info 	GetParameterValues<br>  	2013-01-14M23:03:26 	TR-069 	info 	next inform after 66810 sec<br>  	2013-01-14M23:21:14 	PPPOE 	info 	[PPP35]LCP: missing 1 Echo Replies<br>  	2013-01-15T00:00:47 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T00:00:47 	WLAN 	info 	wlan_statistic_tcp_conns : 129<br>  	2013-01-15T00:00:47 	WLAN 	info 	wlan_statistic_udp_conns : 173<br>  	2013-01-15T01:00:48 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T01:00:48 	WLAN 	info 	wlan_statistic_tcp_conns : 133<br>  	2013-01-15T01:00:48 	WLAN 	info 	wlan_statistic_udp_conns : 159<br>  	2013-01-15T02:00:49 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T02:00:49 	WLAN 	info 	wlan_statistic_tcp_conns : 127<br>  	2013-01-15T02:00:49 	WLAN 	info 	wlan_statistic_udp_conns : 162<br>  	2013-01-15T03:00:50 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T03:00:50 	WLAN 	info 	wlan_statistic_tcp_conns : 135<br>  	2013-01-15T03:00:50 	WLAN 	info 	wlan_statistic_udp_conns : 167<br>  	2013-01-15T04:00:51 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T04:00:51 	WLAN 	info 	wlan_statistic_tcp_conns : 143<br>  	2013-01-15T04:00:51 	WLAN 	info 	wlan_statistic_udp_conns : 163<br>  	2013-01-15T05:00:52 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T05:00:52 	WLAN 	info 	wlan_statistic_tcp_conns : 149<br>  	2013-01-15T05:00:52 	WLAN 	info 	wlan_statistic_udp_conns : 158<br>  	2013-01-15T05:26:44 	PPPOE 	info 	[PPP35]LCP: missing 1 Echo Replies<br>  	2013-01-15T06:00:53 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T06:00:53 	WLAN 	info 	wlan_statistic_tcp_conns : 136<br>  	2013-01-15T06:00:53 	WLAN 	info 	wlan_statistic_udp_conns : 166<br>  	2013-01-15T07:00:54 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T07:00:54 	WLAN 	info 	wlan_statistic_tcp_conns : 112<br>  	2013-01-15T07:00:54 	WLAN 	info 	wlan_statistic_udp_conns : 206<br>  	2013-01-15T08:00:55 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T08:00:55 	WLAN 	info 	wlan_statistic_tcp_conns : 119<br>  	2013-01-15T08:00:55 	WLAN 	info 	wlan_statistic_udp_conns : 187<br>  	2013-01-15T09:00:56 	Ethernet 	info 	A large number of connections have been detected<br>  	2013-01-15T09:00:56 	WLAN 	info 	wlan_statistic_tcp_conns : 113<br>  	2013-01-15T09:00:56 	WLAN 	info 	wlan_statistic_udp_conns : 178 <br><br>No packet loss that I've noticed - solid 13-43ms 0% loss.  Everything is sluggish even when I disable P2P.  I can't stay connected to XBL for more than 30 minutes at a time before I get kicked off... it's very strange.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913099</guid>
<pubDate>Tue, 15 Jan 2013 10:13:04 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913043</link>
<description><![CDATA[Phibian posted : Check for packet loss.  May well be this issue: &raquo;<A HREF="/forum/r27781822-DSL-Network-congestion-tonight-">[DSL] Network congestion tonight?</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27913043</guid>
<pubDate>Tue, 15 Jan 2013 09:53:53 EDT</pubDate>
</item>

<item>
<title>Re: New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27912856</link>
<description><![CDATA[TSI PhilR posted : Morning,<br><br>I've reached out to one of my contacts at Bell inquiring about any recent updates to the Cellpipe line, I should hear something back shortly.<br><br>Also, you could check the system log in the cellpipe and see if there are any indications in the log about an update as well.<br><br>If you'd like to make a post in the private forum, and post the log file, I don't mind checking it over for you either.<br><small>--<br>TSI PhilR - TekSavvy Solutions Inc.<br>Manager, Escalations, Errors & Recovery<br>Authorized TSI employee ( &raquo;<A HREF="/faq/teksavvy">TekSavvy FAQ</A> &raquo;<A HREF="/faq/14672#14672">Official support in the forum</A> )</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-New-Firmware-Cellpipe-27912856</guid>
<pubDate>Tue, 15 Jan 2013 08:40:02 EDT</pubDate>
</item>

<item>
<title>New Firmware?  Cellpipe</title>
<link>http://www.dslreports.com/forum/New-Firmware-Cellpipe-27912575</link>
<description><![CDATA[JMJimmy posted : I've had no issues since my initial setup woes but all of the sudden I'm being disconnected from XBL constantly, 3 disconnects in one day on my PCs, P2P is all over the place (uploading at 400kbps+ one moment, 0kbps the next).  <br><br>Last time this sort of thing happened it was due to a bug in the cellpipe firmware that took Bhell forever to fix.  Is there anyway to tell if Bhell has updated mine recently?  (and if so can it be rolled back?)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/New-Firmware-Cellpipe-27912575</guid>
<pubDate>Tue, 15 Jan 2013 02:06:30 EDT</pubDate>
</item>

</channel>
</rss>
