AT&T Fiber supports static IP blocks, but the process for ordering and configuring them isn’t automated or well-documented. If you’re running a home lab, hosting a personal site, or experimenting with enterprise-grade networking on a budget, a static IP block lets you assign fixed public IP addresses to your servers for reliable remote access or robust network setups. I recently configured a /28 static IP block on my AT&T Fiber connection using the Nokia BGW320-505 router, and this guide will walk you through the steps to set it up with confidence.

Why use a static IP block?

Static IP blocks are a game-changer for home labs or small networks, offering a range of fixed public IP addresses that you can assign to devices for direct internet access without relying on NAT. With AT&T Fiber, a /28 block provides 16 IP addresses, 13 of which are usable for your servers, switches, or a pfSense firewall. This setup is ideal for:

• Hosting websites or services: Run your own web server, like an Kubernetes cluster, with dedicated public IP addresses for the Ingress VIP and the API VIP.
• Remote access to management interfaces: Connect directly to tools like BMCs for seamless server management.
• Running public-facing applications: Avoid port forwarding complexities for apps or services exposed to the internet.

A /28 block gives you enough IPs to experiment with enterprise-grade setups—think high-availability clusters or multi-server networks—on budget-friendly hardware, making it perfect for home lab enthusiasts looking to push the limits of legacy gear.

Understanding IP Block Sizes

Before configuring your static IP block on AT&T Fiber, it’s helpful to understand the IP block sizes AT&T offers. The table below breaks down common options, showing the CIDR notation, subnet masks, total addresses, and usable addresses after AT&T reserves three IPs (for the network, broadcast, and gateway).

CIDR	Subnet Mask	Total Addresses	Usable Addresses
/29	255.255.255.248	8	5
/28	255.255.255.240	16	13
/27	255.255.255.224	32	29

How It Works:

• CIDR Notation: The number (e.g., /28) represents the bits in the subnet mask. For a /28, it’s 2^(32-28) = 16 total addresses.
• Reserved Addresses: AT&T reserves three addresses per block: one for the network, one for the broadcast, and one for their gateway.
• Usable Addresses: Subtract the reserved addresses from the total. For a /28, that’s 16 – 3 = 13 usable IPs.

For my home lab, I chose a /28 block, providing 13 usable IPs—perfect for assigning to my Dell servers, Cisco 1Gbps switch, and PDUs. A /29 (5 usable IPs) might work for smaller setups with just a couple of servers or a pfSense firewall, while a /27 (29 usable IPs) is overkill unless you’re building a mini data center with high-availability clusters or AI workloads.

Ordering a static IP block

AT&T Fiber offers static IP blocks, but their process for ordering one is murky, and documentation for setting it up on the Nokia BGW320-505 is practically nonexistent. If you’re building a home lab with servers or networking gear, here’s how to navigate the process based on my experience.

1. Contact AT&T Support: Start by reaching out to AT&T via live chat or by calling 1-800-288-2020. Their automated phone system can be a maze, so keep selecting options for ordering new services or technical support until you reach a live person. I recommend asking for a “Technical Support Representative” to ensure you’re talking to someone who understands static IP blocks.
2. Request Your IP Block: Tell the representative you want to purchase a static IP block for your AT&T Fiber connection. Specify the block size you need (e.g., /28 for 13 usable IPs). They’ll verify your account and confirm that your router (in my case, the Nokia BGW320-505) supports static IPs. You’ll be given the IP address range and maybe subnet details, but don’t expect immediate activation.
3. Prepare for a Truck Roll: In my case, AT&T required a technician visit my house to “activate” the static IP block, even though my connection and router were already set up. The technician checked my fiber connection and router but didn’t configure the IP block. They explained that their role is mostly “compliance”—ensuring the connection and hardware meet AT&T’s standards. Be prepared: you’ll likely need to configure the block yourself, as I did, since technician expertise in this area varies.
4. Capture the IP Block Details: The technician will have your static IP block details (e.g., IP range, subnet mask, gateway) on their phone or paperwork. In my case, the technician showed me the details on their phone, expecting me to write them down. Instead, I took a quick photo with my phone to capture everything accurately. You can also ask the technician to email you a screenshot or write down the details yourself. Double-check that you have the full IP range, subnet mask, and gateway address, as you’ll need these for configuring your Nokia BGW320-505.

