1. 18 Aug, 2016 2 commits
    • The idea is to allow applications to contribute NeighbourMessageHandlers to
      handle ARP/NDP packets coming from a particular ConnectPoint, Interface or with
      a particular traffic selector. Applications can contribute different handlers
      for different ports, because they know how those ports will be used. Also,
      multiple applications can contribute handlers for different ports/interfaces
      without having to have one ARP handler for the entire network. The framework
      provides actions that the handler can choose to take - flood, proxy, reply, drop.
      The handler is free to implement some other action if none of these fit what it
      needs to do. The framework also handles many of the common tasks for ARP handlers,
      like parsing packets, abstracting the differences between ARP and NDP, implementing
      actions like replying to a request. This allows handlers to be very simple and
      easy to understand and implement.
      
      Change-Id: I313c723e9ebc3d0816eb79870ee0536780e7a640
      Jonathan Hart authored
    • Change-Id: I0fe6027e66815ab2e7db5e090dd5aea39b3c36e1
      Yuta HIGUCHI authored
  2. 17 Aug, 2016 11 commits
  3. 16 Aug, 2016 12 commits
  4. 15 Aug, 2016 4 commits
  5. 13 Aug, 2016 4 commits
  6. 12 Aug, 2016 7 commits