Working with Uverse Gateway

Discussion in 'Tomato Firmware' started by tismon, Aug 26, 2014.

  1. tismon

    tismon Serious Server Member

    To start, yes I've searched for this and I haven't found something that works.

    Basically, I'm trying to just use the Uverse Gateway as a modem only and I've run into an issue. I'm currently running Shibby on my RT-N16.

    This is what I've posted on the ATT support forum that has not helped.

    Gateway DMZ does not save
    I have a Gateway 3800hgv and trying to use it as a modem only via setting my router in DMZ in the gateway.

    Everything works initially and the public IP is allowed to go to the router, all port forwarding works, etc. That is, for about 10-20 min at most. After that, the setting is revoked in the gateway and DMZ is no longer set for the router (can provide screenshots if needed), but is rather set back to the default.

    I can trigger this reset by renewing the IP in the router, but it also happens on it's own fairly quickly. The automatic renew is set to 12 hours so this isn't the culprit for both cases.

    I've done a factory reset on the gateway to no avail.
    Am I missing a setting or do I just have a bad gateway?

    Thank you​

    I may be missing something that's causing this conflict, but I suspect that it's just the unit.
    Thank you for any support

  2. Grimson

    Grimson Networkin' Nut Member

    Is your provider using some kind of remote configuration/administration for your Gateway? If yes, this might cause the setting to be turned of.

    To exclude any DHCP issues just use a fixed IP on the RT-N16 and not DHCP.
  3. Monk E. Boy

    Monk E. Boy Network Guru Member

    Unfortunately that's probably something in the UVerse gateway. You'll need to contact AT&T to get that resolved, unfortunately.

    When I had UVerse (twice, in two different states) I just set the router as DMZ and it worked. I did have to add a firewall rule to let the IP address renew at the 50% point, but that may have since been fixed in Tomato. The only thing that happened without them was I would "lose" connectivity when the DHCP lease expired, since Tomato lost its IP address and had to request a new one via DHCP from the gateway, which took about 30-45 seconds and then everything went back to normal. Once the rule was in place, the lease renewed at the 50% mark and connectivity was solid.

    One thing I would check is how long your initial lease is for, because sometimes the first DHCP lease from a gateway or ISP is a short lease and then, once you've held onto it for that time, the subsequent leases are long. If that DHCP bug is still present in Tomato, and the lease is short, maybe it's expiring the DMZ at the end of the lease because Tomato didn't contact it at the 50% mark like it was supposed to.

    This was my workaround for the bug. You can try sticking this into Administration -> Scripts -> Firewall and see if it helps your situation:
    iptables -I INPUT -p udp --sport 67 --dport 68 -j ACCEPT
  4. Monk E. Boy

    Monk E. Boy Network Guru Member

    Unfortunately UVerse's DMZ mode is really, really weird. It actually gives the DMZ host the gateway's public IP address, so Tomato's WAN port will get a public IP and not a NAT IP.

    It certainly could be AT&T sending down some configuration periodically and blowing away his settings. I know Brighthouse will do that if you get in and change settings on your gateway (they actually won't give customers the username & password to gateways! Though the installer will usually share it with you if they don't feel you'll screw up settings left and right). Every night they push down whatever configuration they have saved for your gateway. Nothing like having to call your ISP to change your WiFi password - not to mention having your ISP record your WiFi password.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice