AT&T's new router -- the 2Wire 3600HGV -- doesn't have a true bridge mode. This is a problem if you'd rather have a plain old DSL modem delegating DHCP and NAT to their router. There is, however, a way to get the 3600HGV into a bridge-like mode. There is a succinct version of how to do this floating around the internet, but here I've added the specific key presses needed in the specific case of connecting to an Airport Extreme. The bullet points below are my annotations.
If you haven't already, disable the wireless on the 2Wire:
1. http://192.168.1.254/
2. Settings > LAN > Wireless
3. Set the following options:
Wireless interface: [disabled]
Wi-Fi Protected setup: [disabled]
SSID Broadcast: [disabled]
4. Click "save" at the bottom of the page.
You will need your gateway's password to confirm the changes.
Now put the 2Wire into a bridge-like mode:
1. Set your router's WAN interface to get an IP address via DHCP. This is required at first so that the 2Wire recognizes your router.
- Open Airport Utility on mac or windows
- Right click Airport icon at left > Manual Setup
- Internet > Internet Connection > Connection Sharing: Off (Bridge Mode)
2. Plug your router's WAN interface to one of the 2Wire's LAN interfaces.
- Connect AT&T modem to Airport Extreme with ethernet.
3. Restart your router, let it get an IP address via DHCP.
- Update, Continue.
4. Log into the 2Wire router's interface. Go to Settings -> Firewall -> Applications, Pinholes, and DMZ
- http://192.168.1.254
5. Select your router under section (1).
- Choose [your router]
6. Click the DMZPlus button under section (2).
7. Click the Save button.
- password: [see sticker on bottom of 2Wire modem]
8. Restart your router, when it gets an address via DHCP again, it will be the public outside IP address. At this point, you can leave your router in DHCP mode (make sure the firewall on your router allows the DHCP renewal packets, which will occur every 10 minutes), or you can change your router's IP address assignment on the WAN interface to static, and use the same settings it received via DHCP.
- Go to Airport Utility
- Summary > IP Address: [should NOT look like 192.blah.blah.blah]
- Right click on Airport icon at left > Restart... [wait]
- Internet > Internet Connection > Connection Sharing: Share a public IP address
- I think he means "...you can PUT your router INTO DHCP mode..." which is the only thing that makes sense, since this is the point of the whole exercise. I have no idea what to do with respect to the rest of the sentence. Not sure if this applies to Airport Extreme or not.
9. On the 2Wire router go to Settings -> Firewall -> Advanced Configuration
- http://192.168.1.254
10. Uncheck the following: Stealth Mode, Block Ping, Strict UDP Session Control.
11. Check everything under Outbound Protocol Control except NetBIOS.
12. Uncheck NetBIOS under Inbound Protocol Control.
13. Uncheck all the Attack Detection checkboxes (7 of them).
14. Click Save.
- I had to restart my Airport Extreme to get the DHCP working on the Airport.
Some Notes:
1. I found this tidbit about how things might get reverted:
the 2wire router that's supplied for UVerse is awful. Follow the directions in post 2 of the link below to get it to work nicely with an AEBS, thats what i do and it works without any hitches, except when AT&T force software update and it switches it back to factory settings. You'll know thats happened though as the AEBS will start to complain about double-NAT.
http://forums.att.com/t5/Residential-Gateway/U-verse-for-BUSINESS-2Wire-3600HGV-bridge-mode-or-another-AT-amp/td-p/2707031
2. (Optional) Confirm that your devices have IP addresses assigned by Airport Extreme; by default they are 10.0.1.*. Check then in Airport Utility > Airport > Summary > Wireless Clients > DHCP Clients. See column "IP Address".
3. (Optional) On the 2Wire router: Settings > LAN > Status > Devices > Clear List, if you have many listed besides your router. After this, only your router should remain on the list.
