-
Notifications
You must be signed in to change notification settings - Fork 788
Host checking with fping stalling #629
Description
Running v1.23 with fping: Version 3.13
This does not happen using standard ping either, which is just like issue #485 mentions. I notice fping sweeping the entire subnet instead of just the active hosts.
Following subnets setup for Host(Ping Check):
192.168.25.0/24
172.17.0.0/16
pingCheck.php seems to stall. If I manually run the script, it loads up and pings through 192.168.25.0/24 and returns results to the command line but stalls indefinitely at:
192.168.25.254 : xmt/rcv/%loss = 1/0/100%
Until I try to ctrl-c the script, then it runs through the 172.17.0.0/16 subnet, to eventually stall on at:
172.17.255.254 : xmt/rcv/%loss = 0/0/0%
The oddity is there are no assigned IP's in 172.17.0.0/16 to ping check. I can disable host checking on the 172.17.0.0/16 and the pingCheck.php scripts completes without issue and updates the assigned IP's in the 192.168.25.0/24 just fine. Disabling host checking on the 192.168.25.0/24 and enabling it on the 172.17.0.0/16 and running pingCheck.php comes back with "No addresses to check", which is still true since nothing has been assigned in that subnet. But why when both 192.168.25.0/24 and 172.17.0.0/16 are enabled for host checking does it attempt to ping through 172.17.0.0/16 when no hosts are assigned?