Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

AT&T U-Verse Pace Router Setup for SmartLink

Member ✭✭
edited October 2018 in New Ideas
I'm on a U-Verse DSL connection at home (works quite well) that is provisioned through an AT&T branded Pace wireless router.  I've written an illustrated guide for configuring this router, Pace model 5031NV, for use by SmartLink.  The router doesn't provide UPnP support but does have a fairly easy to use interface for configuring port forwarding.

This guide may be useful to people who use similar routers from Pace, or may be generally useful for learning the concepts of port forwarding in a home router.

You can pull down a copy of the PDF from this location: https://1drv.ms/b/s!AgvdqNf7I04lgdh6H5w1FyC2hJu_pA

If you have questions, please reply to this Community thread and I'll try to answer them.

Dave Fisher / NX6D


Welcome!

It looks like you're new here. Sign in or register to get started.

Comments

  • Now it's 2023, and I have the same problem with a newer ATT fiber modem. It's a model BGW320-505 which does 1 Gig up and down. Does anyone have the settings to get the port forwarding to work with this one? Thanks de KF8QL
  • Hi Dave,

    Just curious if you were able to finally get your issue resolved with Smarklink remote access as I have ATT Fiber and have put through port forwarding for 4993 and 4994 but still doesn't work from remote location,.
    Thanks,
    Mike
    k8nre
  • Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin
    edited February 27

    Mike, is your ISP provider using CGNAT?

    You can open a support ticket and we will look into it for you.

    If you're not familiar with networking but want to check if your Internet Service Provider (ISP) is using Carrier-Grade NAT (CGNAT), follow this simple step-by-step guide:

    Step 1: Find Your Public IP Address

    1. Open a web browser (Chrome, Edge, Firefox, etc.).
    2. Go to https://whatismyipaddress.com/ or just search "What is my IP" on Google.
    3. Note down the IPv4 address displayed (it’s usually in the format of ****.****.****.****, like 192.168.1.100).

    Step 2: Find Your Router’s WAN IP Address

    1. Open a Command Prompt (Windows) or Terminal (Mac/Linux).
    2. Type:
      • Windows: ipconfig and press Enter
      • Mac/Linux: ifconfig or ip a and press Enter
    3. Look for the "Default Gateway" or "Router" IP.
    4. Open a web browser and type this IP into the address bar (e.g., 192.168.1.1). Press Enter.
    5. Log in to your router (usually "admin" for username and a password set by you or on a sticker on the router).
    6. Find the WAN IP Address in the router’s status or network settings.

    Step 3: Compare the IP Addresses

    • If your public IP (Step 1) matches your router’s WAN IP (Step 2) → Your ISP is NOT using CGNAT.
    • If the public IP and WAN IP are different, and your WAN IP starts with:
      • 100.64.x.x – 100.127.x.x (a special CGNAT range)
      • 10.x.x.x, 172.16.x.x – 172.31.x.x, or 192.168.x.x (private IPs)
      • Then your ISP IS using CGNAT.

    Step 4: Optional - Confirm with a Traceroute Test

    1. Open Command Prompt/Terminal again.
    2. Type:
      • Windows: tracert 8.8.8.8 and press Enter
      • Mac/Linux: traceroute 8.8.8.8 and press Enter
    3. Look at the first few hops. If you see 100.x.x.x or private IP addresses, your ISP is using CGNAT.

    Why It Matters?

    • CGNAT can block inbound connections, which affects remote access, gaming, and some networking applications such as SmartLink.
    • If you need a public IP for things like running a server or remote access, contact your ISP and ask if they offer a static IP or an option to bypass CGNAT.
  • Nothing in the 100.x range as here is my trace from ATT side. I assume the 108.82.184.1 mentioned doesn't make it private or part of CGNAT correct?

    traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 40 byte packets
    1 192.168.1.254 (192.168.1.254) 4.625 ms 4.297 ms 4.105 ms
    2 108-82-184-1.lightspeed.clmboh.sbcglobal.net (108.82.184.1) 7.494 ms 8.104 ms 7.358 ms
    3 71.151.141.128 (71.151.141.128) 8.610 ms 7.860 ms 9.024 ms
    4 32.130.19.130 (32.130.19.130) 20.520 ms 17.723 ms 16.898 ms
    5 32.130.20.28 (32.130.20.28) 18.554 ms 18.402 ms 18.846 ms
    6 32.130.91.19 (32.130.91.19) 20.186 ms 18.044 ms 18.912 ms
    7 12.255.10.56 (12.255.10.56) 18.866 ms
    12.255.10.44 (12.255.10.44) 19.059 ms
    12.255.10.54 (12.255.10.54) 20.432 ms
  • Additionally, I have opened up ticket and working with Tim Your request (#70711) has been updated. but thought I'd search the forums specific to ATT router.

    The odd thing is i can see from logs that I'm coming in and I've put in the port forwarding for 4993/udp and 4994/tcp. and I leave the network settings in smart link option on the 8400m to automatic.. when I connect from secondary ISP that I have it reboots my 8400M.. has done this several times.. so scratching my head on that one..
  • Member
    edited February 27
    Update. solved issue.. still have to port forward within the ATT router for 4993 and 4994 but I also have to manually add those two ports under the SmartLink setup MANUAL portion within the 8400M on the network tab.. so now my remote access is working successfully..

Leave a Comment