AT&T UVerse with Sonicwall

A location at work needed more bandwidth.  Unfortunately, the only option in the area was AT&T UVerse.  The location is a remote office that was currently being connected back to the main building through a Sonicwall NSA2400 site-to-site VPN.  I had heard and read alot of horror stories about trying to get the UVerse in bridge mode, getting IP Passthrough to work, etc.  Before the service was activated I printed out a 15 page doc that someone else used everytime they had to do this.  Luckily, I didn’t need it, it wasn’t that complicated.

Here are the details:

  • The UVerse modem is model 5258AC
  • The Sonicwall is an NSA2400
  • I order static IPs and got a block of 8

The technician gave me a handwritten paper with my IPs, Gateway, and Subnet Mask on it.  It said:

  • Subnet Mask: 255.255.255.248
  • Gateway: 76.xxx.xxx.94
  • First Usable: 76.xxx.xxx.89
  • Last Usable: 76.xxx.xxx.93

So I started looking and testing.  It is kinda confusing the way AT&T does this, more like I’ve just not seen it done this way.

  1. With nothing connected to the UVerse modem, I set my laptop to the first IP available in the block and connected it via ethernet.  I opened my browser and went to 192.168.1.254 which brought me to the web interface of the UVerse modem.
  2. I looked around and this was the significant portion I saw in there,uverse2
  3. Once i figured out that the router had the 94 address, I realized I could probably set the WAN interface on the sonicwall to one of my other available addresses and be fine, which is what I did.weldsonicwall
  4. I then put my laptop on the LAN and was able to browse the network and the internet as expected.

No changes were made to the UVerse router at all.  Changed the IP address of the WAN interface to an available IP in my static block and everything was up as expected.  I then changed the IP on the other end of my site-to-site VPN tunnel and it came right up.

Alot easier than I expected and none of the nightmares others had reported.