Searched refs:reachable (Results 1 – 10 of 10) sorted by relevance
77 # Make sure it is reachable83 # Make sure it is reachable121 # IP should be reachable142 # IP should still be reachable
421 uint_t reachable, retrans; in incoming_ra() local438 reachable = ntohl(ra->nd_ra_reachable); in incoming_ra()439 if (reachable != 0 && in incoming_ra()440 reachable != pi->pi_BaseReachableTime) { in incoming_ra()441 pi->pi_BaseReachableTime = reachable; in incoming_ra()1239 uint_t reachable, retrans; in verify_ra_consistency() local1254 reachable = ntohl(ra->nd_ra_reachable); in verify_ra_consistency()1255 if (reachable != 0 && pi->pi_AdvReachableTime != 0 && in verify_ra_consistency()1256 reachable != pi->pi_AdvReachableTime) { in verify_ra_consistency()1260 reachable, pi->pi_AdvReachableTime); in verify_ra_consistency()
77 # is reachable via routing information before ipsecconf(1m)
401 /(?:lost|reachable):\s+\d+ bytes in (\d+) blocks/) {
40 filesystem is reachable, then the usual svcadm(1M) invocations to clear
677 fail with: "host not reachable", or with a timeout error. If your ftp
1516 fail to contact a reachable host. The most prominent reason for this
26 to selectively clone a subroutine and data reachable from that
622 to selectively clone a subroutine and data reachable from that
2039 that are easily reachable.