ff02::1 39 bytes from fe80::206:5bff:fe68:249b%en0: adric 26 bytes from fe80::2b0:d0ff:fe05:fc06%en0: ace 37 bytes from fe80::202:b3ff:fe65:604b%en0: jo forty bytes from fe80::2b0:d0ff:fef4:c6c5%en0: sarah-jane ^C --- ff02::1 ping6 records --- 1 packets transmitted, 1 packets acquired, +3 duplicates, zero% packet loss If we examine instance 5-4 and instance 5-5 we will see that now not all nodes replied to the node info request. regrettably, those queries will not be but an entire a part of the traditional. If ping is operating ok, then it's going to even be attainable to telnet, whether you just get a "connection refused" message in reaction. observe that almost all models of telnet don't have an particular choice to let you specify the interface for use for a link-local handle. To get round this, a few structures immediately use a default interface. On systems that aid scope IDs in addresses, those can be utilized as a substitute. instance 5-6 indicates a few examples of those in use. the 1st instance, on Linux, indicates telnetting to a unscoped link-local deal with and the corresponding mistakes.
Rated 5 – based on votes of