5de448e3 | 19-Feb-2017 |
David van Moolenbroek <david@minix3.org> |
Import NetBSD ndp(8)
Like arp(8), this utility already uses the NetBSD 8 protocol for talking to the operating system through routing sockets.
Like arp(8), this utility is not fully functional, due
Import NetBSD ndp(8)
Like arp(8), this utility already uses the NetBSD 8 protocol for talking to the operating system through routing sockets.
Like arp(8), this utility is not fully functional, due to limitations of lwIP. While ndp(8) should provide a proper (read-only) view of the contents of the Neighbor Discovery table, any attempts to modify the table will fail. In addition, various other ndp(8) features are not supported. On MINIX 3, the prefix and default router lists are not managed by the operating system however, but rather by dhcpcd(8); therefore, an implementation of the features related to those lists would not provide any actual functionality.
Change-Id: I479bfc8141ba69fe50c1b2f7091933267ce6fa3e
show more ...
|
04e82b7d | 15-Feb-2017 |
David van Moolenbroek <david@minix3.org> |
Import NetBSD arp(8)
Behaviorally this port should already be largely on par with the NetBSD 8 version, in that it sets the RTF_LLDATA flag on routing socket requests to indicate that they target li
Import NetBSD arp(8)
Behaviorally this port should already be largely on par with the NetBSD 8 version, in that it sets the RTF_LLDATA flag on routing socket requests to indicate that they target link-local data.
Many parts of the arp(8) functionality are currently not yet supported by the operating system, largely due to lwIP not exposing appropriate means of implementing them.
Change-Id: Icfac054b4deddda03eee4acf0e261aa48cd031ba
show more ...
|