)]}'
{
  "commit": "57c5c6526df82970ca24293798d278862cf55106",
  "tree": "91847b2de0f333fa3a45691054f38c82f44f7609",
  "parents": [
    "94b6bfd28357dfa5a4f478b7393522816976c0b0"
  ],
  "author": {
    "name": "Paul Jakma",
    "email": "paul@quagga.net",
    "time": "Thu Jan 07 06:12:53 2010 +0000"
  },
  "committer": {
    "name": "Paul Jakma",
    "email": "paul@quagga.net",
    "time": "Wed Dec 08 17:11:18 2010 +0000"
  },
  "message": "ospfd: Reset neighbour inactivity timer for any packet arrival\n\n* The hello protocol monitors connectivity in 2 different ways:\n\n  a) local -\u003e remote\n  b) remote -\u003e local\n\n  Connectivity is required in both directions (2-way) for adjacencies to\n  form.\n\n  The first requires a round-trip to detect, and is done by advertising\n  which other hosts a router knows about in its hello messages.  This allows\n  a host to detect which other routers are and are not receiving its\n  message.  If a remote neighbour delists the local router, then the local\n  router raises a \"1-Way Received\" event.\n\n  The latter is straight-forward, and is detected by setting a timer for the\n  neighbour. If another Hello packet is not received within this time then\n  the neighbour is dead, and a separate \"Inactive\" event is raised.\n\n  These are 2 different and relatively independent measures.\n\n  Knowing that we can optimise the 2nd, remote-\u003elocal measure and reset\n  the timer when /any/ packet arrives from that neighbour. For any packet\n  is as good as a Hello packet. This can help in marginal situations, where\n  the number of protocol messages that must be sent sometimes can exceed\n  the capacity of the network to transmit the messages within the configured\n  dead-time. I.e. an OSPF network with lots of LSAs, slow links and/or\n  slow hosts (e.g. O(10k) LSAs, O(100kbit) links, embedded CPUs, and O(10s)\n  dead-times).\n\n  This optimisation allows an OSPF network to run closer to this margin,\n  and/or allows networks to perhaps better cope with rare periods of\n  exceptional load, where otherwise they would not.\n\n  It\u0027s fully compatible with plain OSPF implementations and doesn\u0027t\n  prejudice dead-neighbour detection.\n\n* ospf_nsm.h: Rename HelloReceived event to PacketReceived.\n* ospf_nsm.c: (nsm_hello_received) -\u003e nsm_packet_received\n* ospf_packet.c: Schedule PacketReceived whenever a valid message is\n  received.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "15fff349acf54eb4c3b2d89c0e743420cd3a1a7b",
      "old_mode": 33188,
      "old_path": "ospfd/ospf_nsm.c",
      "new_id": "1ab6ce3186ef77aa4d0e3d2f0578120058d34d7b",
      "new_mode": 33188,
      "new_path": "ospfd/ospf_nsm.c"
    },
    {
      "type": "modify",
      "old_id": "1121dae6108a856084fe72d0cc58a6dfc2fc2264",
      "old_mode": 33188,
      "old_path": "ospfd/ospf_nsm.h",
      "new_id": "4f2ae808393f530e50d306cb281661867f823ea6",
      "new_mode": 33188,
      "new_path": "ospfd/ospf_nsm.h"
    },
    {
      "type": "modify",
      "old_id": "57ed11404029afbf0e064653e83cd277a6a6b85b",
      "old_mode": 33188,
      "old_path": "ospfd/ospf_packet.c",
      "new_id": "80641b49e075268b69cac899813e3c3d5b94a48f",
      "new_mode": 33188,
      "new_path": "ospfd/ospf_packet.c"
    }
  ]
}