什么原因可能导致网络最初 ping 不通,然后又成功

什么原因可能导致网络最初 ping 不通,然后又成功

每次我启动服务器时,无论我让它“上线”多长时间,前几次 ping 似乎都会失败(SSH 等也是如此)。示例:

josh@homeserv:/var/www/html/amp$ ping 192.168.0.200
PING 192.168.0.200 (192.168.0.200) 56(84) bytes of data.
From 192.168.0.201 icmp_seq=1 Destination Host Unreachable
From 192.168.0.201 icmp_seq=2 Destination Host Unreachable
From 192.168.0.201 icmp_seq=3 Destination Host Unreachable
64 bytes from 192.168.0.201: icmp_seq=4 ttl=64 time=1195 ms
64 bytes from 192.168.0.201: icmp_seq=13 ttl=64 time=137 ms
64 bytes from 192.168.0.201: icmp_seq=15 ttl=64 time=128 ms
64 bytes from 192.168.0.201: icmp_seq=18 ttl=64 time=112 ms
64 bytes from 192.168.0.201: icmp_seq=19 ttl=64 time=2.89 ms
64 bytes from 192.168.0.201: icmp_seq=20 ttl=64 time=4.16 ms
64 bytes from 192.168.0.201: icmp_seq=21 ttl=64 time=5.55 ms
64 bytes from 192.168.0.201: icmp_seq=22 ttl=64 time=2.04 ms
64 bytes from 192.168.0.201: icmp_seq=23 ttl=64 time=2.64 ms
64 bytes from 192.168.0.201: icmp_seq=24 ttl=64 time=3.32 ms
64 bytes from 192.168.0.201: icmp_seq=25 ttl=64 time=4.13 ms
64 bytes from 192.168.0.201: icmp_seq=26 ttl=64 time=2.01 ms
64 bytes from 192.168.0.201: icmp_seq=27 ttl=64 time=3.07 ms
64 bytes from 192.168.0.201: icmp_seq=28 ttl=64 time=3.99 ms
64 bytes from 192.168.0.201: icmp_seq=29 ttl=64 time=5.05 ms
64 bytes from 192.168.0.201: icmp_seq=30 ttl=64 time=10.5 ms
64 bytes from 192.168.0.201: icmp_seq=31 ttl=64 time=2.93 ms
64 bytes from 192.168.0.201: icmp_seq=32 ttl=64 time=4.78 ms
64 bytes from 192.168.0.201: icmp_seq=33 ttl=64 time=9.18 ms
64 bytes from 192.168.0.201: icmp_seq=34 ttl=64 time=3.97 ms
64 bytes from 192.168.0.201: icmp_seq=35 ttl=64 time=2.06 ms
64 bytes from 192.168.0.201: icmp_seq=36 ttl=64 time=5.06 ms
64 bytes from 192.168.0.201: icmp_seq=37 ttl=64 time=3.00 ms
64 bytes from 192.168.0.201: icmp_seq=38 ttl=64 time=3.43 ms
64 bytes from 192.168.0.201: icmp_seq=39 ttl=64 time=3.64 ms
64 bytes from 192.168.0.201: icmp_seq=40 ttl=64 time=5.70 ms
64 bytes from 192.168.0.201: icmp_seq=41 ttl=64 time=2.57 ms
64 bytes from 192.168.0.201: icmp_seq=42 ttl=64 time=4.75 ms
64 bytes from 192.168.0.201: icmp_seq=43 ttl=64 time=2.32 ms
64 bytes from 192.168.0.201: icmp_seq=44 ttl=64 time=3.75 ms
64 bytes from 192.168.0.201: icmp_seq=45 ttl=64 time=33.5 ms
64 bytes from 192.168.0.201: icmp_seq=46 ttl=64 time=176 ms

请注意,前 3 次失败,第 4 次、第 5 次和第 6 次都很慢,然后一切正常,直到最后一次变得非常高。我几乎可以处理那个“峰值”,但启动让我很头疼,因为这是我的“构建”环境,它必须稳定,而且由于内存泄漏和电源要求,我必须定期重新启动它(RCD 经常出现故障,有时是因为我必须做的事情比我的备用电源所能承受的时间更长)。

连接是通过 wifi 进行的,因此某种程度的间歇性峰值是不可避免的,但这似乎是 100% 一致的,每次我启动机器时,我都必须先启动网络接口,然后它才会响应我。

如果需要日志文件,请告知哪些(我不知道哪个有用,到目前为止已经设法避免在网络方面做任何过于繁重的事情,而现在这种回避确实让生活变得更加困难。

相关内容