blocked ports?

Maybe this ATT article will help. It says:

As noted above, AT&T blocks certain ports that transfer malicious or disruptive traffic to protect our customers and our network. Below is more information about port blocking that is currently in place. We may block additional ports in the future based upon threat assessments.

Port 25 I believe can be unblocked for $49 by requesting it (assuming they still do that).  I don't know if any of the other ports can be requested to be unblocked probably because why would you want any of those unblocked?

This table doesn't distinguish between source port blocking and destination port blocking.  NTP, for example, is source port blocked (i.e. a destination port of 123 is allowed to pass, but a source port of 123 is not).  As your outbound traffic goes through NAT translation, the source port will be changed and the traffic will pass, if configured to not go through NAT, then the unchanged source port will be blocked.

Thank you both.

I was able to find what I needed and used that to get a port I needed opened 🙂

@rudyg305  How did you do this? What did you do to get your port unblocked?

I have a custom application that ATT seems to want to block after an hour or so ...  its not about configuring a pinhole through the firewall in the router (as it works for a period of time), its not about usage as I have unlimited gigabit over fiber ... it works for awhile and that after a time, my application stops working and I see the port is blocked (not in my router but somewhere on the ATT side).

It’s a dance .... I change the port ...it works until it stops, find the port blocked somewhere, change the port in the firewall and the application ..its works for a while ..rinse and repeat ...

@ackerthehacker, do you have a BGW 210 Gateway?  And if so, what version firmware?

One version of the firmware (1.6.7 if I remember correctly) had an issue where port forwarding would only work for a few hours, then fail.  The fix is to get off that version of the firmware.

Well it seems there is some inconsistency with what AT&T blocks.

This thread focused on ports, but it could be that what is getting blocked is the "application".

When opening up a connection, be it by http, https, or direct from a local application, there are firewall inspections that will happen and many times, regardless of the actual port, the firewall will see an application being used. Sometimes this is by correlating the ports used and the destination, other times is by the actual source or destination application.

AT&T blocks, on SOME towers, PCoIP, which breaks the ability to use VMwares Horizonview.

This is a business application and should not be blocked, as it provides remote access for employees working in the field.

It does not appear the used ports are blocked, but rather an inconsistency in firewall rules applied to the towers/traffic.