Read and enjoy.

Public service messages for uverse end users:

1.) make sure you are not using any "plug-link" /Homeplug type of devices on your gigapower service. Apparently these devices might never get you a good speed test. They seem to also cause LAN problems for the NVG589's

2.) DO NOT let animals (in my example a cat) to progressively keep urinating on your modem and expect full speeds.

3.) make sure your devices can do 1000 (gig) sync on the LAN. You can't achieve 300 mbps speeds if your local lan is at 100mbps. Hate to say it, just simply isn't going to happen.

4.) DO NOT flood your upstream- that age old TCP/IP flaw is alive and well when you flood/max out your upstream.
--
Scott, CCIE #14618 Routing & Switching
»rolande.wordpress.com/

Actually, the diverging hop is where the traffic branches from the AT&T (Tier1) network into the AT&T Uverse and (former) Bellsouth FastAccess networks. IPv6-in-IP (protocol 41) gets dropped inbound by Uverse, but not Bellsouth. "All" (not that I've tried all 255) other protocols get through. Unless you know someone who has access to that hop, all any of us can do is point and say "it stopped right there."

That is definitely the recommended thing to do on the 2Wire/Pace devices at this point, due to all of the bugs and security issues with it enabled. I have not seen the issue readout on the Motorola devices but do not believe that it suffers from much of the same crappy code issues that the 2Wire devices do. I have enabled the IPv6 option on my NVG589 and am using DHCP-PD from my Cisco router to delegate one of the /64 prefixes from the assigned /60 netblock to my internal network. It's working like a champ now.