随机高端口号上的多个连接

随机高端口号上的多个连接

我的笔记本电脑出现了一些问题,导致 Ubuntu 20.04 速度变慢。检查 netstat 显示在随机高端口上有多个已建立的保持连接,这些连接源自外部计算机的端口 443。CPU 使用率很高,但找不到正在使用它的内容。我刚刚卸载并重新安装了 chrome,这有帮助。这些连接正常吗?不是 IT 人员,只是感觉有点奇怪。

    Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       Timer
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      off (0.00/0/0)
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      off (0.00/0/0)
tcp        0      0 192.168.1.12:53884      104.18.130.236:443      ESTABLISHED keepalive (20.72/0/0)
tcp        0      0 192.168.1.12:53266      104.18.40.222:443       ESTABLISHED keepalive (4.34/0/0)
tcp        0      0 192.168.1.12:55602      151.101.65.181:443      ESTABLISHED keepalive (35.06/0/0)
tcp        0      0 192.168.1.12:45592      23.55.3.87:443          ESTABLISHED keepalive (0.24/0/0)
tcp        0      0 192.168.1.12:33384      172.217.24.34:443       ESTABLISHED keepalive (24.82/0/0)
tcp        0      0 192.168.1.12:50656      142.250.4.188:5228      ESTABLISHED keepalive (37.10/0/0)
tcp        0      0 192.168.1.12:55890      142.250.66.163:443      ESTABLISHED keepalive (20.72/0/0)
tcp        0      0 192.168.1.12:51840      142.251.143.163:443     ESTABLISHED keepalive (2.29/0/0)
tcp        0      0 192.168.1.12:38292      130.211.33.34:443       ESTABLISHED keepalive (2.29/0/0)
tcp        0      0 192.168.1.12:34296      23.55.3.87:443          ESTABLISHED keepalive (0.24/0/0)
tcp        0      0 192.168.1.12:49454      142.251.221.66:443      ESTABLISHED keepalive (4.34/0/0)
tcp        0      0 192.168.1.12:60130      207.65.33.78:443        ESTABLISHED keepalive (30.96/0/0)
tcp        0      0 192.168.1.12:47348      18.67.111.87:443        ESTABLISHED keepalive (41.20/0/0)
tcp        0      0 192.168.1.12:41100      151.101.65.181:443      ESTABLISHED keepalive (33.01/0/0)
tcp        0      0 192.168.1.12:46776      172.217.24.33:443       ESTABLISHED keepalive (6.39/0/0)
tcp        0      0 192.168.1.12:59592      172.217.24.42:443       ESTABLISHED keepalive (4.34/0/6)
tcp        0      0 192.168.1.12:42124      151.101.65.108:443      ESTABLISHED keepalive (30.96/0/0)
tcp        0      0 192.168.1.12:33774      52.223.2.229:443        ESTABLISHED keepalive (24.82/0/0)
tcp        0      0 192.168.1.12:41768      142.251.221.78:443      ESTABLISHED keepalive (0.24/0/0)
tcp        0      0 192.168.1.12:41594      172.217.24.42:443       ESTABLISHED keepalive (20.72/0/0)
tcp        0      0 192.168.1.12:54544      172.217.24.40:443       ESTABLISHED keepalive (16.62/0/0)
tcp        0      0 192.168.1.12:58966      198.252.206.25:443      ESTABLISHED keepalive (22.77/0/0)
tcp        0      0 192.168.1.12:45588      23.55.3.87:443          ESTABLISHED keepalive (0.24/0/0)
tcp        0      0 192.168.1.12:39586      151.101.65.181:443      ESTABLISHED keepalive (35.06/0/0)
tcp        0      0 192.168.1.12:55776      172.64.150.156:443      ESTABLISHED keepalive (18.67/0/0)
tcp        0      0 192.168.1.12:56604      18.239.199.109:443      ESTABLISHED keepalive (30.96/0/0)
tcp        0      0 192.168.1.12:45982      146.75.92.193:443       ESTABLISHED keepalive (16.62/0/0)
tcp        0      0 192.168.1.12:41662      104.18.130.236:443      ESTABLISHED keepalive (24.81/0/0)
tcp        0      0 192.168.1.12:41732      13.224.181.123:443      ESTABLISHED keepalive (28.91/0/0)
tcp        0      0 192.168.1.12:34918      172.217.24.34:443       ESTABLISHED keepalive (18.67/0/0)
tcp        0      0 192.168.1.12:35414      172.217.24.42:443       ESTABLISHED keepalive (12.52/0/0)
tcp        0      0 192.168.1.12:34312      23.55.3.87:443          ESTABLISHED keepalive (2.28/0/0)
tcp        0      0 192.168.1.12:35358      216.239.38.178:443      ESTABLISHED keepalive (20.72/0/0)
tcp        0      0 192.168.1.12:59152      172.217.24.34:443       ESTABLISHED keepalive (43.24/0/0)
tcp        0      0 192.168.1.12:41328      204.79.197.204:443      ESTABLISHED keepalive (4.33/0/0)
tcp        0      0 192.168.1.12:52160      216.239.32.116:443      ESTABLISHED keepalive (30.96/0/0)
tcp        0      0 192.168.1.12:46762      172.217.24.33:443       ESTABLISHED keepalive (6.38/0/0)
tcp        0      0 192.168.1.12:47002      104.18.32.137:443       ESTABLISHED keepalive (20.71/0/0)
tcp6       0      0 ::1:631                 :::*                    LISTEN      off (0.00/0/0)
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           off (0.00/0/0)
udp        0      0 127.0.0.53:53           0.0.0.0:*                           off (0.00/0/0)
udp        0      0 192.168.1.12:68         192.168.1.1:67          ESTABLISHED off (0.00/0/0)
udp        0      0 0.0.0.0:631             0.0.0.0:*                           off (0.00/0/0)
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           off (0.00/0/0)
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           off (0.00/0/0)
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           off (0.00/0/0)
udp        0      0 0.0.0.0:58776           0.0.0.0:*                           off (0.00/0/0)
udp6       0      0 :::1900                 :::*                                off (0.00/0/0)
udp6       0      0 :::56808                :::*                                off (0.00/0/0)
udp6       0      0 :::5353                 :::*                                off (0.00/0/0)
raw6       0      0 :::58                   :::*                    7           off (0.00/0/0)

谢谢阅读

答案1

所有这些连接都是从您的 PC 传出到外部 Web 服务器的。尝试找出哪个本地进程发起了这些连接。我猜可能是 Web 浏览器。

sudo netstat -lntp

上述命令将在最后一列显示进程号。

下面是一个输出示例,最后一列的进程号在所有行中都是 6895:

tcp        0      0 10.1.1.111:44248        34.149.100.209:443      ESTABLISHED     6895/firefox-trunk  
tcp        0      0 10.1.1.111:53812        34.107.243.93:443       ESTABLISHED     6895/firefox-trunk  
tcp        0      0 10.1.1.111:33646        198.252.206.25:443      ESTABLISHED     6895/firefox-trunk

流程详情:

ps -ef | grep 6895

找到这些进程并停止或终止它们。探索这些进程启动的原因和时间。

您可以使用该top命令发现CPU负载过高的真正原因。

sudo top

查找% CPU列中值较高的进程。

相关内容