Is AXE5400 blocking port 22 outbound?
I routinely access a remote web server using SSH from my office Mac Mini. This uses port 22. I use this every day, so I'm confident it's all set up properly on both my end and at the remote server.
When I replaced my existing router with a new AXE5400, I can no longer connect to my server. The connection attempt times out.
My assumption is that the AXE5400 is blocking outbound port 22. I can't find any firewall or other settings that seem relevant to this problem.
Am I correct in assuming port 22 outbound is blocked, and if so, how do I unblock it?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
It's highly unlikely that your home router would block an SSH outgoing connection.
You have to check for any special configuration on your old router or any other network devices in you LAN that could cause this.
- Copy Link
- Report Inappropriate Content
I've figured out my problem. The AXE5400 is in fact NOT blocking port 22. I'll explain the problem in case it helps somebody else at some point.
When I SSH out of my office computer to my remote web server, the conversation takes place on port 22. To provide maximum security, I have the firewall on my web server set to only accept SSH requests if they originate at a specific IP address: the external IP address my ISP assigns to my office.
When I replaced my old router with the AXE5400, my ISP assigned a new IP address. So my web server refused to accept my SSH requests.
When I put my old router back in place, I got my old IP back, and everything worked fine. With the new AXE5400, SSH failed. This was 100% reproducible.
This seemed to point to the AXE5400 being the problem. But it wasn't, it was the change in IP address that caused the problem.
So the TL;DR is: don't assume your external IP address will stay the same when you get a new office (or home) router. It might, or it might not--it's up to your ISP.
In my case, I had set up the server firewall at least five years ago and had totally forgotten that it had a rule that depended upon my external IP.
- Copy Link
- Report Inappropriate Content
Hola, buenas tardes @terziyski
Me llamo Pau Monreal y soy beta tester y entusiasta de la tecnología.
Excelente análisis el que compartiste, esto seguro ayuda a otros usuarios. Efectivamente, los routers TP-Link no bloquean el puerto 22 saliente por defecto, así que si al cambiar el router deja de funcionar SSH, casi siempre la causa está en:
- Cambio de IP pública por parte del ISP (como fue tu caso).
- Algún cortafuegos en el servidor que filtra por IP.
- Algún software de seguridad en el PC que interfiere.
Para cualquiera que llegue aquí con un problema similar:
- Comprueben primero si la IP externa ha cambiado (por ejemplo en whatismyip.com).
- Si usan firewalls con reglas de IP, actualícenlas.
- Solo como último recurso revisen el router, ya que por defecto no filtra SSH saliente.
Muy buena aportación, @dana3 . Deberías marcar tu respuesta como solución para que quede visible en el hilo.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 291
Replies: 3
Voters 0
No one has voted for it yet.