List of compatible modems for Fusion X2 pair bonded service
Posted: Tue Mar 10, 2015 10:53 am
If you're supplying your own equipment for Fusion X2 (single phone line, double speed internet) service, please list the model number here. Thanks!
Sonic.net Forums
https://forums.sonic.net/
C'mon, don't keep us hanging. Let us know what magical modem this is and what is required to make it work. Or were you on AT&T's IPDSLAM U-verse (ADSL2+)?ryanca wrote:I also already have a VDSL2 modem I was using successfully on U-Verse (an actual modem, not AT&T's hardware - there were some shenanigans involved in making it work), but I have no idea if it's compatible with your equipment (my loop is close to 5000 ft so it doesn't much matter anyway).
I guess this explains why my ADSL2+ modem stopped working (would sync, wasn't receiving any frames) when my X2 upgrade was provisioned last night (I have a tech scheduled to come out in the morning to bring the second line up).dane wrote:No, the ZyXel P-663HN also does not support PTM, nor VDSL2. It'd work if you happened to land on one of our ATM/G.bond interfaces, but we're now provisioning the newer "universal" (UDSL) interface which supports both VDSL2 and ADSL2+ and ADSL2, using PTM instead of ATM.
The UDSL interfaces are assigned in every case where customers are close enough to obtain VDSL2 sync speeds, and in a growing number of cases for longer-loop customers who are more likely to get ADSL2+ due to distance. All new port growth is built using the new interface, so it's more and more common. So, older ADSL2+ CPE which support only ATM and G.bond won't work.
I totally understand. The Pace 5168N seems to be pretty nice hardware, and $9.50/mo is a reasonable cost to rent it considering that it probably costs $200-$250. I (being the sort of person to have a home network with VLANs and a router running Debian) just don't want/need most of what it does - all I want is good (no caps, no filtering, no traffic shaping, reliable, low latency, sufficient bandwidth) IP connectivity to my router.dane wrote: I strongly encourage Sonic members to remain in our end-to-end equipment rental and wire plan service. It's a nominal monthly cost, and allows us to provide fully integrated support. Support's dashboard shows things like wireless interference, missing filters, and we can push security and feature updates when needed. The wire plan means you'll never pay for a technician visit, even if the issue is related to inside wiring or the CPE itself. By taking full responsibility end-to-end from the DSLAM through the DSL modem/router and WiFi, Sonic can own and resolve every issue, without arguing about who pays for what, whether it's your equipment or ours, etc.
I had to use my modem (which was very difficult to find) for physical connectivity as well as the AT&T 2wire CPE so that the AT&T hardware could do 802.1x auth. It's highly impractical to set up, but it does avoid going through their lousy NAT.Guest wrote:C'mon, don't keep us hanging. Let us know what magical modem this is and what is required to make it work. Or were you on AT&T's IPDSLAM U-verse (ADSL2+)?ryanca wrote:I also already have a VDSL2 modem I was using successfully on U-Verse (an actual modem, not AT&T's hardware - there were some shenanigans involved in making it work), but I have no idea if it's compatible with your equipment (my loop is close to 5000 ft so it doesn't much matter anyway).
No, that's not the reason. The issue is that your loop was made part of an ATM G.bond group, so you need to use the Pace 5168 that we sent.ryanca wrote:I guess this explains why my ADSL2+ modem stopped working (would sync, wasn't receiving any frames) when my X2 upgrade was provisioned last night (I have a tech scheduled to come out in the morning to bring the second line up).dane wrote:No, the ZyXel P-663HN also does not support PTM, nor VDSL2. It'd work if you happened to land on one of our ATM/G.bond interfaces, but we're now provisioning the newer "universal" (UDSL) interface which supports both VDSL2 and ADSL2+ and ADSL2, using PTM instead of ATM.
The UDSL interfaces are assigned in every case where customers are close enough to obtain VDSL2 sync speeds, and in a growing number of cases for longer-loop customers who are more likely to get ADSL2+ due to distance. All new port growth is built using the new interface, so it's more and more common. So, older ADSL2+ CPE which support only ATM and G.bond won't work.