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

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

<channel>
<title>Re: Netopia 33xx routers and high upchannel utilization in AT&#x26;T Midwest</title>
<link>http://www.dslreports.com/forum/r21046440</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 14:31:58 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 14:31:58 EDT</lastBuildDate>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21178174</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : Radiodoc used:<br><br>Efficient Networks 5861, symptom was no traffic and inability to reconnect/re-establish connection without power cycling.  The CPE thought it had a connection when it didn't.  Theory:  Modem chip locked up since UI and telnet were their usual snappy selves.<br><br>Efficient Networks 4200, symptom was near-complete lockup of unit.  UI was sort of accessible if you wanted to wait 5 minutes for each page load.  As many as 50 spontaneous hardware reboots an hour.  Traffic slowed to bits-per-second pace on WAN side.  CRC errors on upstream into the hundreds of thousands.  Zero on downstream.<br><br>2-Wire 1701HG, symptom was almost the same as Efficient 4200 except that traffic just stopped.  Also dozens of restarts an hour, sometimes more than once per minute.<br><br>Broadxent router (forgot the model number) would just lock up.<br><br>Westell 2200, symptom was negative s/n (-125 dB) on upstream, connection would drop without modem being able to tell and reconnect, eventual total lockup.<br><br>Efficient 5660, would gallantly keep reconnecting when it detected a problem but this resulted in hundreds of reconnects a day.  Eventually even it would stop trying.<br><br>Replacing the RT card stopped it all immediately.  AT&T tech told me that this is a known problem with those particular cards and he was going to try to get a "new" one from the garage.  Unfortunately my brother in law must have gotten my old one because his connection, fed from the same equipment, went to hell a couple of months ago.  Solution:  New RT card.<br><br>I am currently using the 2-Wire and have had precisely zero problems since the card was replaced.  Coincidence?  Nope.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21178174</guid>
<pubDate>Sat, 27 Sep 2008 13:53:08 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21169646</link>
<description><![CDATA[<A HREF="/useremail/u/411904"><b>gdm</b></A> : I don't think so.  I'd be curious to see what CPE's Doc used but right now I tried two different ones.  <br><br>I was in that townhouse for 19 months and it happened twice.  I have heard from the techs the cards can go bad in the RT's, at least my CEV could get over heated.  I can't remember exactly but I think it was within 2-3 months of each other.<br><br>I just don't think it's a vendor issue if it was we would have seen this pop up much more.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21169646</guid>
<pubDate>Thu, 25 Sep 2008 21:06:16 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21169557</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Radiodoc said he'd used CPE from several different vendors as well.<br><br>So should it really be a vendor issue?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21169557</guid>
<pubDate>Thu, 25 Sep 2008 20:47:31 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21169481</link>
<description><![CDATA[<A HREF="/useremail/u/411904"><b>gdm</b></A> : Glad to hear things are stable again.  When I crashed I was using the 5100a and a zyxel 643.  Not sure which one was the first vs the second.<br><br>I believe with the 643 I had more issues since it held sync a bit better then the 5100a.  The 5100a I had to physically unplug it in order for it to work.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21169481</guid>
<pubDate>Thu, 25 Sep 2008 20:33:30 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21169334</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : You'd need to have the vendor perform a FAR to ever figure out the true cause. Also without any debugs or access to the device I couldn't even hazard a guess.<br><br>well...on second though, I can hazard a guess. I guess an evil leprechaun was giving it a dirty look.<br><small>--<br><A HREF="http://www.dennisjudd.com">My Blog. Because I desperately need the acknowledgement of others.</a><br><br><A HREF="http://www.dennisjudd.com/juddfamily">Visit the Judd Family website to see my kids!</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21169334</guid>
<pubDate>Thu, 25 Sep 2008 20:02:51 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21169194</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Profile has been back to a 768K up channel for some time now, DNS settings are back to where they were, and there is no overflow problem with the router's NAT tables.<br><br>100% convinced the problem was fixed with the installation of a new RT card, as Radiodoc and gdm had said.<br><br>Now, anyone have any idea why this happened?  Please note, this actually caused the Netopia CPE to crash hard.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21169194</guid>
<pubDate>Thu, 25 Sep 2008 19:31:34 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21114001</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I'll pass the final word on that when the profile goes back to a 768 up channel.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21114001</guid>
<pubDate>Mon, 15 Sep 2008 15:37:05 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21113979</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : Swapping the RT card woulnd't effect the NAT table...<br><br>Still don't understand the actual problem, but at least your clients problem seems to have been resolved for now.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21113979</guid>
<pubDate>Mon, 15 Sep 2008 15:32:15 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21113927</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Nope, but it turns out that's not really the problem either.  I set DNS back to the old way, and it still kept going even when the table held 3200 entries.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21113927</guid>
<pubDate>Mon, 15 Sep 2008 15:24:54 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21113243</link>
<description><![CDATA[<A HREF="/useremail/u/1029026"><b>koma3504</b></A> :  Thanks Glad the issue has been fixed.<br>Did it fix any of the high nat table being used??]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21113243</guid>
<pubDate>Mon, 15 Sep 2008 13:27:35 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21113238</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Still no failure.<br><br>If it makes it through tomorrow afternoon, I'm going to say the problem is solved.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21113238</guid>
<pubDate>Mon, 15 Sep 2008 13:26:11 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21113230</link>
<description><![CDATA[<A HREF="/useremail/u/1029026"><b>koma3504</b></A> :  How is that new RT card working out for you??]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21113230</guid>
<pubDate>Mon, 15 Sep 2008 13:24:41 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21092861</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : You got me, but so far, it's working.<br><br>Got a new card in yesterday.<br><br>I'm betting there's a component somewhere on the card that doesn't perform as well due to heat, or time.<br><br>Assuming that's the problem here.  It was for Radiodoc and gdm, and they hardly ever agree on anything.  ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21092861</guid>
<pubDate>Thu, 11 Sep 2008 09:49:34 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21086206</link>
<description><![CDATA[<A HREF="/useremail/u/1029026"><b>koma3504</b></A> :  Simple if it is a Bad RT card it is BAd and is not working as it  should. And would then Malform the packets Coming and going though the port on the Card. Enough Malformed packets can lock any thing up. I just hooked up My NEtopia And all hell broke loose. <br><br> The Mail Server if it sends out Allot of email all @ once could be Causeing the Card to heat up and fail.<br><br> You could Try a Simple test Un hook All the phone wires AT the NID for An hour or so And see if letting the Card cools off improves anything.<br><br> By chance have you checked your ground To the NID it is supposed to be 25 Oms or less According to the NFPA And take note if it flucuates alot as well.<br><br> It is worth checking to see even if it is good.<br><br>&raquo;<A HREF="http://www.nfpa.org/assets/files/PDF/ne&middot;&middot;&middot;raft.pdf" >www.nfpa.org/assets/files/PDF/ne&middot;&middot;&middot;raft.pdf</A><br><br>minumum of a 5 foot rod that is 1/2 inch in diamater in wet soil conditions.<br><br>800.40 b 3 minumum of 6awg for ground wire. the grounding conductor shall be run to the grounding electrode in as straight a line as practical.<br>you also want the least resistance.<br><br>250.56 Resistance of Rod, Pipe, and Plate Electrodes. A<br>single electrode consisting of a rod, pipe, or plate that does<br>not have a resistance to ground of 25 ohms or less shall be<br>augmented by one additional electrode of any of the types<br>specified by 250.52(A)(2) through (A)(7). Where multiple<br>rod, pipe, or plate electrodes are installed to meet the requirements<br>of this section, they shall not be less than 1.8 m<br>(6 ft) apart.<br>FPN: The paralleling efficiency of rods longer than 2.5 m<br>(8 ft) is improved by spacing greater than 1.8 m (6 ft).<br><br>(4) Clearance Supply service drops of 0&#150;750 volts running<br>above and parallel to communications service drops<br>shall have a minimum separation of 300 mm (12 in.) at any<br>point in the span, including the point of and at their attachment<br>to the building, provided the nongrounded conductors<br>are insulated and that a clearance of not less than 1.0 m<br>(40 in.) is maintained between the two services at the pole.<br><br>800.25 Abandoned Cables. the accessible portion of abandoned communications cables shall be removed. [ROP 16-128, 16-129, 16-130]<br><small>--<br>&#134; Koma &#134;<br><b><i>If YOu Don't Think It's Possable!! It's Acually A Reality!!The best way to predict the future is to invent it. Alan Kay!!<br>Ya Don't Know The signal Till Ya Ride It!!<br>Voice Break's There's Trouble!!!!</b></i></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21086206</guid>
<pubDate>Wed, 10 Sep 2008 02:23:20 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21083198</link>
<description><![CDATA[<A HREF="/useremail/u/603962"><b>StillLearn</b></A> : A dumb questions from a naive observer: why should a problem with an RT card, or anything else out of the premises, make a router hang up to where its interface cannot be accessed?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21083198</guid>
<pubDate>Tue, 09 Sep 2008 15:50:15 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21082991</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Okay, bad news.<br><br>Changing the resolv.conf last week to use 68.94.156.1<br>and 68.94.157.1 as nameservers didn't solve the Netopia freezing problem.<br><br>They sent out an e-mail yesterday, and it crashed within half an hour, and today within an hour.  It was fine from Thursday evening through Monday, when they weren't sending.<br><br>Are we back to thinking it's the RT card at this point?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21082991</guid>
<pubDate>Tue, 09 Sep 2008 15:17:00 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21068502</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : The funny thing is, remember when I asked you about Bittorrent on the phone? Same kind of scenario's really, except maybe in reverse....hundreds of packets overflowing some memory buffer or triggering a bug.<br><br>You'd make a good stress tester apparently....want to beta the next Microsoft OS? :D<br><small>--<br><A HREF="http://www.dennisjudd.com">My Blog. Because I desperately need the acknowledgement of others.</a><br><br><A HREF="http://www.dennisjudd.com/juddfamily">Visit the Judd Family website to see my kids!</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21068502</guid>
<pubDate>Sat, 06 Sep 2008 14:42:31 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21067973</link>
<description><![CDATA[<A HREF="/useremail/u/1348016"><b>DNSguy</b></A> : <div class="bquote"><small>said by  lev <A HREF="/useremail/u/399707"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>I still don't see why the Netopia routers don't have a setting to tell them not to give a damn about DNS.<br></div>I don't think the Netopia give a damn about DNS, it's that it has to NAT all those outbound connections the internal server is using to make DNS lookups.  The same thing would happen on your D-Link if you turned off the DNS relay and ran a server behind it also running a mailing list.  As long as you are using a private IP for the server, it's going to have to NAT for any type of outbound request.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21067973</guid>
<pubDate>Sat, 06 Sep 2008 12:20:51 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21067929</link>
<description><![CDATA[<A HREF="/useremail/u/1348016"><b>DNSguy</b></A> : There would be no way to pass the DNS IP's from the CPE, this configuration would require a hard coding.<br><br>From reading this topic, I have the following assumptions, if any of these are wrong, let me know.<br>1) The Linux server you mentioned is running a nameserver, and it's BIND 9.<br>2) The namserver is used for caching only, and is not authoritative for any domains.<br>2) The resolv.conf on that box used to point to localhost, which is why it was making so many outbound DNS connections when the mail list was running.<br>3) You changed the resolv.conf to point to the anycast servers.<br><br>Did I get anything wrong?<br><br>To set up forwarding, look for the options section in the named.conf file.<br>Within the options section, add the following lines:<br><br>forward only;<br>forwarders { IP1; IP2; IP3; };<br><br>then either stop / start named or do an rndc reconfig<br><br>You can use the IP's of any rescursive DNS server you want, even OpenDNS.   :(<br>I probably would not put more than 3 IP's in that list.<br><br>With this configuration, the nameserver will ask the forwarders for any information it does not have in cache instead of doing the recursive lookup itself.  Recursive lookups can open up a lot of outbound ports, as you have to contact the root name servers, then the authoritative box for that domain.  Let me know if this helps at all.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21067929</guid>
<pubDate>Sat, 06 Sep 2008 12:13:11 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21067544</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Shame you're limiting yourself to beer.  Lot of nice 9+% abv ales out there.  :)<br><br>I still don't see why the Netopia routers don't have a setting to tell them not to give a damn about DNS.<br><br>I have an inexpensive little D-Link wireless router I use inside my own LAN, that has an on/off DNS relay option that states:<br><br>"When DNS Relay is enabled, the router plays the role of a DNS server. DNS requests sent to the router are forwarded to the ISP's DNS server. This provides a constant DNS address that LAN computers can use, even when the router obtains a different DNS server address from the ISP upon re-establishing the WAN connection. You should disable DNS relay if you implement a LAN-side DNS server as a virtual server."<br><br>Why is there no similar defeat for managing DNS on the Netopias?  It's a product provided specifically for multiple static IP support, where there'd be a much greater chance of people putting servers up.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21067544</guid>
<pubDate>Sat, 06 Sep 2008 10:25:20 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21067478</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : <div class="bquote"><small>said by  lev <A HREF="/useremail/u/399707"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>Um...<br><small>Someone protect me?</small><br> </div>I'll be happy to help in exchange for a six pack of beer with at least 9% abv.  ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21067478</guid>
<pubDate>Sat, 06 Sep 2008 10:11:39 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21067234</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Um...<br><br>Err...<br><br><small>Someone protect me?</small><br><br>Seriously, thanks for jumping in.  That'd be a good idea, but would I have to hard code the DNS information by IP address, or would there be a way to do it with whatever information is passed to the CPE for that connection?<br><br>I rarely do more than configure zone files in BIND, so I DEFINITELY bow down to your expertise.  Tell me what to change, and where, and I'll do it.<br><br><div class="bquote"><small>said by  DNSguy <A HREF="/useremail/u/1348016"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>"10 minutes after changing to the anycast (yuck) servers"<br><br>Oh I see how it is.  Insult my servers, then use them to run a mailing list.  What was that account name, so I can make some "performance adjustments"?   :)<br><br>You can always turn up BIND on that Linux server, with a forward only config to the anycast IP.  Then every look up would stay internal and the anycast server would only be used if the entry was not already cached.  I imagine that would cut down the traffic quite a bit.<br> </div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21067234</guid>
<pubDate>Sat, 06 Sep 2008 08:50:16 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21064905</link>
<description><![CDATA[<A HREF="/useremail/u/1348016"><b>DNSguy</b></A> : "10 minutes after changing to the anycast (yuck) servers"<br><br>Oh I see how it is.  Insult my servers, then use them to run a mailing list.  What was that account name, so I can make some "performance adjustments"?   :)<br><br>You can always turn up BIND on that Linux server, with a forward only config to the anycast IP.  Then every look up would stay internal and the anycast server would only be used if the entry was not already cached.  I imagine that would cut down the traffic quite a bit.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21064905</guid>
<pubDate>Fri, 05 Sep 2008 19:15:17 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21061761</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : Then give the router running bind a public IP address instead of a private LAN IP....that should bypass the NAT.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21061761</guid>
<pubDate>Fri, 05 Sep 2008 10:49:30 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21061545</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Yes, but they're pretty much dooming the router to eventual failure if there's enough DNS lookups over a short period of time from a locally hosted server configured with NAT.<br><br>There should be an option to exclude the router from tracking DNS.  The computer running BIND should take care of that.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21061545</guid>
<pubDate>Fri, 05 Sep 2008 09:58:50 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21059455</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : because they are sourcing from a LAN port? that's what it looks like to me anyways.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21059455</guid>
<pubDate>Thu, 04 Sep 2008 21:27:08 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21058616</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : That we will.<br><br>I'm also going to try to figure out why the NAT even needs to track DNS requests.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21058616</guid>
<pubDate>Thu, 04 Sep 2008 19:04:38 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21058198</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : You haven't dropped any packets on that circuit....I've been watching all afternoon since we talked.<br><br>Guess we'll see next week?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21058198</guid>
<pubDate>Thu, 04 Sep 2008 17:52:11 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21058084</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Sigh,<br><br>I just noticed that the server had finished sending out the mailing list at 3:35, so nothing formal was determined... but it still looks pretty damn likely.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21058084</guid>
<pubDate>Thu, 04 Sep 2008 17:33:26 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057761</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I did more checking.<br><br>Most of addresses seem to be within the blocks of sites that they're mailing to.  I can't stop the lookups unless I change their server to use an outside DNS.<br><br>I'll change the resolv.conf file temporarily and see if that addresses things.<br><br>----<br><br>edit: 10 minutes after changing to the anycast (yuck) servers, and the IP NAT used list number went from over 2000 (seems like it crashes somewhere around 2500) to 367.<br><br>If the router doesn't lose its connection, then at least I have a short-term solution.  Still, the router SHOULD be better able to address a significant number of DNS calls from a local server without dying.<br><br>Thanks everyone for the help so far... I'll keep you posted!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057761</guid>
<pubDate>Thu, 04 Sep 2008 16:26:48 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057637</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : <div class="bquote"><small>said by  lev <A HREF="/useremail/u/399707"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>I honestly don't know why it's keeping track of so much information in its NAT table.<br> </div>yes, but you won't have to know why if you can figure out how to stop that server from pumping queries out like crazy.<br><small>--<br><A HREF="http://www.dennisjudd.com">My Blog. Because I desperately need the acknowledgement of others.</a><br><br><A HREF="http://www.dennisjudd.com/juddfamily">Visit the Judd Family website to see my kids!</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057637</guid>
<pubDate>Thu, 04 Sep 2008 16:07:07 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057623</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I'm sitting here now watching the "IP NAT used list" number climb again.<br><br>It would make some sense that, if it dies when that number gets high enough, that turning off NAT might be another possible solution.  Not exactly loving the idea, but it also could stop the router from crashing.  I honestly don't know why it's keeping track of so much information in its NAT table.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057623</guid>
<pubDate>Thu, 04 Sep 2008 16:05:02 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057524</link>
<description><![CDATA[<A HREF="/useremail/u/267904"><b>drmorley</b></A> : Give Postini a shot.  It's basically free ($3/year) and you can offload all that garbage to Google's servers.  I use it for bulk spam and it's fantastic.<br><small>--<br>&raquo;<A HREF="http://mediafly.com/Welcome.aspx" >mediafly.com/Welcome.aspx</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057524</guid>
<pubDate>Thu, 04 Sep 2008 15:45:09 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057489</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I've come to that solution as well.  They're not sending out another mailing until Monday, so I'll leave the DNS blacklist up until then, as well as research solutions for a way to download a blacklist file to their server on a daily/hourly basis, so that the router won't have to work so hard.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057489</guid>
<pubDate>Thu, 04 Sep 2008 15:39:23 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057479</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : I noticed that too, but figured he knows what he's doing.  Seems that it really should be going to a local cache instead of hammering the outbound channel and NAT table like that.<br><small>--<br>Toolmaster of La Grange.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057479</guid>
<pubDate>Thu, 04 Sep 2008 15:37:37 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057410</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : What about throttling it back? There must be a parameter somewhere that controls how many lookups/requests it can perform at a given moment.<br><br>Plus the one thing that confuses me is this....why are the port 53 requests all going out to different domains? Why aren't they going to AT&T's DNS servers, or to the Netopia itself?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057410</guid>
<pubDate>Thu, 04 Sep 2008 15:25:10 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057385</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : Well, you <i>could</i> turn that off and see what happens...especially considering the coincidental relationship between the increase in spam blocks and the router troubles.  That kind of traffic may require a "real" router.<br><small>--<br>Toolmaster of La Grange.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057385</guid>
<pubDate>Thu, 04 Sep 2008 15:19:44 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057317</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Yes, I've used putty and the command line, with a show-all command.  It's the best way to get into the router from remote.  I shell into the server and then telnet into the router from the LAN.<br><br>For what it's worth, to be more specific, many of those DNS lookups seem to be coming from the following line in the sendmail.mc file:<br><br><textarea name="code" class="text" cols=50 rows=10>FEATURE(dnsbl, `zen.spamhaus.org', `"Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip="$&amp;{client_addr}')dnl&#012;</textarea><!--end code block-->Obviously, invoking the DNSBL lookup is important, as witnessed below.  It blocked 34 nefarious incoming spam attempts in 2 1/2 minutes, which on a weekly basis, works out to 137,000 avoided e-mail connections.  This too, could be the problem, as the server was only blocking about 30,000 attempts a few months ago.<br><br><textarea name="code" class="text" cols=50 rows=10> tail -1000 /var/log/maillog | grep spamhaus&#012;Sep  4 13:56:49 mail sendmail&#91;29306&#93;: ruleset=check_relay, arg1=&#91;200.24.5.118&#93;, arg2=127.0.0.4, relay=&#91;200.24.5.118&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=200.24.5.118&#012;Sep  4 13:57:03 mail sendmail&#91;29388&#93;: ruleset=check_relay, arg1=&#91;190.176.70.230&#93;, arg2=127.0.0.4, relay=190-176-70-230.speedy.com.ar &#91;190.176.70.230&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=190.176.70.230&#012;Sep  4 13:57:08 mail sendmail&#91;29419&#93;: ruleset=check_relay, arg1=bd21dd58.virtua.com.br, arg2=127.0.0.4, relay=bd21dd58.virtua.com.br &#91;189.33.221.88&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=189.33.221.88&#012;Sep  4 13:57:12 mail sendmail&#91;29444&#93;: ruleset=check_relay, arg1=&#91;88.232.211.18&#93;, arg2=127.0.0.10, relay=&#91;88.232.211.18&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=88.232.211.18&#012;Sep  4 13:57:12 mail sendmail&#91;29447&#93;: ruleset=check_relay, arg1=cable-87-116-164-44.dynamic.sbb.rs, arg2=127.0.0.11, relay=cable-87-116-164-44.dynamic.sbb.rs &#91;87.116.164.44&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=87.116.164.44&#012;Sep  4 13:57:14 mail sendmail&#91;29456&#93;: ruleset=check_relay, arg1=&#91;118.131.150.2&#93;, arg2=127.0.0.4, relay=&#91;118.131.150.2&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=118.131.150.2&#012;Sep  4 13:57:20 mail sendmail&#91;29484&#93;: ruleset=check_relay, arg1=&#91;190.87.70.145&#93;, arg2=127.0.0.11, relay=&#91;190.87.70.145&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=190.87.70.145&#012;Sep  4 13:57:28 mail sendmail&#91;29526&#93;: ruleset=check_relay, arg1=&#91;189.70.183.40&#93;, arg2=127.0.0.4, relay=18970183040.user.veloxzone.com.br &#91;189.70.183.40&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=189.70.183.40&#012;Sep  4 13:57:29 mail sendmail&#91;29533&#93;: ruleset=check_relay, arg1=ner-as23111.alshamil.net.ae, arg2=127.0.0.11, relay=ner-as23111.alshamil.net.ae &#91;217.164.250.251&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=217.164.250.251&#012;Sep  4 13:57:30 mail sendmail&#91;29546&#93;: ruleset=check_relay, arg1=&#91;189.70.183.40&#93;, arg2=127.0.0.11, relay=18970183040.user.veloxzone.com.br &#91;189.70.183.40&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=189.70.183.40&#012;Sep  4 13:57:50 mail sendmail&#91;29591&#93;: ruleset=check_relay, arg1=&#91;92.98.45.180&#93;, arg2=127.0.0.4, relay=&#91;92.98.45.180&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=92.98.45.180&#012;Sep  4 13:57:52 mail sendmail&#91;29642&#93;: ruleset=check_relay, arg1=pool-96-227-51-60.phlapa.fios.verizon.net, arg2=127.0.0.4, relay=pool-96-227-51-60.phlapa.fios.verizon.net &#91;96.227.51.60&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=96.227.51.60&#012;Sep  4 13:57:54 mail sendmail&#91;29648&#93;: ruleset=check_relay, arg1=82.131.223.223.pool.invitel.hu, arg2=127.0.0.11, relay=82.131.223.223.pool.invitel.hu &#91;82.131.223.223&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=82.131.223.223&#012;Sep  4 13:58:08 mail sendmail&#91;29702&#93;: ruleset=check_relay, arg1=dae66581.now.mfnet.ne.jp, arg2=127.0.0.4, relay=dae66581.now.mfnet.ne.jp &#91;218.230.101.129&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=218.230.101.129&#012;Sep  4 13:58:08 mail sendmail&#91;29710&#93;: ruleset=check_relay, arg1=&#91;85.102.138.135&#93;, arg2=127.0.0.4, relay=dsl85-102-35463.ttnet.net.tr &#91;85.102.138.135&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=85.102.138.135&#012;Sep  4 13:58:08 mail sendmail&#91;29709&#93;: ruleset=check_relay, arg1=&#91;85.102.138.135&#93;, arg2=127.0.0.4, relay=dsl85-102-35463.ttnet.net.tr &#91;85.102.138.135&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=85.102.138.135&#012;Sep  4 13:58:09 mail sendmail&#91;29722&#93;: ruleset=check_relay, arg1=&#91;118.131.150.2&#93;, arg2=127.0.0.4, relay=&#91;118.131.150.2&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=118.131.150.2&#012;Sep  4 13:58:18 mail sendmail&#91;29754&#93;: ruleset=check_relay, arg1=&#91;118.131.150.2&#93;, arg2=127.0.0.4, relay=&#91;118.131.150.2&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=118.131.150.2&#012;Sep  4 13:58:20 mail sendmail&#91;29761&#93;: ruleset=check_relay, arg1=&#91;118.131.150.2&#93;, arg2=127.0.0.4, relay=&#91;118.131.150.2&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=118.131.150.2&#012;Sep  4 13:58:21 mail sendmail&#91;29753&#93;: ruleset=check_relay, arg1=&#91;77.76.12.231&#93;, arg2=127.0.0.4, relay=&#91;77.76.12.231&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=77.76.12.231&#012;Sep  4 13:58:21 mail sendmail&#91;29766&#93;: ruleset=check_relay, arg1=&#91;88.230.68.210&#93;, arg2=127.0.0.4, relay=dsl88.230-17618.ttnet.net.tr &#91;88.230.68.210&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=88.230.68.210&#012;Sep  4 13:58:21 mail sendmail&#91;29773&#93;: ruleset=check_relay, arg1=&#91;118.131.150.2&#93;, arg2=127.0.0.4, relay=&#91;118.131.150.2&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=118.131.150.2&#012;Sep  4 13:58:25 mail sendmail&#91;29799&#93;: ruleset=check_relay, arg1=cable-87-116-164-44.dynamic.sbb.rs, arg2=127.0.0.4, relay=cable-87-116-164-44.dynamic.sbb.rs &#91;87.116.164.44&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=87.116.164.44&#012;Sep  4 13:58:28 mail sendmail&#91;29814&#93;: ruleset=check_relay, arg1=host86-159-137-29.range86-159.btcentralplus.com, arg2=127.0.0.4, relay=host86-159-137-29.range86-159.btcentralplus.com &#91;86.159.137.29&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=86.159.137.29&#012;Sep  4 13:58:36 mail sendmail&#91;29839&#93;: ruleset=check_relay, arg1=&#91;201.10.88.224&#93;, arg2=127.0.0.4, relay=201-10-88-224.pgosm7006.dsl.brasiltelecom.net.br &#91;201.10.88.224&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=201.10.88.224&#012;Sep  4 13:59:05 mail sendmail&#91;29980&#93;: ruleset=check_relay, arg1=&#91;189.12.163.21&#93;, arg2=127.0.0.11, relay=18912163021.user.veloxzone.com.br &#91;189.12.163.21&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=189.12.163.21&#012;Sep  4 13:59:06 mail sendmail&#91;29981&#93;: ruleset=check_relay, arg1=athedsl-408816.home.otenet.gr, arg2=127.0.0.10, relay=athedsl-408816.home.otenet.gr &#91;79.131.148.238&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=79.131.148.238&#012;Sep  4 13:59:09 mail sendmail&#91;29982&#93;: ruleset=check_relay, arg1=72.19.191.90.dyn.estpak.ee, arg2=127.0.0.4, relay=72.19.191.90.dyn.estpak.ee &#91;90.191.19.72&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=90.191.19.72&#012;Sep  4 13:59:10 mail sendmail&#91;29983&#93;: ruleset=check_relay, arg1=72.19.191.90.dyn.estpak.ee, arg2=127.0.0.11, relay=72.19.191.90.dyn.estpak.ee &#91;90.191.19.72&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=90.191.19.72&#012;Sep  4 13:59:12 mail sendmail&#91;29984&#93;: ruleset=check_relay, arg1=cable-87-116-164-44.dynamic.sbb.rs, arg2=127.0.0.11, relay=cable-87-116-164-44.dynamic.sbb.rs &#91;87.116.164.44&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=87.116.164.44&#012;Sep  4 13:59:14 mail sendmail&#91;29985&#93;: ruleset=check_relay, arg1=&#91;118.71.173.135&#93;, arg2=127.0.0.11, relay=adsl-dynamic-pool-xxx.fpt.vn &#91;118.71.173.135&#93; (may be forged), reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=118.71.173.135&#012;Sep  4 13:59:18 mail sendmail&#91;30012&#93;: ruleset=check_relay, arg1=80.244.137.192.mielec137.tnp.pl, arg2=127.0.0.11, relay=80.244.137.192.mielec137.tnp.pl &#91;80.244.137.192&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=80.244.137.192&#012;Sep  4 13:59:20 mail sendmail&#91;30021&#93;: ruleset=check_relay, arg1=dsl-243-191-18.telkomadsl.co.za, arg2=127.0.0.11, relay=dsl-243-191-18.telkomadsl.co.za &#91;41.243.191.18&#93;, reject=553 5.3.0 Rejected due to open relay - see http://www.spamhaus.org/query/bl?ip=41.243.191.18&#012;</textarea><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057317</guid>
<pubDate>Thu, 04 Sep 2008 15:08:13 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057045</link>
<description><![CDATA[<A HREF="/useremail/u/1029026"><b>koma3504</b></A> :  Yes I would say that the Nat table is is over loading with all those Dns Lookups. That is the exact same behavier I have seen with every Netopia I have had.<br><br> The only way I have found to fix that was to put up a modem in bridge mode and let a linux box/Smoothwall IpCop etc... do the PPPoE<br><br> Those stats your'e getting on your netopia Are we to assumme that you get those by Telneting in to the Netopia.<br><br> If not Have you tried telneting in to the netopia using something like putty etc... ??<br><small>--<br>&#134; Koma &#134;<br><b><i>If YOu Don't Think It's Possable!! It's Acually A Reality!!The best way to predict the future is to invent it. Alan Kay!!<br>Ya Don't Know The signal Till Ya Ride It!!<br>Voice Break's There's Trouble!!!!</b></i></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057045</guid>
<pubDate>Thu, 04 Sep 2008 14:19:27 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057012</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Apache's running, but it's only in support of mailman.<br><br>Thanks for the reminder... I closed TCP 80 and 443 ports on the firewall.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057012</guid>
<pubDate>Thu, 04 Sep 2008 14:12:44 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21057006</link>
<description><![CDATA[<A HREF="/useremail/u/1323812"><b>reddog6102</b></A> : I was thinking the power output on the upstream looked very high myself being so close to the dslam.What i would look at is the house cable from the dslam to the router.Is it old,bridgetap,various t1's working close by.As far as the ip route you posted,thats beyond my paygrade/scope of work!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21057006</guid>
<pubDate>Thu, 04 Sep 2008 14:11:11 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056992</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : It also seems to be running a webserver....]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056992</guid>
<pubDate>Thu, 04 Sep 2008 14:08:42 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056965</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Yes, it's running Linux, and no, it's not trying to be a root server.  It's just sending out to a mailing list, and doing its own lookups for each site.<br><br>Also, it's rejecting connections from incoming mail servers that are open relays at a pretty startling rate... approximately 110,000 blocked connection attempts per week.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056965</guid>
<pubDate>Thu, 04 Sep 2008 14:01:28 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056915</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : wow....is that server on 192.168.254.19 running unix/bind and trying to be a DNS root server or something crazy?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056915</guid>
<pubDate>Thu, 04 Sep 2008 13:53:43 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056869</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I'm going to paste part of the "all-info" diagnostic of the modem in.<br><br>192.168.254.019 is the server that's sending out to a mailman mailing list.<br><br>Does anyone think the Netopia's table is overloading?  There's a lot of calls for DNS on UDP 53.<br><br>The Netopia is fine on memory, as you can see first.<br>--------<br>Memory status:<br>Heap: total bytes 7555072 (free 4663176, allocated 2891896)<br>System Packet Buffers: total 500 free 468 min 346<br>Image usage: text 3922636, data 726404, bss 636812<br><br><textarea name="code" class="text" cols=50 rows=10>IP NAT used list, total = 2247&#012;Key Inside_Address :Port     Outside_Address:Port     OPort  Life   Prot&#012;000 192.168.254.019:51291    012.198.003.178:00053    51291  00002  UDP  &#012;001 192.168.254.019:01805    204.074.109.001:00053    01805  00010  UDP  &#012;002 192.168.254.019:50956    209.070.133.003:00053    50956  00045  UDP  &#012;003 192.168.254.019:59886    205.178.190.034:00053    59886  00139  UDP  &#012;004 192.168.254.019:41463    205.178.190.026:00053    41463  00083  UDP  &#012;005 192.168.254.019:61317    216.222.208.141:00053    61317  00027  UDP  &#012;006 192.168.254.019:51154    156.154.072.065:00053    51154  00165  UDP  &#012;006 192.168.254.019:01529    150.208.010.026:00053    01529  00110  UDP  &#012;006 192.168.254.019:39497    198.006.001.202:00053    39497  00110  UDP  &#012;006 192.168.254.019:58001    063.077.045.130:00053    58001  00038  UDP  &#012;006 192.168.254.019:26384    204.196.197.003:00053    26384  00005  UDP  &#012;007 192.168.254.019:52150    204.246.224.133:00025    52150  00017  TCP  &#012;008 192.168.254.019:55350    072.052.179.223:00053    55350  00055  UDP  &#012;010 192.168.254.019:63380    216.123.224.131:00053    63380  00163  UDP  &#012;010 192.168.254.019:21538    213.247.155.245:00053    21538  00048  UDP  &#012;011 192.168.254.019:52474    080.085.071.030:00053    52474  00162  UDP  &#012;011 192.168.254.019:45775    063.173.209.073:00053    45775  00115  UDP  &#012;011 192.168.254.019:40652    204.011.209.076:00053    40652  00074  UDP  &#012;011 192.168.254.019:38671    204.253.245.009:00053    38671  00032  UDP  &#012;012 192.168.254.019:59197    216.039.053.003:00025    59197  14398  TCP  &#012;012 192.168.254.019:28139    205.178.190.046:00053    28139  00037  UDP  &#012;013 192.168.254.019:59900    192.012.094.030:00053    59900  00147  UDP  &#012;014 192.168.254.019:12040    209.132.221.019:00053    12040  00176  UDP  &#012;014 192.168.254.019:25368    192.073.061.003:00053    25368  00162  UDP  &#012;014 192.168.254.019:38956    204.196.188.022:00025    38956  00021  TCP  &#012;014 192.168.254.019:17658    202.012.027.033:00053    17658  00086  UDP  &#012;014 192.168.254.019:52497    200.037.195.010:00053    52497  00061  UDP  &#012;015 192.168.254.019:17897    205.178.190.051:00053    17897  00159  UDP  &#012;016 192.168.254.019:28700    204.074.112.001:00053    28700  00155  UDP  &#012;016 192.168.254.019:27019    064.126.106.146:00053    27019  00003  UDP  &#012;018 192.168.254.019:58379    208.195.132.020:00053    58379  00173  UDP  &#012;018 192.168.254.019:42968    206.055.232.071:00053    42968  00163  UDP  &#012;018 192.168.254.019:48655    149.130.010.016:00053    48655  00052  UDP  &#012;020 192.168.254.019:02743    069.025.073.106:00053    02743  00176  UDP  &#012;020 192.168.254.019:38962    204.196.188.022:00025    38962  00023  TCP  &#012;020 192.168.254.019:57814    062.190.034.075:00053    57814  00162  UDP  &#012;020 192.168.254.019:23084    199.038.149.245:00053    23084  00159  UDP  &#012;020 192.168.254.019:19993    168.039.166.008:00053    19993  00041  UDP  &#012;020 192.168.254.019:33684    216.222.212.141:00053    33684  00025  UDP  &#012;021 192.168.254.019:04255    146.145.087.131:00053    04255  00040  UDP  &#012;021 192.168.254.019:35488    063.077.045.130:00053    35488  00038  UDP  &#012;021 192.168.254.019:18186    195.244.245.024:00053    18186  00010  UDP  &#012;021 192.168.254.019:26410    063.201.004.248:00053    26410  00001  UDP  &#012;023 192.168.254.019:48134    192.026.092.030:00053    48134  00149  UDP  &#012;023 192.168.254.019:10246    192.031.080.030:00053    10246  00130  UDP  &#012;023 192.168.254.019:35600    199.250.021.020:00053    35600  00130  UDP  &#012;024 192.168.254.019:49984    206.051.224.229:00053    49984  00172  UDP  &#012;024 192.168.254.019:17586    064.040.131.115:00053    17586  00157  UDP  &#012;024 192.168.254.019:07431    192.048.079.030:00053    07431  00033  UDP  &#012;025 192.168.254.019:62433    012.127.016.069:00053    62433  00174  UDP  &#012;025 192.168.254.019:44964    170.222.064.130:00053    44964  00127  UDP  &#012;025 192.168.254.019:36675    064.029.145.010:00025    36675  00011  TCP  &#012;026 192.168.254.019:54646    149.130.070.177:00053    54646  00034  UDP  &#012;026 192.168.254.019:26121    192.012.094.030:00053    26121  00031  UDP  &#012;027 192.168.254.019:31262    205.178.190.010:00053    31262  00165  UDP  &#012;027 192.168.254.019:55074    209.011.221.006:00053    55074  00094  UDP  &#012;028 192.168.254.019:27147    192.041.162.030:00053    27147  00141  UDP  &#012;028 192.168.254.019:04011    205.189.048.126:00053    04011  00132  UDP  &#012;028 192.168.254.019:15398    069.027.096.003:00053    15398  00034  UDP  &#012;029 192.168.254.019:50456    216.040.047.018:00053    50456  00110  UDP  &#012;029 192.168.254.019:03615    063.214.034.011:00053    03615  00086  UDP  &#012;031 192.168.254.019:62494    205.178.144.014:00053    62494  00170  UDP  &#012;031 192.168.254.019:03616    132.250.110.012:00053    03616  00086  UDP  &#012;031 192.168.254.019:44814    192.042.093.030:00053    44814  00036  UDP  &#012;031 192.168.254.019:37664    161.185.001.012:00053    37664  00012  UDP  &#012;032 192.168.254.019:61479    147.064.032.006:00053    61479  00130  UDP  &#012;032 192.168.254.019:49411    207.228.035.042:00053    49411  00005  UDP  &#012;033 192.168.254.019:57514    063.209.003.132:00053    57514  00092  UDP  &#012;033 192.168.254.019:15341    156.154.072.065:00053    15341  00052  UDP  &#012;034 192.168.254.019:24593    192.031.080.030:00053    24593  00163  UDP  &#012;034 192.168.254.019:54810    199.120.154.021:00053    54810  00104  UDP  &#012;034 192.168.254.019:59270    070.246.240.169:00053    59270  00053  UDP  &#012;035 192.168.254.019:16918    150.208.010.026:00053    16918  00101  UDP  &#012;036 192.168.254.019:18534    066.203.199.203:00053    18534  00163  UDP  &#012;036 192.168.254.019:38359    128.008.010.090:00053    38359  00128  UDP  &#012;036 192.168.254.019:32812    198.254.016.005:00053    32812  00083  UDP  &#012;036 192.168.254.019:13360    204.074.112.001:00053    13360  00020  UDP  &#012;037 192.168.254.019:18992    066.208.002.002:00053    18992  00093  UDP  &#012;037 192.168.254.019:65044    192.041.162.030:00053    65044  00054  UDP  &#012;038 192.168.254.019:25582    012.127.016.069:00053    25582  00147  UDP  &#012;038 192.168.254.019:21793    216.040.047.018:00053    21793  00110  UDP  &#012;039 192.168.254.019:53827    192.005.005.241:00053    53827  00017  UDP  &#012;040 192.168.254.019:27378    012.180.109.067:00053    27378  00147  UDP  &#012;040 192.168.254.019:40983    192.031.080.030:00053    40983  00112  UDP  &#012;041 192.168.254.019:01845    204.074.101.001:00053    01845  00056  UDP  &#012;041 192.168.254.019:63510    192.031.080.032:00053    63510  00009  UDP  &#012;042 192.168.254.019:12585    193.108.091.014:00053    12585  00097  UDP  &#012;042 192.168.254.019:24857    192.055.083.030:00053    24857  00088  UDP  &#012;042 192.168.254.019:39978    212.183.160.013:00053    39978  00029  UDP  &#012;043 192.168.254.019:19274    066.186.008.238:00053    19274  00161  UDP  &#012;043 192.168.254.019:22422    074.174.028.162:00053    22422  00127  UDP  &#012;043 192.168.254.019:22580    192.112.036.004:00053    22580  00096  UDP  &#012;044 192.168.254.019:14322    206.055.232.071:00053    14322  00159  UDP  &#012;044 192.168.254.019:45754    066.111.017.127:00053    45754  00136  UDP  &#012;044 192.168.254.019:22061    063.170.142.012:00053    22061  00136  UDP  &#012;044 192.168.254.019:41596    128.242.113.189:00053    41596  00118  UDP  &#012;044 192.168.254.019:18206    066.045.117.027:00053    18206  00057  UDP  &#012;044 192.168.254.019:34351    209.006.082.010:00053    34351  00014  UDP  &#012;045 192.168.254.019:10274    205.178.144.024:00053    10274  00155  UDP  &#012;045 192.168.254.019:07459    170.094.047.023:00053    07459  00069  UDP  &#012;045 192.168.254.019:55465    216.020.063.145:00053    55465  00060  UDP  &#012;046 192.168.254.019:30778    216.021.128.001:00053    30778  00144  UDP  &#012;046 192.168.254.019:33399    195.198.081.196:00053    33399  00135  UDP  &#012;046 192.168.254.019:33309    192.052.178.030:00053    33309  00089  UDP  &#012;048 192.168.254.019:03360    161.115.175.029:00053    03360  00030  UDP  &#012;049 192.168.254.019:02837    199.193.013.041:00053    02837  00175  UDP  &#012;049 192.168.254.019:28733    206.055.232.001:00053    28733  00163  UDP  &#012;049 192.168.254.019:30717    156.154.072.065:00053    30717  00110  UDP  &#012;050 192.168.254.019:14611    140.153.043.044:00053    14611  00148  UDP  &#012;052 192.168.254.019:65082    198.051.214.007:00053    65082  00173  UDP  &#012;052 192.168.254.019:46437    072.055.114.220:00053    46437  00171  UDP  &#012;052 192.168.254.019:24099    192.041.162.030:00053    24099  00054  UDP  &#012;052 192.168.254.019:28209    063.244.142.016:00053    28209  00027  UDP  &#012;053 192.168.254.019:24612    192.043.172.030:00053    24612  00148  UDP  &#012;053 192.168.254.019:20657    216.020.063.145:00053    20657  00060  UDP  &#012;053 192.168.254.019:57152    195.233.129.002:00053    57152  00028  UDP  &#012;053 192.168.254.019:39678    216.035.197.068:00053    39678  00026  UDP  &#012;053 192.168.254.019:10048    193.041.037.002:00053    10048  00005  UDP  &#012;054 192.168.254.019:35765    164.082.148.142:00053    35765  00038  UDP  &#012;055 192.168.254.019:23092    149.130.010.016:00053    23092  00066  UDP  &#012;056 192.168.254.019:08237    205.178.144.024:00053    08237  00152  UDP  &#012;056 192.168.254.019:04952    204.041.004.237:00053    04952  00090  UDP  &#012;056 192.168.254.019:03101    208.109.132.040:00053    03101  00045  UDP  &#012;056 192.168.254.019:19295    207.253.012.230:00053    19295  00013  UDP  &#012;057 192.168.254.019:22822    192.055.083.032:00053    22822  00135  UDP  &#012;057 192.168.254.019:49704    192.033.014.030:00053    49704  00079  UDP  &#012;058 192.168.254.019:09767    192.012.094.032:00053    09767  00176  UDP  &#012;058 192.168.254.019:01508    217.023.130.099:00053    01508  00159  UDP  &#012;058 192.168.254.019:21130    128.242.113.189:00053    21130  00118  UDP  &#012;058 192.168.254.019:60202    137.118.001.029:00053    60202  00021  UDP  &#012;059 192.168.254.019:46679    192.005.005.241:00053    46679  00020  UDP  &#012;059 192.168.254.019:06215    144.089.040.001:00053    06215  00010  UDP  &#012;060 192.168.254.019:37843    204.249.212.118:00053    37843  00147  UDP  &#012;060 192.168.254.019:42558    063.214.034.011:00053    42558  00086  UDP  &#012;061 192.168.254.019:47113    156.154.072.065:00053    47113  00123  UDP  &#012;061 192.168.254.019:44597    199.120.154.021:00053    44597  00105  UDP  &#012;061 192.168.254.019:16940    192.052.178.030:00053    16940  00002  UDP  &#012;062 192.168.254.019:13101    167.206.001.030:00053    13101  00129  UDP  &#012;063 192.168.254.019:28740    195.187.244.008:00053    28740  00124  UDP  &#012;064 192.168.254.019:17484    206.055.232.001:00053    17484  00160  UDP  &#012;064 192.168.254.019:50227    205.178.144.026:00053    50227  00058  UDP  &#012;064 192.168.254.019:02892    204.074.101.001:00053    02892  00056  UDP  &#012;067 192.168.254.019:23452    066.165.160.180:00053    23452  00048  UDP  &#012;068 192.168.254.019:53297    192.031.080.032:00053    53297  00128  UDP  &#012;070 192.168.254.019:08913    063.077.045.130:00053    08913  00038  UDP  &#012;070 192.168.254.019:39260    063.209.010.247:00053    39260  00021  UDP  &#012;071 192.168.254.019:58348    217.012.004.104:00053    58348  00178  UDP  &#012;071 192.168.254.019:48959    216.032.181.021:00053    48959  00089  UDP  &#012;072 192.168.254.019:36849    130.189.240.100:00053    36849  00135  UDP  &#012;072 192.168.254.019:57874    069.085.254.067:00053    57874  00025  UDP  &#012;073 192.168.254.019:05136    012.127.016.070:00053    05136  00138  UDP  &#012;073 192.168.254.019:50251    213.092.008.011:00053    50251  00029  UDP  &#012;074 192.168.254.019:61836    064.246.042.203:00053    61836  00124  UDP  &#012;074 192.168.254.019:57102    063.173.209.073:00053    57102  00115  UDP  &#012;075 192.168.254.019:54389    204.041.004.010:00025    54389  14286  TCP  &#012;076 192.168.254.019:59217    216.103.101.008:00053    59217  00149  UDP  &#012;076 192.168.254.019:50581    064.211.042.196:00053    50581  00057  UDP  &#012;076 192.168.254.019:43108    213.247.155.245:00053    43108  00048  UDP  &#012;077 192.168.254.019:38439    205.178.190.051:00053    38439  00158  UDP  &#012;077 192.168.254.019:60758    212.181.091.004:00053    60758  00157  UDP  &#012;079 192.168.254.019:24223    128.242.113.189:00053    24223  00035  UDP  &#012;080 192.168.254.019:40789    158.057.045.008:00053    40789  00156  UDP  &#012;080 192.168.254.019:12379    216.108.208.002:00053    12379  00096  UDP  &#012;081 192.168.254.019:20800    192.035.051.030:00053    20800  00096  UDP  &#012;081 192.168.254.019:46889    204.068.245.053:00053    46889  00009  UDP  &#012;082 192.168.254.019:41030    216.153.000.025:00053    41030  00164  UDP  &#012;084 192.168.254.019:57437    209.235.192.004:00053    57437  00042  UDP  &#012;085 192.168.254.019:17115    206.065.185.135:00053    17115  00059  UDP  &#012;085 192.168.254.019:07732    205.178.190.046:00053    07732  00037  UDP  &#012;086 192.168.254.019:19767    140.153.043.044:00053    19767  00148  UDP  &#012;086 192.168.254.019:30651    066.196.084.168:00053    30651  00036  UDP  &#012;086 192.168.254.019:10326    064.094.136.013:00053    10326  00018  UDP  &#012;087 192.168.254.019:25202    204.054.009.242:00053    25202  00098  UDP  &#012;087 192.168.254.019:16422    194.085.252.062:00053    16422  00048  UDP  &#012;088 192.168.254.019:41031    192.031.080.030:00053    41031  00167  UDP  &#012;088 192.168.254.019:16481    198.041.000.004:00053    16481  00049  UDP  &#012;089 192.168.254.019:39476    067.114.146.050:00053    39476  00151  UDP  &#012;089 192.168.254.019:45737    128.242.113.189:00053    45737  00035  UDP  &#012;089 192.168.254.019:05448    192.048.079.030:00053    05448  00033  UDP  &#012;090 192.168.254.019:54389    160.042.128.025:00025    54389  00026  TCP  &#012;090 192.168.254.019:61373    207.047.040.170:00053    61373  00011  UDP  &#012;090 192.168.254.019:64545    012.127.016.070:00053    64545  00010  UDP  &#012;091 192.168.254.019:21095    199.007.066.001:00053    21095  00138  UDP  &#012;091 192.168.254.019:27602    206.081.136.150:00053    27602  00098  UDP  &#012;092 192.168.254.019:34416    156.045.254.032:00025    34416  00012  TCP  &#012;092 192.168.254.019:50044    204.041.004.237:00053    50044  00041  UDP  &#012;092 192.168.254.019:58343    012.017.000.130:00053    58343  00006  UDP  &#012;093 192.168.254.019:04682    192.041.162.032:00053    04682  00148  UDP  &#012;093 192.168.254.019:06722    131.191.254.040:00053    06722  00130  UDP  &#012;093 192.168.254.019:41062    147.076.000.004:00053    41062  00035  UDP  &#012;094 192.168.254.019:57381    012.127.016.070:00053    57381  00109  UDP  &#012;095 192.168.254.019:02105    205.178.144.051:00053    02105  00158  UDP  &#012;095 192.168.254.019:29652    008.011.252.152:00053    29652  00058  UDP  &#012;095 192.168.254.019:15958    202.044.170.022:00053    15958  00035  UDP  &#012;096 192.168.254.019:15378    066.135.224.091:00053    15378  00161  UDP  &#012;096 192.168.254.019:20056    171.066.002.021:00053    20056  00062  UDP  &#012;097 192.168.254.019:01133    204.074.112.001:00053    01133  00127  UDP  &#012;098 192.168.254.019:12013    209.247.001.130:00053    12013  00143  UDP  &#012;098 192.168.254.019:02897    192.042.093.030:00053    02897  00036  UDP  &#012;098 192.168.254.019:34560    198.006.049.111:00053    34560  00023  UDP  &#012;099 192.168.254.019:51536    192.055.083.032:00053    51536  00135  UDP  &#012;099 192.168.254.019:10355    064.018.015.253:00053    10355  00105  UDP  &#012;099 192.168.254.019:15407    156.154.072.065:00053    15407  00052  UDP  &#012;099 192.168.254.019:09547    167.064.243.037:00053    09547  00045  UDP  &#012;100 192.168.254.019:44080    156.154.072.065:00053    44080  00091  UDP  &#012;100 192.168.254.019:48576    149.130.070.177:00053    48576  00044  UDP  &#012;100 192.168.254.019:54176    216.220.208.209:00053    54176  00030  UDP  &#012;100 192.168.254.019:34670    204.196.197.003:00053    34670  00018  UDP  &#012;101 192.168.254.019:47193    205.178.188.025:00053    47193  00170  UDP  &#012;101 192.168.254.019:53447    075.126.027.171:00053    53447  00151  UDP  &#012;101 192.168.254.019:34474    205.151.069.200:00053    34474  00040  UDP  &#012;101 192.168.254.019:08236    012.127.016.070:00053    08236  00000  UDP  &#012;102 192.168.254.019:54769    192.197.162.130:00053    54769  00040  UDP  &#012;102 192.168.254.019:53577    069.028.095.042:00053    53577  00030  UDP  &#012;103 192.168.254.019:53362    158.229.200.002:00053    53362  00169  UDP  &#012;103 192.168.254.019:55167    147.064.032.245:00053    55167  00128  UDP  &#012;105 192.168.254.019:44632    192.033.014.030:00053    44632  00138  UDP  &#012;105 192.168.254.019:01368    192.035.051.030:00053    01368  00046  UDP  &#012;106 192.168.254.019:18284    199.193.013.011:00053    18284  00176  UDP  &#012;106 192.168.254.019:52104    216.032.181.022:00025    52104  00002  TCP  &#012;106 192.168.254.019:10099    064.202.165.004:00053    10099  00045  UDP  &#012;106 192.168.254.019:47769    192.133.042.005:00025    47769  14360  TCP  &#012;107 192.168.254.019:21474    206.081.136.150:00053    21474  00099  UDP  &#012;107 192.168.254.019:61352    064.018.008.208:00053    61352  00095  UDP  &#012;107 192.168.254.019:22644    198.254.016.004:00053    22644  00064  UDP  &#012;107 192.168.254.019:25715    198.254.016.005:00053    25715  00062  UDP  &#012;108 192.168.254.019:48776    192.005.005.241:00053    48776  00147  UDP  &#012;108 192.168.254.019:31835    192.031.080.030:00053    31835  00017  UDP  &#012;109 192.168.254.019:53373    064.018.015.253:00053    53373  00139  UDP  &#012;109 192.168.254.019:16928    128.008.010.090:00053    16928  00128  UDP  &#012;110 192.168.254.019:02681    208.080.126.002:00053    02681  00165  UDP  &#012;110 192.168.254.019:36210    208.056.139.009:00053    36210  00047  UDP  &#012;111 192.168.254.019:23424    066.250.040.252:00053    23424  00123  UDP  &#012;111 192.168.254.019:13099    198.006.001.081:00053    13099  00050  UDP  &#012;112 192.168.254.019:06454    158.229.207.071:00053    06454  00167  UDP  &#012;112 192.168.254.019:56188    198.103.097.001:00053    56188  00165  UDP  &#012;112 192.168.254.019:58468    056.000.100.025:00053    58468  00111  UDP  &#012;112 192.168.254.019:45076    199.191.128.105:00053    45076  00007  UDP  &#012;114 192.168.254.019:16254    151.164.001.001:00053    16254  00080  UDP  &#012;114 192.168.254.019:59152    198.006.049.111:00053    59152  00024  UDP  &#012;114 192.168.254.019:21346    137.118.001.029:00053    21346  00020  UDP  &#012;115 192.168.254.019:39788    063.105.037.020:00053    39788  00177  UDP  &#012;115 192.168.254.019:58982    150.208.010.026:00053    58982  00049  UDP  &#012;115 192.168.254.019:30320    149.130.010.016:00053    30320  00039  UDP  &#012;115 192.168.254.019:25203    216.220.214.013:00053    25203  00029  UDP  &#012;116 192.168.254.019:06319    207.253.227.210:00053    06319  00112  UDP  &#012;116 192.168.254.019:34599    064.005.041.090:00053    34599  00092  UDP  &#012;116 192.168.254.019:36669    069.059.189.068:00053    36669  00030  UDP  &#012;116 192.168.254.019:65534    012.017.000.131:00053    65534  00006  UDP  &#012;117 192.168.254.019:52115    216.032.181.022:00025    52115  00006  TCP  &#012;117 192.168.254.019:26753    204.074.112.001:00053    26753  00088  UDP  &#012;117 192.168.254.019:62326    161.185.001.012:00053    62326  00012  UDP  &#012;119 192.168.254.019:20904    072.055.114.220:00053    20904  00171  UDP  &#012;119 192.168.254.019:23737    066.203.199.203:00053    23737  00163  UDP  &#012;119 192.168.254.019:54926    199.038.149.246:00053    54926  00159  UDP  &#012;119 192.168.254.019:15491    204.074.112.001:00053    15491  00086  UDP  &#012;120 192.168.254.019:39938    216.123.224.131:00053    39938  00163  UDP  &#012;120 192.168.254.019:16516    199.007.068.001:00053    16516  00090  UDP  &#012;121 192.168.254.019:21930    072.055.114.220:00053    21930  00171  UDP  &#012;121 192.168.254.019:43928    066.186.008.238:00053    43928  00161  UDP  &#012;121 192.168.254.019:55429    199.007.068.001:00053    55429  00091  UDP  &#012;122 192.168.254.019:58819    064.211.042.196:00053    58819  00158  UDP  &#012;123 192.168.254.019:04230    216.108.208.002:00053    04230  00096  UDP  &#012;123 192.168.254.019:51305    207.088.020.031:00053    51305  00005  UDP  &#012;124 192.168.254.019:32325    164.235.034.068:00053    32325  00102  UDP  &#012;124 192.168.254.019:32945    204.152.239.216:00053    32945  00029  UDP  &#012;125 192.168.254.019:50589    198.182.159.020:00025    50589  00009  TCP  &#012;125 192.168.254.019:63625    209.197.064.001:00053    63625  00135  UDP  &#012;125 192.168.254.019:48931    167.206.001.103:00053    48931  00129  UDP  &#012;125 192.168.254.019:14087    132.250.001.131:00053    14087  00086  UDP  &#012;126 192.168.254.019:24000    064.246.042.203:00053    24000  00124  UDP  &#012;127 192.168.254.019:47746    198.128.002.010:00053    47746  00160  UDP  &#012;127 192.168.254.019:15499    204.074.112.001:00053    15499  00135  UDP  &#012;127 192.168.254.019:28286    202.055.146.014:00053    28286  00125  UDP  &#012;128 192.168.254.019:54412    204.074.112.001:00053    54412  00029  UDP  &#012;128 192.168.254.019:65346    128.220.001.075:00053    65346  00013  UDP  &#012;129 192.168.254.019:61330    066.250.040.252:00053    61330  00122  UDP  &#012;130 192.168.254.019:09102    204.074.109.001:00053    09102  00129  UDP  &#012;130 192.168.254.019:53114    216.032.181.021:00053    53114  00046  UDP  &#012;132 192.168.254.019:51836    164.165.070.060:00025    51836  00029  TCP  &#012;132 192.168.254.019:59507    192.026.092.030:00053    59507  00172  UDP  &#012;132 192.168.254.019:02184    209.210.176.009:00053    02184  00130  UDP  &#012;132 192.168.254.019:35679    167.064.057.050:00053    35679  00045  UDP  &#012;132 192.168.254.019:50251    012.127.016.070:00053    50251  00011  UDP  &#012;133 192.168.254.019:36753    204.074.109.001:00053    36753  00173  UDP  &#012;133 192.168.254.019:43439    064.018.007.010:00025    43439  00013  TCP  &#012;133 192.168.254.019:34230    216.203.022.220:00053    34230  00109  UDP  &#012;133 192.168.254.019:39028    192.026.092.030:00053    39028  00092  UDP  &#012;133 192.168.254.019:48270    198.254.016.004:00053    48270  00072  UDP  &#012;133 192.168.254.019:37797    204.041.004.237:00053    37797  00038  UDP  &#012;133 192.168.254.019:32624    064.237.045.034:00053    32624  00017  UDP  &#012;134 192.168.254.019:05269    065.205.231.254:00053    05269  00145  UDP  &#012;134 192.168.254.019:47762    199.019.054.001:00053    47762  00128  UDP  &#012;134 192.168.254.019:44138    066.250.040.041:00053    44138  00122  UDP  &#012;134 192.168.254.019:02863    205.156.189.100:00053    02863  00112  UDP  &#012;134 192.168.254.019:30610    204.074.101.001:00053    30610  00019  UDP  &#012;134 192.168.254.019:59281    193.041.037.002:00053    59281  00004  UDP  &#012;135 192.168.254.019:06252    216.069.160.040:00053    06252  00170  UDP  &#012;135 192.168.254.019:11408    198.254.016.004:00053    11408  00072  UDP  &#012;136 192.168.254.019:06754    205.178.190.051:00053    06754  00158  UDP  &#012;137 192.168.254.019:23884    069.028.095.074:00053    23884  00029  UDP  &#012;138 192.168.254.019:41890    147.064.032.245:00053    41890  00128  UDP  &#012;138 192.168.254.019:14490    064.018.015.253:00053    14490  00112  UDP  &#012;138 192.168.254.019:60566    204.074.112.001:00053    60566  00029  UDP  &#012;139 192.168.254.019:54147    216.032.181.021:00053    54147  00170  UDP  &#012;139 192.168.254.019:03093    216.123.224.131:00053    03093  00163  UDP  &#012;139 192.168.254.019:55409    205.178.144.039:00053    55409  00090  UDP  &#012;140 192.168.254.019:34948    198.241.000.060:00025    34948  00017  TCP  &#012;141 192.168.254.019:33942    205.178.144.004:00053    33942  00165  UDP  &#012;141 192.168.254.019:27772    192.026.092.030:00053    27772  00025  UDP  &#012;142 192.168.254.019:56561    063.246.147.170:00053    56561  00136  UDP  &#012;142 192.168.254.019:14964    131.191.254.039:00053    14964  00130  UDP  &#012;142 192.168.254.019:43009    216.021.224.154:00053    43009  00074  UDP  &#012;143 192.168.254.019:52378    204.017.036.002:00053    52378  00178  UDP  &#012;143 192.168.254.019:30976    209.051.159.156:00053    30976  00157  UDP  &#012;143 192.168.254.019:02991    204.041.008.237:00053    02991  00007  UDP  &#012;144 192.168.254.019:42489    198.124.226.203:00025    42489  00026  TCP  &#012;144 192.168.254.019:60561    192.033.004.012:00053    60561  00135  UDP  &#012;144 192.168.254.019:64501    066.196.084.168:00053    64501  00036  UDP  &#012;145 192.168.254.019:39330    208.038.046.252:00053    39330  00112  UDP  &#012;146 192.168.254.019:27802    208.235.064.005:00053    27802  00082  UDP  &#012;146 192.168.254.019:26388    065.069.149.139:00053    26388  00080  UDP  &#012;146 192.168.254.019:22682    198.254.016.005:00053    22682  00066  UDP  &#012;146 192.168.254.019:56414    156.154.072.065:00053    56414  00052  UDP  &#012;146 192.168.254.019:37249    192.055.083.030:00053    37249  00038  UDP  &#012;147 192.168.254.019:42778    162.129.253.134:00053    42778  00013  UDP  &#012;148 192.168.254.019:60711    142.131.015.161:00025    60711  14400  TCP  &#012;148 192.168.254.019:09387    199.038.151.246:00053    09387  00160  UDP  &#012;148 192.168.254.019:07203    065.054.240.126:00053    07203  00157  UDP  &#012;148 192.168.254.019:53408    204.074.112.001:00053    53408  00110  UDP  &#012;149 192.168.254.019:55969    199.007.066.001:00053    55969  00138  UDP  &#012;149 192.168.254.019:48156    074.254.100.134:00053    48156  00122  UDP  &#012;150 192.168.254.019:37526    063.170.142.013:00053    37526  00136  UDP  &#012;150 192.168.254.019:45171    152.158.016.048:00053    45171  00132  UDP  &#012;150 192.168.254.019:34977    216.108.208.002:00053    34977  00097  UDP  &#012;151 192.168.254.019:11414    208.069.152.014:00053    11414  00152  UDP  &#012;151 192.168.254.019:57507    204.074.112.001:00053    57507  00018  UDP  &#012;152 192.168.254.019:43458    064.018.007.010:00025    43458  00016  TCP  &#012;152 192.168.254.019:51296    012.127.016.069:00053    51296  00171  UDP  &#012;153 192.168.254.019:00137    066.218.040.066:24592    00137  00128  UDP  &#012;153 192.168.254.019:19906    199.201.154.228:00053    19906  00016  UDP  &#012;154 192.168.254.019:34180    199.005.199.035:00053    34180  00128  UDP  &#012;154 192.168.254.019:50829    150.208.010.026:00053    50829  00099  UDP  &#012;154 192.168.254.019:10403    192.112.036.004:00053    10403  00096  UDP  &#012;155 192.168.254.019:23649    206.055.232.071:00053    23649  00163  UDP  &#012;155 192.168.254.019:07143    193.000.000.193:00053    07143  00149  UDP  &#012;155 192.168.254.019:45155    012.127.016.069:00053    45155  00147  UDP  &#012;156 192.168.254.019:56387    216.157.144.102:00053    56387  00124  UDP  &#012;156 192.168.254.019:21419    209.208.092.254:00053    21419  00110  UDP  &#012;156 192.168.254.019:11279    216.021.224.154:00053    11279  00074  UDP  &#012;156 192.168.254.019:17049    149.130.010.016:00053    17049  00056  UDP  &#012;157 192.168.254.019:10663    141.150.159.003:00053    10663  00160  UDP  &#012;158 192.168.254.019:25512    192.073.061.003:00053    25512  00162  UDP  &#012;158 192.168.254.019:24703    204.074.112.044:00053    24703  00162  UDP  &#012;158 192.168.254.019:59549    141.224.064.014:00053    59549  00135  UDP  &#012;158 192.168.254.019:55691    192.055.083.032:00053    55691  00135  UDP  &#012;158 192.168.254.019:10466    192.228.079.201:00053    10466  00048  UDP  &#012;159 192.168.254.019:46537    207.126.147.010:00025    46537  00016  TCP  &#012;159 192.168.254.019:07993    198.006.001.115:00053    07993  00083  UDP  &#012;160 192.168.254.019:65461    063.201.004.248:00053    65461  00002  UDP  &#012;163 192.168.254.019:31661    004.002.049.003:00053    31661  00162  UDP  &#012;163 192.168.254.019:49855    192.005.005.241:00053    49855  00147  UDP  &#012;163 192.168.254.019:53618    204.061.215.062:00053    53618  00061  UDP  &#012;164 192.168.254.019:38014    205.178.144.051:00053    38014  00159  UDP  &#012;164 192.168.254.019:23945    064.129.155.040:00053    23945  00115  UDP  &#012;164 192.168.254.019:11693    143.215.143.004:00053    11693  00030  UDP  &#012;165 192.168.254.019:49042    064.241.157.071:00025    49042  14399  TCP  &#012;166 192.168.254.019:55473    158.229.200.002:00053    55473  00169  UDP  &#012;166 192.168.254.019:29167    064.211.042.196:00053    29167  00057  UDP  &#012;166 192.168.254.019:55973    065.170.002.014:00053    55973  00003  UDP  &#012;167 192.168.254.019:37040    198.041.000.004:00053    37040  00158  UDP  &#012;167 192.168.254.019:55306    207.047.040.170:00053    55306  00088  UDP  &#012;168 192.168.254.019:56241    129.170.017.004:00053    56241  00137  UDP  &#012;169 192.168.254.019:24274    209.164.013.228:00053    24274  00138  UDP  &#012;170 192.168.254.019:58094    062.119.149.201:00053    58094  00130  UDP  &#012;171 192.168.254.019:58778    192.035.051.030:00053    58778  00012  UDP  &#012;174 192.168.254.019:38561    150.208.010.026:00053    38561  00099  UDP  &#012;174 192.168.254.019:47626    149.130.070.177:00053    47626  00048  UDP  &#012;175 192.168.254.019:14518    147.064.032.006:00053    14518  00130  UDP  &#012;175 192.168.254.019:50105    203.147.241.003:00053    50105  00109  UDP  &#012;176 192.168.254.019:36826    064.029.145.010:00025    36826  00029  TCP  &#012;176 192.168.254.019:62632    205.178.184.021:00053    62632  00139  UDP  &#012;176 192.168.254.019:54196    204.253.245.009:00053    54196  00033  UDP  &#012;177 192.168.254.019:53648    205.194.019.085:00025    53648  00007  TCP  &#012;177 192.168.254.019:48162    066.133.136.195:00025    48162  00004  TCP  &#012;178 192.168.254.019:44221    216.108.208.002:00053    44221  00096  UDP  &#012;178 192.168.254.019:25249    192.033.014.030:00053    25249  00083  UDP  &#012;179 192.168.254.019:50877    199.193.010.042:00025    50877  00016  TCP  &#012;179 192.168.254.019:19448    063.251.092.200:00053    19448  00171  UDP  &#012;179 192.168.254.019:43860    209.126.137.108:00053    43860  00144  UDP  &#012;179 192.168.254.019:29885    216.108.208.003:00053    29885  00099  UDP  &#012;179 192.168.254.019:15411    216.222.212.141:00053    15411  00025  UDP  &#012;180 192.168.254.019:23774    216.082.247.227:00053    23774  00179  UDP  &#012;180 192.168.254.019:28323    192.041.162.030:00053    28323  00176  UDP  &#012;181 192.168.254.019:11919    205.178.190.051:00053    11919  00158  UDP  &#012;181 192.168.254.019:00025    216.157.255.016:48601    00025  00000  TCP  &#012;181 192.168.254.019:02012    207.253.012.230:00053    02012  00013  UDP  &#012;182 192.168.254.019:11003    062.119.149.200:00053    11003  00126  UDP  &#012;182 192.168.254.019:02688    069.085.254.067:00053    02688  00025  UDP  &#012;182 192.168.254.019:58548    209.166.168.015:00053    58548  00011  UDP  &#012;183 192.168.254.019:44360    119.160.247.124:00053    44360  00092  UDP  &#012;184 192.168.254.019:25251    205.178.190.034:00053    25251  00139  UDP  &#012;185 192.168.254.019:31352    199.228.142.078:00053    31352  00147  UDP  &#012;185 192.168.254.019:14334    063.251.092.200:00053    14334  00022  UDP  &#012;186 192.168.254.019:38569    192.033.014.030:00053    38569  00060  UDP  &#012;187 192.168.254.019:24716    206.139.064.060:00053    24716  00090  UDP  &#012;188 192.168.254.019:55962    208.109.014.047:00053    55962  00169  UDP  &#012;188 192.168.254.019:37524    128.063.002.053:00053    37524  00167  UDP  &#012;188 192.168.254.019:37047    072.232.188.018:00053    37047  00019  UDP  &#012;189 192.168.254.019:35545    192.197.181.241:00053    35545  00165  UDP  &#012;190 192.168.254.019:28824    205.178.144.051:00053    28824  00158  UDP  &#012;190 192.168.254.019:08325    012.127.016.070:00053    08325  00084  UDP  &#012;190 192.168.254.019:20041    063.192.114.130:00053    20041  00005  UDP  &#012;191 192.168.254.019:32709    130.068.001.007:00053    32709  00106  UDP  &#012;191 192.168.254.019:59285    204.235.121.055:00053    59285  00017  UDP  &#012;192 192.168.254.019:25228    012.039.198.065:00053    25228  00084  UDP  &#012;193 192.168.254.019:61626    212.156.004.020:00053    61626  00014  UDP  &#012;194 192.168.254.019:23875    159.087.179.140:00053    23875  00052  UDP  &#012;194 192.168.254.019:43200    209.166.168.015:00053    43200  00011  UDP  &#012;195 192.168.254.019:14221    012.180.109.067:00053    14221  00147  UDP  &#012;195 192.168.254.019:22227    204.074.109.253:00053    22227  00016  UDP  &#012;195 192.168.254.019:31920    192.031.080.032:00053    31920  00013  UDP  &#012;196 192.168.254.019:63700    064.018.015.253:00053    63700  00172  UDP  &#012;196 192.168.254.019:45007    216.068.049.002:00053    45007  00146  UDP  &#012;196 192.168.254.019:59263    216.136.033.082:00053    59263  00018  UDP  &#012;199 192.168.254.019:12015    066.197.185.229:00053    12015  00144  UDP  &#012;199 192.168.254.019:16372    204.011.140.224:00053    16372  00089  UDP  &#012;199 192.168.254.019:63817    216.021.231.139:00053    63817  00074  UDP  &#012;199 192.168.254.019:28879    198.254.016.005:00053    28879  00070  UDP  &#012;200 192.168.254.019:38154    066.203.199.203:00053    38154  00164  UDP  &#012;200 192.168.254.019:36791    216.092.061.030:00053    36791  00134  UDP  &#012;200 192.168.254.019:54218    216.089.093.011:00053    54218  00111  UDP  &#012;201 192.168.254.019:52872    199.228.142.078:00053    52872  00046  UDP  &#012;202 192.168.254.019:27861    158.229.200.002:00053    27861  00169  UDP  &#012;202 192.168.254.019:06611    212.181.091.004:00053    06611  00157  UDP  &#012;202 192.168.254.019:37065    141.224.064.014:00053    37065  00135  UDP  &#012;202 192.168.254.019:47436    216.021.231.139:00053    47436  00074  UDP  &#012;202 192.168.254.019:58077    216.147.001.250:00053    58077  00048  UDP  &#012;202 192.168.254.019:26810    216.220.212.029:00053    26810  00029  UDP  &#012;203 192.168.254.019:47816    149.130.010.016:00053    47816  00032  UDP  &#012;204 192.168.254.019:61098    208.109.014.047:00053    61098  00170  UDP  &#012;204 192.168.254.019:63167    216.205.226.026:00053    63167  00160  UDP  &#012;206 192.168.254.019:37907    063.251.092.200:00053    37907  00171  UDP  &#012;206 192.168.254.019:39099    192.026.092.032:00053    39099  00142  UDP  &#012;207 192.168.254.019:47546    158.229.207.073:00025    47546  00013  TCP  &#012;208 192.168.254.019:02751    192.005.006.030:00053    02751  00170  UDP  &#012;209 192.168.254.019:17172    198.006.001.202:00053    17172  00149  UDP  &#012;209 192.168.254.019:59602    192.033.004.012:00053    59602  00135  UDP  &#012;209 192.168.254.019:50659    208.038.046.251:00053    50659  00114  UDP  &#012;209 192.168.254.019:17626    192.112.036.004:00053    17626  00096  UDP  &#012;210 192.168.254.019:24798    128.231.064.001:00053    24798  00119  UDP  &#012;212 192.168.254.019:51511    063.246.147.170:00053    51511  00030  UDP  &#012;212 192.168.254.019:62489    064.147.104.200:00053    62489  00003  UDP  &#012;213 192.168.254.019:29424    205.171.009.242:00053    29424  00065  UDP  &#012;214 192.168.254.019:54452    199.093.044.047:00053    54452  00159  UDP  &#012;214 192.168.254.017:02978    072.014.223.018:00080    49600  14391  TCP  &#012;215 192.168.254.019:37591    194.242.186.013:00053    37591  00141  UDP  &#012;215 192.168.254.019:11462    192.031.080.030:00053    11462  00130  UDP  &#012;215 192.168.254.019:58842    136.001.007.010:00053    58842  00098  UDP  &#012;216 192.168.254.019:16487    205.189.048.126:00053    16487  00112  UDP  &#012;216 192.168.254.019:63194    063.214.034.011:00053    63194  00086  UDP  &#012;216 192.168.254.019:54244    151.164.001.001:00053    54244  00080  UDP  &#012;216 192.168.254.019:12249    161.185.001.012:00053    12249  00012  UDP  &#012;217 192.168.254.019:08872    207.041.014.062:00053    08872  00073  UDP  &#012;217 192.168.254.019:33697    216.035.197.069:00053    33697  00026  UDP  &#012;219 192.168.254.019:27363    205.178.190.005:00053    27363  00170  UDP  &#012;219 192.168.254.019:06131    147.064.032.245:00053    06131  00128  UDP  &#012;219 192.168.254.019:40679    192.026.210.001:00053    40679  00040  UDP  &#012;220 192.168.254.019:07400    206.055.232.001:00053    07400  00163  UDP  &#012;220 192.168.254.019:64493    066.250.040.252:00053    64493  00122  UDP  &#012;220 192.168.254.019:61407    209.237.137.010:00053    61407  00079  UDP  &#012;221 192.168.254.019:42153    156.154.072.065:00053    42153  00110  UDP  &#012;223 192.168.254.019:47054    192.042.093.030:00053    47054  00172  UDP  &#012;223 192.168.254.019:63227    192.197.181.241:00053    63227  00165  UDP  &#012;223 192.168.254.019:32424    164.235.034.068:00053    32424  00103  UDP  &#012;224 192.168.254.019:24015    192.035.051.030:00053    24015  00083  UDP  &#012;225 192.168.254.019:23012    066.225.199.010:00053    23012  00048  UDP  &#012;225 192.168.254.019:24804    157.093.252.010:00053    24804  00020  UDP  &#012;226 192.168.254.019:05583    192.055.083.032:00053    05583  00135  UDP  &#012;226 192.168.254.019:21054    149.130.070.177:00053    21054  00040  UDP  &#012;226 192.168.254.019:54540    204.041.004.010:00025    54540  14349  TCP  &#012;227 192.168.254.019:01766    153.009.002.010:00053    01766  00177  UDP  &#012;227 192.168.254.019:06377    205.178.144.007:00053    06377  00085  UDP  &#012;228 192.168.254.019:32702    012.004.125.051:00053    32702  00127  UDP  &#012;230 192.168.254.019:56083    066.196.082.007:00025    56083  00018  TCP  &#012;231 192.168.254.019:29939    204.074.112.001:00053    29939  00152  UDP  &#012;231 192.168.254.019:22742    192.026.092.030:00053    22742  00042  UDP  &#012;232 192.168.254.019:59413    204.011.140.224:00053    59413  00144  UDP  &#012;232 192.168.254.019:43001    195.232.196.252:00053    43001  00027  UDP  &#012;233 192.168.254.019:55000    192.012.094.030:00053    55000  00147  UDP  &#012;233 192.168.254.019:12277    204.074.101.001:00053    12277  00019  UDP  &#012;233 192.168.254.019:19478    204.011.140.224:00053    19478  00011  UDP  &#012;234 192.168.254.019:50925    192.203.230.010:00053    50925  00162  UDP  &#012;234 192.168.254.019:61296    070.086.061.135:00053    61296  00120  UDP  &#012;234 192.168.254.019:35630    062.119.149.201:00053    35630  00118  UDP  &#012;234 192.168.254.019:58278    198.006.001.081:00053    58278  00050  UDP  &#012;235 192.168.254.019:46244    069.020.060.123:00025    46244  00000  TCP  &#012;235 192.168.254.019:17114    192.005.006.030:00053    17114  00065  UDP  &#012;236 192.168.254.019:48605    209.204.159.028:00053    48605  00031  UDP  &#012;237 192.168.254.019:11996    192.041.162.030:00053    11996  00086  UDP  &#012;238 192.168.254.019:06365    192.054.112.030:00053    06365  00098  UDP  &#012;240 192.168.254.019:04348    204.074.112.001:00053    04348  00105  UDP  &#012;240 192.168.254.019:12015    012.130.062.014:00053    12015  00098  UDP  &#012;240 192.168.254.019:52707    069.028.095.026:00053    52707  00088  UDP  &#012;240 192.168.254.019:07903    192.041.162.030:00053    07903  00046  UDP  &#012;242 192.168.254.019:54401    205.189.048.126:00053    54401  00092  UDP  &#012;242 192.168.254.019:49375    192.031.080.032:00053    49375  00016  UDP  &#012;243 192.168.254.019:55806    198.166.215.002:00053    55806  00120  UDP  &#012;244 192.168.254.019:46071    202.078.077.010:00053    46071  00074  UDP  &#012;245 192.168.254.019:09919    074.200.194.067:00053    09919  00084  UDP  &#012;246 192.168.254.019:17922    192.197.083.001:00053    17922  00165  UDP  &#012;247 192.168.254.019:38078    012.127.016.070:00053    38078  00109  UDP  &#012;248 192.168.254.019:49981    062.119.149.200:00053    49981  00116  UDP  &#012;248 192.168.254.019:03549    207.130.095.040:00053    03549  00104  UDP  &#012;249 192.168.254.019:35544    205.178.190.046:00053    35544  00157  UDP  &#012;249 192.168.254.019:42275    216.082.247.227:00053    42275  00110  UDP  &#012;250 192.168.254.019:56553    192.031.080.030:00053    56553  00167  UDP  &#012;250 192.168.254.019:07172    192.073.061.003:00053    07172  00162  UDP  &#012;251 192.168.254.019:03560    192.055.083.032:00053    03560  00135  UDP  &#012;252 192.168.254.019:25854    063.081.160.011:00053    25854  00173  UDP  &#012;252 192.168.254.019:04843    192.005.006.030:00053    04843  00086  UDP  &#012;252 192.168.254.019:03810    208.067.174.039:00053    03810  00031  UDP  &#012;253 192.168.254.019:09225    204.074.101.001:00053    09225  00056  UDP  &#012;253 192.168.254.019:05888    192.203.230.010:00053    05888  00013  UDP  &#012;254 192.168.254.019:06997    198.006.001.182:00053    06997  00145  UDP  &#012;254 192.168.254.019:57579    192.031.080.032:00053    57579  00128  UDP  &#012;255 192.168.254.019:36334    192.048.079.030:00053    36334  00136  UDP  &#012;256 192.168.254.019:42252    206.055.232.001:00053    42252  00163  UDP  &#012;256 192.168.254.019:08928    205.178.190.045:00053    08928  00112  UDP  &#012;257 192.168.254.019:51422    152.158.036.048:00053    51422  00132  UDP  &#012;257 192.168.254.019:41601    207.035.202.141:00053    41601  00032  UDP  &#012;258 192.168.254.019:19153    207.041.014.062:00053    19153  00073  UDP  &#012;260 192.168.254.019:12002    208.109.014.047:00053    12002  00169  UDP  &#012;260 192.168.254.019:54032    199.019.054.001:00053    54032  00042  UDP  &#012;261 192.168.254.019:61468    204.074.108.246:00053    61468  00164  UDP  &#012;261 192.168.254.019:45560    080.085.075.065:00025    45560  00014  TCP  &#012;261 192.168.254.019:10513    204.074.112.001:00053    10513  00005  UDP  &#012;262 192.168.254.017:03008    072.014.223.018:00080    49648  14391  TCP  &#012;262 192.168.254.019:11408    216.123.224.131:00053    11408  00163  UDP  &#012;262 192.168.254.019:07698    063.254.227.001:00053    07698  00136  UDP  &#012;262 192.168.254.019:01168    012.017.000.131:00053    01168  00006  UDP  &#012;263 192.168.254.019:65456    216.069.185.100:00053    65456  00170  UDP  &#012;264 192.168.254.019:28083    069.028.095.098:00053    28083  00138  UDP  &#012;264 192.168.254.019:45215    204.249.212.118:00053    45215  00127  UDP  &#012;264 192.168.254.019:62052    149.130.070.177:00053    62052  00035  UDP  &#012;265 192.168.254.019:33296    209.200.131.006:00053    33296  00143  UDP  &#012;265 192.168.254.019:49541    216.020.063.145:00053    49541  00060  UDP  &#012;265 192.168.254.019:41938    069.059.189.068:00053    41938  00031  UDP  &#012;268 192.168.254.019:34445    202.065.014.140:00053    34445  00121  UDP  &#012;268 192.168.254.019:01236    012.127.016.069:00053    01236  00094  UDP  &#012;268 192.168.254.019:15576    156.154.072.065:00053    15576  00052  UDP  &#012;268 192.168.254.019:03835    192.012.094.030:00053    03835  00003  UDP  &#012;271 192.168.254.019:59113    205.178.190.051:00053    59113  00158  UDP  &#012;272 192.168.254.019:59605    071.252.000.072:00053    59605  00128  UDP  &#012;272 192.168.254.019:23295    192.005.006.030:00053    23295  00086  UDP  &#012;272 192.168.254.019:52620    216.020.063.145:00053    52620  00059  UDP  &#012;272 192.168.254.019:01039    162.075.001.014:00053    01039  00018  UDP  &#012;274 192.168.254.019:53534    204.074.112.001:00053    53534  00170  UDP  &#012;275 192.168.254.019:37205    066.203.199.203:00053    37205  00162  UDP  &#012;275 192.168.254.019:23800    063.210.044.040:00053    23800  00105  UDP  &#012;275 192.168.254.019:13595    198.104.140.005:00053    13595  00102  UDP  &#012;275 192.168.254.019:55410    193.000.012.174:00053    55410  00073  UDP  &#012;275 192.168.254.019:41166    207.088.020.082:00053    41166  00005  UDP  &#012;277 192.168.254.019:42015    004.002.049.003:00053    42015  00162  UDP  &#012;277 192.168.254.019:28403    209.082.050.047:00053    28403  00057  UDP  &#012;277 192.168.254.019:45345    204.074.112.001:00053    45345  00050  UDP  &#012;278 192.168.254.019:52626    216.020.063.145:00053    52626  00057  UDP  &#012;279 192.168.254.019:26750    064.215.164.166:00053    26750  00131  UDP  &#012;279 192.168.254.019:48379    066.250.040.041:00053    48379  00122  UDP  &#012;280 192.168.254.019:12814    170.094.047.023:00053    12814  00163  UDP  &#012;280 192.168.254.019:10300    128.196.128.233:00053    10300  00135  UDP  &#012;281 192.168.254.019:05896    192.033.014.030:00053    05896  00045  UDP  &#012;281 192.168.254.019:02340    216.157.192.002:00053    02340  00024  UDP  &#012;282 192.168.254.019:37641    192.033.014.030:00053    37641  00019  UDP  &#012;282 192.168.254.019:15585    012.127.016.070:00053    15585  00000  UDP  &#012;283 192.168.254.019:59179    204.074.109.253:00053    59179  00016  UDP  &#012;284 192.168.254.019:54529    216.069.160.040:00053    54529  00170  UDP  &#012;284 192.168.254.019:15399    195.233.129.002:00053    15399  00027  UDP  &#012;285 192.168.254.019:36134    129.170.016.004:00053    36134  00137  UDP  &#012;285 192.168.254.019:02281    156.154.072.065:00053    02281  00110  UDP  &#012;285 192.168.254.019:24332    192.041.162.030:00053    24332  00054  UDP  &#012;286 192.168.254.019:01046    216.032.181.021:00053    01046  00138  UDP  &#012;286 192.168.254.019:41737    205.056.138.034:00053    41737  00086  UDP  &#012;287 192.168.254.019:13070    192.005.006.030:00053    13070  00176  UDP  &#012;289 192.168.254.019:39702    216.220.230.024:00053    39702  00116  UDP  &#012;289 192.168.254.019:31533    192.026.210.001:00053    31533  00040  UDP  &#012;289 192.168.254.019:15632    192.026.092.030:00053    15632  00025  UDP  &#012;289 192.168.254.019:15898    020.001.107.020:00053    15898  00010  UDP  &#012;290 192.168.254.019:21736    206.055.232.071:00053    21736  00163  UDP  &#012;290 192.168.254.019:24878    209.197.064.001:00053    24878  00135  UDP  &#012;291 192.168.254.019:48431    216.021.128.001:00053    48431  00144  UDP  &#012;291 192.168.254.019:04388    192.033.004.012:00053    04388  00064  UDP  &#012;291 192.168.254.019:41234    192.031.080.030:00053    41234  00006  UDP  &#012;292 192.168.254.019:24644    204.041.004.237:00053    24644  00097  UDP  &#012;292 192.168.254.019:17200    204.069.234.001:00053    17200  00056  UDP  &#012;292 192.168.254.019:64048    203.083.159.001:00053    64048  00033  UDP  &#012;293 192.168.254.019:41934    216.069.185.100:00053    41934  00045  UDP  &#012;293 192.168.254.019:16815    146.145.087.131:00053    16815  00041  UDP  &#012;294 192.168.254.019:51505    158.229.200.002:00053    51505  00173  UDP  &#012;294 192.168.254.019:58418    204.074.101.001:00053    58418  00056  UDP  &#012;294 192.168.254.019:57433    206.222.012.218:00053    57433  00030  UDP  &#012;295 192.168.254.019:61215    199.120.154.021:00053    61215  00105  UDP  &#012;295 192.168.254.019:37668    149.130.010.016:00053    37668  00044  UDP  &#012;296 192.168.254.019:17713    198.041.000.004:00053    17713  00049  UDP  &#012;296 192.168.254.019:57155    205.171.009.242:00053    57155  00017  UDP  &#012;296 192.168.254.019:41204    156.154.072.065:00053    41204  00002  UDP  &#012;297 192.168.254.019:35602    061.129.074.036:00053    35602  00065  UDP  &#012;298 192.168.254.019:43810    199.120.154.021:00053    43810  00104  UDP  &#012;298 192.168.254.019:59276    064.038.033.171:00053    59276  00088  UDP  &#012;299 192.168.254.019:47415    204.074.112.001:00053    47415  00092  UDP  &#012;299 192.168.254.019:60364    209.126.137.108:00053    60364  00037  UDP  &#012;299 192.168.254.019:48050    162.129.253.134:00053    48050  00013  UDP  &#012;300 192.168.254.019:54299    192.042.093.030:00053    54299  00152  UDP  &#012;300 192.168.254.019:08891    207.153.206.126:00053    08891  00139  UDP  &#012;300 192.168.254.019:06031    193.221.085.170:00053    06031  00132  UDP  &#012;300 192.168.254.019:27516    128.242.113.189:00053    27516  00118  UDP  &#012;300 192.168.254.019:46128    204.253.245.009:00053    46128  00033  UDP  &#012;301 192.168.254.019:19533    204.041.008.237:00053    19533  00039  UDP  &#012;301 192.168.254.019:53462    161.149.240.100:00053    53462  00001  UDP  &#012;302 192.168.254.019:36134    205.178.184.021:00053    36134  00037  UDP  &#012;302 192.168.254.019:47289    012.017.000.130:00053    47289  00006  UDP  &#012;303 192.168.254.019:18206    192.012.094.030:00053    18206  00104  UDP  &#012;303 192.168.254.019:60627    199.191.128.105:00053    60627  00094  UDP  &#012;304 192.168.254.019:28323    209.051.142.154:00053    28323  00157  UDP  &#012;304 192.168.254.019:10795    208.047.019.018:00053    10795  00151  UDP  &#012;304 192.168.254.019:29475    150.208.010.026:00053    29475  00110  UDP  &#012;305 192.168.254.019:60171    205.178.190.051:00053    60171  00159  UDP  &#012;305 192.168.254.019:28133    072.051.035.089:00053    28133  00097  UDP  &#012;306 192.168.254.019:41296    216.032.180.022:00025    41296  00002  TCP  &#012;306 192.168.254.019:24609    192.042.093.030:00053    24609  00010  UDP  &#012;307 192.168.254.019:64347    066.197.185.229:00053    64347  00096  UDP  &#012;308 192.168.254.019:22824    205.178.188.025:00053    22824  00165  UDP  &#012;308 192.168.254.019:11071    066.208.002.002:00053    11071  00093  UDP  &#012;308 192.168.254.019:13091    192.041.162.030:00053    13091  00029  UDP  &#012;310 192.168.254.019:35359    216.031.235.075:00025    35359  00014  TCP  &#012;310 192.168.254.019:16142    128.063.002.053:00053    16142  00167  UDP  &#012;310 192.168.254.019:56646    064.018.015.253:00053    56646  00152  UDP  &#012;310 192.168.254.019:27812    209.225.008.159:00053    27812  00137  UDP  &#012;310 192.168.254.019:04319    130.189.240.100:00053    04319  00136  UDP  &#012;310 192.168.254.017:02996    140.174.115.086:00080    49628  00018  TCP  &#012;310 192.168.254.019:05435    146.145.176.008:00053    05435  00053  UDP  &#012;311 192.168.254.019:62657    216.123.224.131:00053    62657  00162  UDP  &#012;311 192.168.254.019:41301    216.032.180.022:00025    41301  00002  TCP  &#012;311 192.168.254.019:63807    198.104.140.005:00053    63807  00103  UDP  &#012;311 192.168.254.019:41507    202.012.027.033:00053    41507  00086  UDP  &#012;311 192.168.254.019:27059    216.020.063.145:00053    27059  00060  UDP  &#012;312 192.168.254.019:35484    132.250.166.208:00025    35484  00017  TCP  &#012;312 192.168.254.017:02998    140.174.115.086:00080    49630  00001  TCP  &#012;312 192.168.254.019:03367    192.026.092.030:00053    03367  00092  UDP  &#012;313 192.168.254.019:62273    205.178.190.005:00053    62273  00170  UDP  &#012;313 192.168.254.017:02999    140.174.115.086:00080    49631  00000  TCP  &#012;313 192.168.254.019:17966    206.213.251.024:00053    17966  00028  UDP  &#012;315 192.168.254.019:39439    142.032.011.096:00025    39439  00001  TCP  &#012;316 192.168.254.019:41512    202.012.027.033:00053    41512  00086  UDP  &#012;317 192.168.254.019:11529    156.154.072.065:00053    11529  00049  UDP  &#012;318 192.168.254.019:04170    204.074.101.001:00053    04170  00054  UDP  &#012;319 192.168.254.019:56110    192.041.162.030:00053    56110  00176  UDP  &#012;319 192.168.254.019:05438    141.224.064.014:00053    05438  00135  UDP  &#012;319 192.168.254.019:30016    192.033.004.012:00053    30016  00052  UDP  &#012;320 192.168.254.019:30534    198.051.214.007:00053    30534  00173  UDP  &#012;321 192.168.254.017:03000    140.174.115.086:00080    49639  00018  TCP  &#012;321 192.168.254.019:31811    065.119.145.011:00053    31811  00141  UDP  &#012;321 192.168.254.019:30569    066.197.185.229:00053    30569  00104  UDP  &#012;321 192.168.254.019:39234    192.033.004.012:00053    39234  00064  UDP  &#012;322 192.168.254.019:17746    064.018.015.253:00053    17746  00164  UDP  &#012;322 192.168.254.019:30817    066.186.008.238:00053    30817  00161  UDP  &#012;322 192.168.254.017:03001    140.174.115.086:00080    49640  00001  TCP  &#012;322 192.168.254.019:48462    206.055.232.001:00053    48462  00159  UDP  &#012;322 192.168.254.019:35021    154.011.136.130:00053    35021  00120  UDP  &#012;322 192.168.254.019:63289    202.044.170.022:00053    63289  00037  UDP  &#012;323 192.168.254.019:46517    216.122.007.155:00053    46517  00170  UDP  &#012;323 192.168.254.017:03002    140.174.115.086:00080    49641  00001  TCP  &#012;323 192.168.254.019:58653    205.178.144.051:00053    58653  00159  UDP  &#012;324 192.168.254.019:45346    141.211.124.086:00025    45346  00003  TCP  &#012;324 192.168.254.017:03003    140.174.115.086:00080    49642  00000  TCP  &#012;324 192.168.254.019:63795    192.054.112.030:00053    63795  00057  UDP  &#012;324 192.168.254.019:09011    192.012.094.030:00053    09011  00026  UDP  &#012;324 192.168.254.019:39118    012.017.000.131:00053    39118  00006  UDP  &#012;325 192.168.254.017:03004    140.174.115.086:00080    49643  00018  TCP  &#012;325 192.168.254.019:56351    064.124.069.051:00053    56351  00084  UDP  &#012;326 192.168.254.017:03005    140.174.115.086:00080    49644  00018  TCP  &#012;</textarea><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056869</guid>
<pubDate>Thu, 04 Sep 2008 13:44:21 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056516</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : It's been a few hours since the last restart, and there's still only 1 upchannel CRC error.<br><br>When the router crashes, I can't get into it anymore to find the value.  This ain't looking easy to solve.  I'll have to take them to Covad or a T1 if this doesn't improve soon.<br><br><textarea name="code" class="text" cols=50 rows=10>ADSL Line State:        Up&#012;ADSL Startup Attempts:  3&#012;ADSL Modulation:        DMT&#012;ADSL Data Path:         Fast&#012;Datapump Version:       DSP 5.2.2.0, HAL 5.2.2.0&#012; &#012;                        Downstream  Upstream&#012;                        ----------  ----------&#012;SNR Margin:                  16.00       21.00 dB&#012;Line Attenuation:             3.00        1.50 dB&#012;Output Power:           -     4.35       10.42 dB&#012;Errored Seconds:                 0           0&#012;Loss of Signal:                  0           0&#012;Loss of Frame:                   0           0&#012;CRC Errors:                      0           1&#012;Data Rate:                    4512         608&#012;</textarea><!--end code block--><br>---<br><br>Update:<br><br>The router crashed completely about 2 minutes after I posted the above.  It was not pingable on the LAN, but it did know when a cable had been removed from the ethernet port.<br><br>The DSL light went out when I unplugged the phone line, but from experience in the past, it does not establish a PPPoE session when reconnected.<br><br>I do think the upstream output power on the Netopia is higher than it used to be in this location (notice it's got a negative value for the downstream power).<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056516</guid>
<pubDate>Thu, 04 Sep 2008 12:31:59 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056283</link>
<description><![CDATA[<A HREF="/useremail/u/1323812"><b>reddog6102</b></A> : This sounds like a Catina/Cienna dslam(correct?).If so the new cienna cards have pinwheels on them that need to coincide with the cable pair of the shelf.Does the sync lite go out when problem occurs?Has the DLC crew checked out the common card for the shelf?Is it OC3 fed or t1 fed?Probably fiber fed if they offer 6meg.My gut tells me its the netopia router,they are very sensitive to junk trafic and will shut down/lock up.Also maybe a t1 working in the same binder group of house cable.This will suck out a certain frequency(forget wich one).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056283</guid>
<pubDate>Thu, 04 Sep 2008 11:40:33 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21056271</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : While you're waiting, keep an eye on the upstream CRC errors.  If they start piling up, with no corresponding increase in downstream CRC errors, you may have exactly the problem I had...which was definitely at the RT.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21056271</guid>
<pubDate>Thu, 04 Sep 2008 11:38:02 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21055411</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : Okay, the new profile didn't fix it.<br><br>I'm going in today with another router, but also asking David to see about getting a completely new card installed.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21055411</guid>
<pubDate>Thu, 04 Sep 2008 08:37:36 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21052480</link>
<description><![CDATA[<A HREF="/useremail/u/1029026"><b>koma3504</b></A> :  That is some very usefull information there. Thanks for posting.<br><br>That Information would make a very good site faq.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21052480</guid>
<pubDate>Wed, 03 Sep 2008 17:58:47 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21052198</link>
<description><![CDATA[<A HREF="/useremail/u/411904"><b>gdm</b></A> : I had this problem when I was in Bartlett over 3 years ago.  My card went bad twice, the first time it was just DSL.  The 2nd time it was POTS.  The tech that came out the 2nd time said the same thing as yours Doc.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21052198</guid>
<pubDate>Wed, 03 Sep 2008 16:59:43 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21052181</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : He tried three different ADLU cards before he got one which actually worked.  Evidently there was/is some kind or austerity program going on and they just keep swapping cards without knowing the exact functional status of any of them.  He finally managed to pry a "new" card out of the garage and installed it.  No problems at all since.<br><br>Now, my brother in law, who is on the same RT, is having all sorts of problems with both DSL and POTS.  The wiring in his building has been eliminated as the cause, and three tech visits later his DSL is down again.<br><br>I suspect <i>most</i> of the cards are in fact bad.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21052181</guid>
<pubDate>Wed, 03 Sep 2008 16:56:25 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21052034</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : reddog, you missed some information in the first post.<br><br>The customer has elite-S service and was syncing at 6016/768, and tests about 130 feet away from the RT, for the simple reason the RT is in the basement, and they're on the 9th floor.  Note the attenuation of 3.0 and 1.5.  They are WELL below the capacity threshold.<br><br>This problem started 6 weeks ago, and the 3346 was operating from July 2005 until then.  The problem persists with a new 3347, and only happens during times when the upchannel is being stressed by their server sending out a large mailman-based mailing list.<br><br>I asked  David <A HREF="/useremail/u/637748"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> to set them to a profile that only had a 608 up channel, and this was the best he could find that would do that.<br><br>Radiodoc, I had your situation in mind when I was working with the tech.  He moved the pair to a completely different card.  Perhaps it was another bad card as well, but it's awfully hard to prove.<br><br>My road to proof of the problem is to first see if the lower up sync makes the problem go away.<br><br>If it does, I'll complain about that, and see if it coincides with an update to the RTs.<br><br>If it doesn't, I'll swap in a 2Wire OfficePortal 1800.<br><br>If that fails, then I can point back at the RT card.  But no matter what, I'm collecting all data from other people in a similar situation.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21052034</guid>
<pubDate>Wed, 03 Sep 2008 16:30:13 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21051500</link>
<description><![CDATA[<A HREF="/useremail/u/157889"><b>RadioDoc</b></A> : Had multiple occasions of multiple different units (Westell, 2-Wire, Efficient/Siemens of various eras) do the same damn thing at home awhile back.  Turned out to be a bad RT card.  Since that's been replaced with a new one (and actually replaced, not just swapped with an equally bad card) I have had zero issues.<br><br>Coincidence?  Nope.  Not according to the last tech who was out and got it fixed for good.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21051500</guid>
<pubDate>Wed, 03 Sep 2008 14:55:31 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21050977</link>
<description><![CDATA[<A HREF="/useremail/u/1323812"><b>reddog6102</b></A> : I am a legacy bellsouth tech but we carry netopia business routers as well and this seems interesting.A couple questions for ya:.what type of problems are you having,what type of dslam?We have had our share of firmware woes with this router over the years.our latest problem was a wholesale mode (picture of house on interface page)that wouldnt open multiple static ip's to be public.Some other problems with other firmware was no 2+ platform compatability and random loss of sync.our current model is 3347-02-1006L/f/w761r9.What speed are you paying for?Your footprint looks like a 6meg profile according to your noise margin amoung other thing but you arent syncing at full bandwidth.you are at fast path wich means no noise profile and 4512kbs at 16db downstream doesnt seem right.For one you have to be close 99-100%capacity(cant tell from that footprint)and that can cause surfing issues.Most alcatel dslams sync at 8128k max.Why you are syncing at 4500k with a noise margin of 16 is strange to me.your noise margin should be lower.I'll wait for other techs to chime in on this one.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21050977</guid>
<pubDate>Wed, 03 Sep 2008 13:19:09 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21050718</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I can try it, but I'm going to wait a bit, since it just moved to a maintenance profile of 4512 down and 608 up.  I'd like to see if it fails at this speed with the current CPE before changing anything.<br><br>Here are the stats after 16 hours.<br><br><textarea name="code" class="text" cols=50 rows=10> &#012;ADSL Line State:        Up&#012;ADSL Startup Attempts:  3&#012;ADSL Modulation:        DMT&#012;ADSL Data Path:         Fast&#012;Datapump Version:       DSP 5.2.2.0, HAL 5.2.2.0&#012; &#012;                        Downstream  Upstream&#012;                        ----------  ----------&#012;SNR Margin:                  16.50       21.00 dB&#012;Line Attenuation:             3.00        1.50 dB&#012;Output Power:           -     4.33       10.49 dB&#012;Errored Seconds:                 0           0&#012;Loss of Signal:                  0           0&#012;Loss of Frame:                   0           0&#012;CRC Errors:                      0           1&#012;Data Rate:                    4512         608&#012;</textarea><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21050718</guid>
<pubDate>Wed, 03 Sep 2008 12:33:41 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21050550</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : Can you try replacing with a 2wire or something? I just have a hard time believing that the RT comes into play...when the symptoms seem more like your overwhelming the memory buffers/routing table in the CPE.<br><small>--<br><A HREF="http://www.dennisjudd.com">My Blog. Because I desperately need the acknowledgement of others.</a><br><br><A HREF="http://www.dennisjudd.com/juddfamily">Visit the Judd Family website to see my kids!</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21050550</guid>
<pubDate>Wed, 03 Sep 2008 12:02:35 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21046440</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : 7.5.1 R10-DP42 and its predecessor on the 3346, and 7.6.1 R9 on the 3347.  These drops started about 6 weeks ago.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21046440</guid>
<pubDate>Tue, 02 Sep 2008 16:47:01 EDT</pubDate>
</item>

<item>
<title>Re: Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21046159</link>
<description><![CDATA[<A HREF="/useremail/u/1029026"><b>koma3504</b></A> : Are you talking aout this version  7.5.1 R10-DP42 <br><br>As i know i have had that happen with my Netopia Running<br>nta751r10_dp42-2.bin<br><br>And I am on a Rt as well.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21046159</guid>
<pubDate>Tue, 02 Sep 2008 15:56:17 EDT</pubDate>
</item>

<item>
<title>Netopia 33xx routers and high upchannel utilization</title>
<link>http://www.dslreports.com/forum/remark,21045875</link>
<description><![CDATA[<A HREF="/useremail/u/399707"><b>lev</b></A> : I've got a client on an Elite-S package that has a mailserver on a hosted IP.  For several years, they've been running without a problem.<br><br>Starting about 6 weeks ago, when they send out to their mailing list, and the upchannel is pegged for a few hours sending to lots of sites, their Netopia 3346 started to freeze.  It wouldn't respond locally, and even the DSL status lights wouldn't update... even if the phone cord was removed.  It took a power reset to bring the router back.<br><br>So they replaced it with a 3347 Netopia unit, with wireless.<br><br>The problem remains.  Only after a few hours of high up bandwidth, will this be a problem.<br><br>They're on a remote terminal, and I'm exploring the possibility that a change to the firmware in the RT might have brought out a problem that was lying latent in the Netopias.  AT&T has already changed the pairs and cut them over to a different card in the RT, and the problem's still there.  David's working on lowering the upchannel to 608 to see if that makes this lockup less likely to occur.<br><br>I'm just looking for anyone else who's seen this behavior with a current firmware version of either the Netopia 3346N-002 or the 3347-02-1006.  Thanks.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21045875</guid>
<pubDate>Tue, 02 Sep 2008 15:18:41 EDT</pubDate>
</item>

</channel>
</rss>
