route 172.* > /dev/null
giggity
(yes I know that isn’t how it works)
1 Like
Thats what I said internally to the other Ninjas.
I definitely appreciate you guys trying to help, even when it’s outside the Plex network. I managed to fix my network though, but not in a way that many AT&T users will be able to do. I have a static IP block (not in the 172.0.0.0 /8 range) and I wasn’t using all of them. So I reconfigured things to have the majority of my regular traffic behind one of the static IPs instead of the DHCP address from the 172.0.0.0 /8 range they provide. All seems fine for me now. The problem is still there, but just bypassed for me.
like this?
ip deny 172.0.0.0/8 any any
2 Likes
AT&T is assigning me a static block to resolve this issue. It’ll be ready by the time I get up for work (which is great cause I work from home). It was affecting my ability to work as well as play. AT&T has no ETA on a resolution for the 172.x.x.x issue.
Glad you were able to resolve your issue as well.
Who did you contact at AT&T to get a static IP block outside the range of affected IP addresses? My first two portions of my IP address that is having the issue is 172.10.x.x. Would the number that I need to call be the 24/7 tech support line? I want to report the issue, but the last time that I had to contact support I was bounced around India and all they did was tell me to reboot my hardware. Any info / help is much appreciated.
855-525-1840 is the number to the “Connect” team. From there, they can transfer you to the “Gig” team. Remember, to remind them how frustrating this has been. Happy hunting.
1 Like
Static IP blocks likely won’t come out of that /12. That /12 is probably dedicated for the dynamic IP pool for the WAN interface on the U-Verse gateways. Static blocks will use RIP to route the /30 subnets and larger to the dynamic WAN IP.
No resolution for me tonight. Called the “Connect” team and was transferred to the “Gig” team. The representative there tried to tell me that plex.tv is associated with malicious software. I had to explain that this was not the case, at which time he promptly reversed course and admitted that they had been receiving calls regarding connectivity issues with the 172.x.x.x IP range. No higher level support available this late at night to be able to assign me a new IP range. Will follow up and report back tomorrow.
Still looks to be down for the 172.X.X.X range, any additional info available?
My call with them last night ended up being escalated and I was told they’d call back within 48 hours. And I don’t doubt it could take them that long to figure out which device is blocking the 172.x IPs AND get the config fixed. Could be longer.
Since the AT&T 172.x subnet appears to only be used for the DHCP addresses of their fiber internet, the bandaid fix is to not use that address. So if they can provision it quickly enough for you, you’ll want to request a block of static IPs. That should be in a very different IP range and sourcing your traffic from one of those IPs will get around this issue. Not exactly a simple fix though. And it will cost money because they charge for the static IP blocks.
Still not working. I did talk with TAC L3 at ATT today and they are aware of the issue. Of course they could not provide an ETA. I did notice that this is also affecting Sony services as well. Basically, any IP peer between ATT fiber and Level3 are being affected.
Anything specific that I need to say to get advanced technical support? I am not even sure how to report the problem in technical language. I was thinking of telling them that the request to plex.tv is timing out on port 443. Is that enough to report?
I’m having the same problem.
I don’t have Fibre but I have AT&T Uverse internet and I haven’t been able to login since last night.
You still probably pull from the same seemingly problematic DHCP pool. If your IP address starts with 172, you’re likely suffering the same issue as the rest of us. If you’re just accessing your server locally, you should be able to reconfigure your server to allow you to access it locally without authentication.
What’s the first part of your WAN IP address? Is it 172.x?
If you’re not sure how to find it, go here and this site will tell you.
Lol, have the same thing too. Since I tried everything I deleted all paired devices. and my tv wasn’t showing the code. I did hotspot on my phone, connected the tv there, and the code appeared instantly, changed to browser. But probably plex won’t work after you back to your wifi. Unless that server is not at the att connection
This does not appear to work with the Plex Android TV app. I already had that configured for my local subnet and saw the same behavior as /u/bryandrexler. However from an iOS device that was logged in already, everything played fine. And I was able to cast from that to the very same Android device.
I had issues with my connectivity previously and started a session on one connection to be carried to the problematic one. For clarity, my job’s network was blocking plex.tv and after I authenticated at home I could carry the session to work. Hopefully it’d work like this for your TV device as well.