AT&T’s lack of clear instructions for ordering or configuring static IPs can be frustrating, especially for home lab enthusiasts looking to leverage enterprise-grade networking on a budget. In the next section, I’ll walk you through setting up the /28 block on the BGW320-505, filling in the gaps AT&T leaves behind.

Configuring the Static IP Block on the Nokia BGW320-505

Setting up a /28 static IP block on your Nokia BGW320-505 router is a key step for running enterprise-grade networking in your home lab, whether you’re hosting a Kubernetes cluster or accessing BMCs on servers. AT&T’s lack of clear documentation and the mismatch between the technician’s provided information and the router’s interface make this process confusing. This guide, based on my experience with my servers and switches, breaks it down into clear steps to help you configure your static IP block with confidence.

Access the Router’s Web Interface

Open a browser and go to http://192.168.1.254, the default IP for the BGW320-505. If this doesn’t work, check the router’s label or your network settings for the correct IP. Log in using the access code on the router’s label, unless you’ve set a custom password.

Navigate to Public Subnet Settings

In the router’s web interface, click the Home Network tab, then select the Subnets and DHCP sub-tab. The HTML-based interface can be slow to load, so be patient. You’ll see sections for Private LAN and DHCP Server, but focus on the Public Subnet section for static IP configuration.

Understand the Technician’s Information

The technician provides several fields (e.g., IP range, subnet mask, gateway), but not all map directly to the router’s settings, which is a major source of confusion without AT&T’s documentation. The table below clarifies what you’ll receive and how it applies to the router:

Technician’s Field	Description	Router Field Mapping
Subnet Mask	The subnet mask for your block (e.g., 255.255.255.240 for a /28).	Enter in Public Subnet Mask.
Network Base Address	One of AT&T’s reserved addresses (network ID).	Not used in the router.
Router	The gateway address for your block.	Enter in Public Gateway Address.
Broadcast	One of AT&T’s reserved addresses (broadcast).	Not used in the router.
Usable Range	The range of assignable IPs (e.g., 162.198.50.241–162.198.40.253 for a /28).	Maps to DHCPv4 Start Address and DHCPv4 End Address.
IP Block Size	The size of your block (e.g., /28).	Not used in the router.
Primary DNS Server	AT&T’s primary DNS server.	Not used in this section (optional for manual device config).
Secondary DNS Server	AT&T’s secondary DNS server.	Not used in this section (optional for manual device config).

Why It’s Confusing: The Network Base Address, Broadcast, IP Block Size, and DNS fields don’t correspond to any router settings, yet the technician provides them. This mismatch can leave you second-guessing which fields are relevant, especially without clear guidance.

Configure the Public Subnet Settings

In the Public Subnet section, enter the following settings using the technician’s information:

• Public Subnet Mode: Set to On to enable static IP configuration.
• Allow Inbound Traffic: Set to On if you need external access to your devices (e.g., for hosting an OpenShift cluster or accessing iDRACs). Leave it Off for added security if external access isn’t required.
• Public Gateway Address: Enter the Router address from the technician (e.g., 162.198.50.254).
• Public Subnet Mask: Enter the Subnet Mask from the technician (e.g., 255.255.255.240 for a /28).
• DHCPv4 Start Address: Enter the first IP in the Usable Range (e.g., 162.198.50.241).
• DHCPv4 End Address: Enter the last IP in the Usable Range (e.g., 162.198.50.253).

Save the settings. The router may take a moment to apply them due to its clunky interface.

Tips for Success

• Save the Technician’s Details: As noted earlier, take a photo, write down, or request an emailed screenshot of the technician’s IP block details. You’ll need the exact Usable Range, Router (gateway), and Subnet Mask for this setup.
• Handle Router Quirks: The BGW320-505’s interface is slow, and saving changes can take time. If settings don’t apply, refresh the page or reboot the router.
• Secure Your Network: If Allow Inbound Traffic is On, ensure devices like a pfSense firewall have proper rules to protect your network.

