warp-scan cannot scan the IP

[LeeCenY]

Version number
v1.2.3

Describe the bug
Scanning IPs was fine in the first two or three days, but today the same operation cannot scan available IPs, and the ping error timeout occurs. I wonder if it is related to the reason why I scanned too frequently in the past.

To Reproduce
Steps to reproduce the behavior:

1. cd /path/cmd/warp-scan
2. go build
3. ./warp-scan
4. See error

time=2024-06-07T20:02:25.835+08:00 level=DEBUG msg="calling expire" subsystem=scanner/engine
time=2024-06-07T20:02:25.836+08:00 level=DEBUG msg="Expire: Not in ideal mode" subsystem=engine/queue
time=2024-06-07T20:02:26.037+08:00 level=DEBUG msg="Started new scanning round" subsystem=scanner/engine
time=2024-06-07T20:02:26.037+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=162.159.195.179
time=2024-06-07T20:02:32.415+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=162.159.195.179 error="read udp 192.168.31.112:57333->162.159.195.179:4233: i/o timeout"
time=2024-06-07T20:02:32.415+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=2606:4700:d1:0:c7c0:58d4:4995:9f3d
time=2024-06-07T20:02:32.417+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=2606:4700:d1:0:c7c0:58d4:4995:9f3d error="dial udp [2606:4700:d1:0:c7c0:58d4:4995:9f3d]:1843: connect: no route to host"
time=2024-06-07T20:02:32.417+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=162.159.193.91
time=2024-06-07T20:02:32.693+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=162.159.193.91 error="error sending random packet: write udp 192.168.31.112:59169->162.159.193.91:7156: write: connection refused"
time=2024-06-07T20:02:32.693+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=188.114.96.249
time=2024-06-07T20:02:39.536+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=188.114.96.249 error="read udp 192.168.31.112:62482->188.114.96.249:4198: i/o timeout"
time=2024-06-07T20:02:39.536+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=2606:4700:d0:0:5693:e8f0:ae54:e90d
time=2024-06-07T20:02:39.538+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=2606:4700:d0:0:5693:e8f0:ae54:e90d error="dial udp [2606:4700:d0:0:5693:e8f0:ae54:e90d]:988: connect: no route to host"
time=2024-06-07T20:02:39.538+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=188.114.98.147
time=2024-06-07T20:02:46.691+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=188.114.98.147 error="read udp 192.168.31.112:53239->188.114.98.147:880: i/o timeout"
time=2024-06-07T20:02:46.692+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=162.159.192.39
time=2024-06-07T20:02:52.831+08:00 level=ERROR msg="ping error" subsystem=scanner/engine addr=162.159.192.39 error="read udp 192.168.31.112:64649->162.159.192.39:1180: i/o timeout"
time=2024-06-07T20:02:52.831+08:00 level=DEBUG msg="pinging IP" subsystem=scanner/engine addr=188.114.99.87
Address RTT (ping) Time

Expected behavior
A clear and concise description of what you expected to happen.
Scan to list of available IPs
Address RTT (ping) Time
188.114.99.162:3581 442.45725ms 2024-06-07 13:52:32
188.114.98.126:903 448.178042ms 2024-06-07 13:52:34
188.114.96.46:7156 461.876083ms 2024-06-07 13:52:35
188.114.98.69:968 462.946584ms 2024-06-07 13:52:17
188.114.97.111:2408 463.743042ms 2024-06-07 13:52:20
162.159.192.57:8886 471.729417ms 2024-06-07 13:52:23
188.114.96.175:1014 492.443ms 2024-06-07 13:52:18
188.114.99.115:987 493.265042ms 2024-06-07 13:52:15

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS 14.5

Additional context
Add any other context about the problem here.

[pars1500]