I tried to ssh from my mac to a remote linux server but got timeout error.
I could ssh when I switched from WiFi to personal hotpot (4G) I can ssh, but I couldn't when using WiFi.
I tried sftp and FileZilla, all failed when using WiFi.
I also tried ssh to the server using another machine, and it turned out the server is also fine.
I tried to reboot the router, but couldn't solve the problem yet.
MacBook Air, macOS 13.3
LLYXC wrote:
Could you tell me more about how to do traceroute for disconnection identification?
The command is traceroute on macOS, and the target host is specified as the parameter.
man traceroute for full syntax details.
The command shows each router in the path.
Some intermediate routers can (will) show as * when an ICMP or name is not available, and that for whatever reason.
In your case, the first hops will be different, while you will (should) eventually get to the same router(s) used for traffic connecting to the ssh target system.
$ traceroute www.duckduckgo.com
traceroute to duckduckgo.com (52.149.246.39), 64 hops max, 52 byte packets
{hops 1-to-4 removed for privacy}
5 et-0-3-0.mpr1.yul1.ca.zip.zayo.com (64.124.142.45) 31.312 ms 30.965 ms 31.513 ms
6 ae66-0.ymq01-96cbe-1b.ntwk.msn.net (104.44.36.147) 31.391 ms
ae64-0.ymq01-96cbe-1a.ntwk.msn.net (104.44.36.145) 34.722 ms 34.436 ms
7 ae24-0.icr02.yto30.ntwk.msn.net (104.44.233.137) 32.104 ms 35.534 ms 31.698 ms
8 be-102-0.ibr01.yto30.ntwk.msn.net (104.44.20.163) 40.782 ms 39.977 ms *
9 be-2-0.ibr02.yto30.ntwk.msn.net (104.44.7.160) 38.466 ms
be-1-0.ibr02.yto20.ntwk.msn.net (104.44.7.163) 38.481 ms 38.404 ms
10 * be-1-0.ibr02.yto20.ntwk.msn.net (104.44.7.163) 38.762 ms
be-4-0.ibr02.nyc30.ntwk.msn.net (104.44.16.151) 39.630 ms
11 be-5-0.ibr02.cle02.ntwk.msn.net (104.44.19.145) 54.111 ms
be-4-0.ibr02.nyc30.ntwk.msn.net (104.44.16.151) 44.134 ms 39.552 ms
12 ae144-0.icr03.bl20.ntwk.msn.net (104.44.32.41) 36.631 ms
be-3-0.ibr02.ch2.ntwk.msn.net (104.44.29.253) 55.163 ms
ae160-0.icr01.bl20.ntwk.msn.net (104.44.22.210) 61.037 ms
13 ae164-0.icr03.bl20.ntwk.msn.net (104.44.32.43) 39.388 ms
be-9-0.ibr02.atl30.ntwk.msn.net (104.44.18.71) 53.894 ms *
14 * * *
15 * * *
{more stuff}
I'd also check the firmware in the router, and ensure it is the most current available from the vendor. Subnet routing issues can show up as discontinuities, whether that is due to an add-on first-few-hops VPN client app, or due to the particular setup of the local IP network routing, or other such.
LLYXC wrote:
Could you tell me more about how to do traceroute for disconnection identification?
The command is traceroute on macOS, and the target host is specified as the parameter.
man traceroute for full syntax details.
The command shows each router in the path.
Some intermediate routers can (will) show as * when an ICMP or name is not available, and that for whatever reason.
In your case, the first hops will be different, while you will (should) eventually get to the same router(s) used for traffic connecting to the ssh target system.
$ traceroute www.duckduckgo.com
traceroute to duckduckgo.com (52.149.246.39), 64 hops max, 52 byte packets
{hops 1-to-4 removed for privacy}
5 et-0-3-0.mpr1.yul1.ca.zip.zayo.com (64.124.142.45) 31.312 ms 30.965 ms 31.513 ms
6 ae66-0.ymq01-96cbe-1b.ntwk.msn.net (104.44.36.147) 31.391 ms
ae64-0.ymq01-96cbe-1a.ntwk.msn.net (104.44.36.145) 34.722 ms 34.436 ms
7 ae24-0.icr02.yto30.ntwk.msn.net (104.44.233.137) 32.104 ms 35.534 ms 31.698 ms
8 be-102-0.ibr01.yto30.ntwk.msn.net (104.44.20.163) 40.782 ms 39.977 ms *
9 be-2-0.ibr02.yto30.ntwk.msn.net (104.44.7.160) 38.466 ms
be-1-0.ibr02.yto20.ntwk.msn.net (104.44.7.163) 38.481 ms 38.404 ms
10 * be-1-0.ibr02.yto20.ntwk.msn.net (104.44.7.163) 38.762 ms
be-4-0.ibr02.nyc30.ntwk.msn.net (104.44.16.151) 39.630 ms
11 be-5-0.ibr02.cle02.ntwk.msn.net (104.44.19.145) 54.111 ms
be-4-0.ibr02.nyc30.ntwk.msn.net (104.44.16.151) 44.134 ms 39.552 ms
12 ae144-0.icr03.bl20.ntwk.msn.net (104.44.32.41) 36.631 ms
be-3-0.ibr02.ch2.ntwk.msn.net (104.44.29.253) 55.163 ms
ae160-0.icr01.bl20.ntwk.msn.net (104.44.22.210) 61.037 ms
13 ae164-0.icr03.bl20.ntwk.msn.net (104.44.32.43) 39.388 ms
be-9-0.ibr02.atl30.ntwk.msn.net (104.44.18.71) 53.894 ms *
14 * * *
15 * * *
{more stuff}
I'd also check the firmware in the router, and ensure it is the most current available from the vendor. Subnet routing issues can show up as discontinuities, whether that is due to an add-on first-few-hops VPN client app, or due to the particular setup of the local IP network routing, or other such.
Update macOS, and then try a traceroute to try to identify where the disconnect arises.
If there are add-on security apps or anti-malware apps or first-few-hops VPN add-ons or related “security “ tools, remove all those per vendors’ instructions, restart, and try again.
Could you tell me more about how to do traceroute for disconnection identification?
ssh from Mac to remote linux server timeout