[port barricade] (22) port range conflicts with reserved port (22)

The list still exists, I found the link a while ago but lost it, the ports listed haven't changed though, will post the list here when I find it

Edit:

Found it

http://about.att.com/sites/broadband/network

port 22 isn't blocked, if the RG is giving an error that port 22 is reserved, its not saying its blocked, its saying its in use by something required for your services to work properly, no idea what that could be though

So the AT&T service requires exclusive access to port 22? This tells me the company has unrestricted access to any computer on my network with SSH capabilities. That is both unethical and scary!

I'd also like to add that my last router (which was the same model) didn't have this restriction. The router broke and AT&T sent a replacement, only when I tried to install the previous configuration did I discover this restriction. But you're saying that I can't use the most basic function of the internet because *all of sudden* "AT&T needs it".

Thanks!

We have a machine that I administer and access remotely via ssh port 22 on a more or less daily basis.   I can't remember when I last used it for sure, but it was certainly within the last couple of days.   Today it was not working and investigation revealed that it's no longer possible to forward port 22.   (Attempting to do results in "port range conflicts with reserved port")   As I say, I don't know with 100% certainty when it stopped working, but I see from the modem status that it was rebooted around 4:00am today (not by me).   I think it's pretty likely that we got a firmware update today that (for whatever reason, maybe not event intentionally) disabled port 22.

Honestly I have no clue why port 22 would be blocked, could be that someone thought it might improve security to block it on an RG level, the port isn't blocked network level though, could always in the mean time run some reverse proxy setup and direct some other port to port 22 on the correct device. I've done that before for running a 3D printer over the internet, not to port 22 mind you, but same idea.

I don't think it's being blocked at the network level, but because of the error message, it's pretty clear that it's being done at the modem level (NVG599).   Is there any way to find out when firmware updates would have  gone out, and what they contain?    Our current firmware version is 9.2.2h3d14, but I don't have any record of what it might have been yesterday or at some earlier time.

Yes, my workaround is to have the modem forward some other external port to the internal port 22.   That works, but it was pretty frustrating to have this stop working and have to figure out on my own by trial and error.

I just noticed this issue today as well. I have only had this router for about 2 weeks and I know mine was working initially when I setup all the firewall rules when I received it. I had a custom rule for port 22 defined and thought I should remove it and re-add it with the routers canned SSH Server rule and now get the (22) port range conflicts with reserved port (22) error.

We have some monitoring software that checks periodically to see if the connection is working.   It was working up until 3:30am on 4/26, and at 4:30am it failed and never came back.   The router was rebooted around 4:00am.  I assume there was an automatic software update at that time.

@IT_Moose 

As an employee you have no idea why it's being blocked? So the reasoning must be so top secret that you don't even get to know lol.

But seriously, this is actual censorship. I'm done with AT&T and I will further advise all my friends and family to do the same.

Hit the same issue last month at my cousin's apartment. I use SSH to manage his media server remotely.

Sometime April 2018 SSH stopped working remotely. I had to physically drive to his place to debug this stupid issue. I deleted the NAT rule and when I tried to add it again I got the error "(22) port range conflicts with reserved port (22)".

Is AT&T using this port or just trying to mess with their customers?

My mom is having the same issue:

- AT&T ISP connection

- AT&T-supplied BGW210-700 router

- Nat/Gaming, choose to open 'SSH Server' to her main computer

- Errors out 'port range conflicts with reserved port (22)'

She's spent quite a while on the phone with various AT&T Customer Disservice reps, eventually finding someone who was willing to report it to Engineering.

So it is 'engineering ticket k23971284', which is of course no guarantee that anything is going to be fixed, but at least it's something.

This is our first foray into AT&T 'engineering ticket' land, so I don't know if 'k' is enough prefix to pin down which ticketing database (they surely have dozens).

Feel free to refer to it in your own interactions on this issue, just in case that helps.

Hers is a BGW210-700.  I have a 5268AC which is not (YET) affected by this.  And I've seen other users report that their NVG589 or NVG599 was affected -- showing that whatever they changed was broader than just the single router.  I expect it'll break in the next 5268AC update; then (hopefully) get fixed on all in the next following update.

We will probably work around it using port forwarding (inbound something-other-than-22 -> 22 on her machine) (and maybe that's better overall, for reduced ssh probing from Our Friends Around The World).  But AT&T should still fix this, it's absurd bee ess.