New Member
•
12 Messages
BGW320 public static IP block
I'm an AT&T Fiber customer with 1gig service. I want to test out hosting some of my own infrastructure and asked AT&T for a public subnet to do it on. I've paid for a public static IP block (X.X.X.56/29) and configured it in my BGW320 as follows:
I've assigned through the fixed allocation DHCP the .57 address to an machine connected to the BGW320 via the LAN ports, and while it gets DHCP and can ping the gateway (.62), it does not have any network access beyond that. I've had the same result with both an OPNSense box and a Macbook.
I've disabled the firewall, packet inspection, etc., and have also not configured any IP passthrough. I can ping the .57 box from other machines both on the public subnet while connected to the BGW, as well as from machines behind the BGW320's NAT on the broader "home" network. This has stumped me, ATT support, and the 2 different techs who have come out to my house.
It feels like there is a route missing that links my public subnet with my router and the broader ATT network. I would appreciate any help in either how to properly setup my public subnet, or even how to further troubleshoot the situation.
I had considered setting up my OPNSense box as a cascaded router, but after one of the many tech visits I no longer have that option available in the UI (which seems odd). I did successfully setup the OPNSense via IP passthrough, but that only got that box the assigned router public IP and I reverted those settings. I probably could configure the OPNSense box to handle both, but I thought for a relatively simple setup (just hosting a couple servers on the public subnet), it was overkill.
Thank you in advance for any help. This has been a huge fiasco.
JefferMC
ACE - Expert
•
32.3K Messages
4 months ago
Yeah, I'm getting lost after 12.122.141.213 too.
0
0
JefferMC
ACE - Expert
•
32.3K Messages
4 months ago
Or after the next shift starts. :)
0
0
dave006
Scholar
•
3.7K Messages
4 months ago
@FastAndLight
Your traceroute worked to the other Public IP Block because you were sending ICPM Ping commands outside of your local Fiber Connection. I can reach the other block also but loopback is not going to work from within your network but we should be able to reach your .60 address from our side if the routing was actually setup correctly for your Static IP Block.
Did you get charged the $99 fee for setup of your Static IP Block?
If yes then request another tech Dispatch to setup your failed configuration on their provided BGW320 since your Static block is not be routed correctly and you need a new Static IP Block. The phone rep will not have a clue but force them to escalate your issue. They can only follow a specific script and never expect them to call you back (ever).
It does happen but is extremely rare. 99% chance you will get a tech dispatch but the tech will also not likely have a clue but can call their support and get it resolved. As you may have noticed they really don't have great direct support for residential Static Blocks even though they still offer the service.
The earlier @ATTHelp rep offered the paid support option since you mentioned your OPNSense box in your initial post. But they can't help with this specific issue.
ETA: added more detail...
Dave
(edited)
0
0
FastAndLight
New Member
•
12 Messages
4 months ago
@JefferMC Funny how that timing works out....
@dave006 Not sure what distinction you are trying to make. I was using a server in google cloud to send the traceroute, both to my block as well as the other. We share the same path for the first 6 hops, and then after that my traceroute dies, and theirs continues on. It is also interesting that the second to last hop on their traceroute is the same block as my fiber connection external ip, 107.192.0.0/11.
I am completely sure that my static block is setup incorrectly on AT&T's side, but I also have zero confidence that anyone who works at AT&T (@ATTHelp ) can either test that or fix it. I'm going to give them another call now to try to remove the block and re-add it.
(edited)
0
0
dave006
Scholar
•
3.7K Messages
4 months ago
@FastAndLight
You did not happen to mention that you were using a remote server to try your tracert or ping commands to your Static IP block.
Did they charge you the $99 fee for your Static IP block setup?
They can't remove it and re-add it but if they remove it the next option is to add a new Static IP Block. That's why I asked if you were charged the regular $99 fee for the Static IP block setup. However the phone reps ability will vary as you have already noticed.
Dave
0
0
FastAndLight
New Member
•
12 Messages
4 months ago
@dave006 The billing is an interesting view. So, I agreed to changes in my account, but to the tune of $15 / month. I don't believe the initial change included anything like a $100 setup fee.
After multiple tries I still did not speak to anyone at AT&T customer service / technical support who has any idea what a static IP block is. I hesitated to ask them to remove anything from my account since I don't have any faith in what they are doing. The second or third time I called the rep couldn't even find my block to confirm it back to me. @ATTHelp is there a number I can call to deal with a team that specifically has some understanding of static IP blocks?
(edited)
0
0
dave006
Scholar
•
3.7K Messages
4 months ago
@FastAndLight
Yes the $15 monthly fee is for the /29 block. There should have also been a $99 one-time setup fee that covered a tech dispatch to configure your Static IP block on your AT&T Gateway (router).
Did you happen to have your Static IP block included on your initial order and Install?
Over the years fewer and fewer install techs could actually configure the Static block (They did not receive training). Lately they they only provide you with the Static IP block as documented on your work order sheet that dispatched the tech. And for some techs that is even a challenge.
Maybe @ATTHelp can help you in a private DM session but you will have to keep checking for a DM message chat request indicator on the top tool bar here on the forum. It is the "DM" ICON between the att.com link and the "Bell" Notification link (mine indicates 99+) as show in the screenshot below. It will have a "Red" status flag with a 1.
0
0
SharphSonirtm
New Member
•
7 Messages
4 months ago
I observe both IPv4 and IPv6 addresses. To ensure tests focus on IPv4, I conduct tests that avoid IPv6, such as pinging by number rather than name. My suspicion is that the issue lies in the incorrect routing from the Static Block to the Dynamic Public. Finding someone to resolve this may prove challenging.
0
0
FastAndLight
New Member
•
12 Messages
4 months ago
@SharphSonirtm I have been pinging by IP. Also, because routing doesn't work, DNS doesn't work. No need to be distracted by IPv6.
@dave006 The tech sent me a screenshot of something via text. No paper or anything. That lack of "official" feeling documentation, combined with the fact that no one at AT&T customer service can quickly and fluently read me back the static IP block information makes me very suspicious that it was ever setup correctly in the first place. I'll be watching for a DM request, though I may have better luck with customer service / tech support roulette.
Unfortunately, I've yet to talk to someone at AT&T (including @ATTHelp on here) who has a grasp of the situation and what we can do to resolve it.
0
0