h.koch's profile

Tutor

 • 

5 Messages

Wednesday, July 4th, 2018 4:37 PM

port range conflicts with reserved port (22)

ssh is the standard for secure connections between networked computers, , and 22 is the standard port used by ssh.

For secure connections (over the internet) to my home computer, I had my u-verse modem forward port 22 to my desktop machine.

(On the modem Arris NVG599, this type of setup option is in the NAT/gaming section.)

This worked fine for over a year. Bur recently, this stopped working all of a sudden.

and when I went through the setup again, the modem complained: port range conflicts with reserved port (22)

Clearly, AT&T has accessed my modem remotely and silently disabled the possibility for using port 22, without informing me.

I find this absolutely DESPICABLE BEHAVIOR.

 

Community Support

 • 

230.7K Messages

6 years ago

Hi, @h.koch


That is odd behavior. It sounds like there may be a faulty setting where the gateway is thinking that the forwarding rule is already in use. The easiest fix maybe to factory reset the gateway and set everything back up once again. When resetting, make sure to do it through the gateway GUI instead of the red button to ensure a full reset. I apologize about the inconvenience this may cause.


Be sure to copy your settings, so you can set it back up easily. Let us know if you run into any more issues.



Lafayette, AT&T Community Specialist


Tutor

 • 

5 Messages

6 years ago

Hi ATTCares

I already switched to a different port for ssh,
and I am not going to waste more time trying other things.
In any case, I doubt that resetting the gateway will do any good; see e.g.
[port barricade] (22) port range conflicts with reserved port (22) and the 12+ replies to that post.

(I only became aware of this discussion

when a "Recommendations" area showed up on the right of my page, after I submitted my last post.)

You may want to read that discussion.

 

Contributor

 • 

1 Message

6 years ago

Hi H.Koch,

 

FWIW, I have the exact same scenario and experience.  Blocking standard ports is 

 

It is terrible.  Security through using non standard ports is not security.

 

Best case they "reserved" it through their own use... but breaking my connection silently when it worked for years is terrible, because I don't know until I'm too far away to fix it.

 

I confirm this is a change/update pushed out to these devices that accidentally or intentionally reserved this port silently and only deleting and recreating the rule made that obvious.  

 

It forces me to do unnatural things to IP packets to work around it.  Please stop it.

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.