With your /28 block configured, you’re ready to assign IPs to your home lab gear. The next section covers mapping these IPs to your devices for enterprise-grade networking on a budget.

Mapping Static IPs to Your Devices

After configuring your /28 static IP block on the Nokia BGW320-505, you need to assign the usable IPs to your home lab devices, such as servers, switches, or a pfSense firewall. AT&T’s lack of documentation makes this step tricky, but I’ll walk you through the method I used—mapping MAC addresses to static IPs via the router’s interface—which is straightforward and reliable. You can also manually configure IPs on devices, but it requires extra care to avoid conflicts.

Prerequisites

Before mapping IPs, ensure each device (e.g., server, switch, or firewall) is:

• Powered on and connected to the BGW320-505 via Ethernet or Wi-Fi.
• Assigned a temporary DHCP address by the router. This confirms the device is visible in the router’s interface.

Access the IP Allocation Settings

1. Log into the router at http://192.168.1.254 using the access code on the router’s access code or your custom password for protected pages.
2. Navigate to the Home Network tab, then select the IP Allocation sub-tab. This shows a table of connected devices with columns like:
   • IPv4 Address: The temporary DHCP address.
   • Device Name (if available): Identifies the device hostname.
   • MAC Address: The device NIC’s unique identifier.
   • Status: Shows “On” if the device is connected, “Off” if not.
   • Allocation: Displays “DHCP Allocation” for dynamic IPs or “Fixed Allocation” for static IPs.
   • Allocate Button: A button in each row to assign a static IP.

Map a Static IP Using a MAC Address

1. In the IP Allocation sub-tab, find the device you want to assign a static IP to (e.g., a Dell server for a Kubernetes cluster). Check its MAC Address and Status (ensure it’s “On”).
2. Click the Allocate button for that device.
3. Scroll to the bottom of the page to the IP address selection list. You’ll see two types of IPs:
   • Private Fixed: These are DHCP reservations for the private LAN (e.g., 192.168.1.x), not public static IPs.
   • Public Fixed: These are your static IPs from the /28 block (e.g., “Public Fixed: 162.108.50.241”).
4. Select a Public Fixed IP from the usable range provided by the technician (e.g., 162.198.50.241–162.198.50.253).
5. Click Save. The Allocation column should now show “Fixed Allocation” for that device.
6. Repeat for other devices, ensuring each gets a unique IP from the usable range.
7. Reboot the device or restart its network interface to apply the new IP. This may take a moment, as the BGW320-505’s interface can be slow.

Alternative: Manually Configure IPs

You can manually set static IPs on devices instead of using the router’s interface. Configure the device’s network settings with:

• IP Address: An IP from the usable range (e.g., 162.198.50.249).
• Subnet Mask: The technician-provided mask (e.g., 255.255.255.240 for a /28).
• Gateway: The Router address from the technician (e.g., 162.198.50.254).
• DNS Servers: Optionally use the technician’s Primary/Secondary DNS Servers or public DNS like 8.8.8.8.

Caution: Check the router’s IP Allocation list to ensure no other device is using the IP you choose, as conflicts can disrupt connectivity.

Tips for Success

• Track IP Assignments: Keep a list of which IPs are assigned to which devices to avoid conflicts. A spreadsheet works well.
• Use DHCP Reservations for Simplicity: Mapping MAC addresses in the router is easier than manual configuration, especially for mixed gear.
• Secure Your Setup: If you enabled Allow Inbound Traffic in the router, configure firewall rules on devices (e.g., pfSense) to protect public-facing services like web servers.
• Handle Router Quirks: The BGW320-505’s interface is clunky. If changes don’t apply, refresh the page or reboot the router.
• Leverage Legacy Gear: My setup uses older Dell servers and a Cisco 1Gbps switch alongside a Mellanox 100Gbps switch, showing you can achieve enterprise-grade networking on a budget.

This process lets you assign your /28 block’s IPs to create a robust, public-facing network for your home lab. Despite AT&T’s lack of guidance, these steps will help you map IPs confidently and bring your setup to life.