)]}'
{
  "commit": "2c13299a05e5544a5e79c2a970256a21f488a3fa",
  "tree": "1d277afb9b346388e1aa244484c3af41dcd6a72e",
  "parents": [
    "66d2ead7df2db9144605c973fcd80b88df33f81b"
  ],
  "author": {
    "name": "Pradosh Mohapatra",
    "email": "pmohapat@cumulusnetworks.com",
    "time": "Sat Sep 07 07:07:20 2013 +0000"
  },
  "committer": {
    "name": "David Lamparter",
    "email": "equinox@opensourcerouting.org",
    "time": "Tue Jun 03 15:08:08 2014 +0200"
  },
  "message": "bgpd: don\u0027t compare next-hop to router-id\n\nWhile announcing a path to a peer, the code currently compares the path\u0027s\nnext-hop with the peer\u0027s router-id. This can lead to problems as the router\nIDs are unique only within an AS. Suppose AS 1 sends route with next-hop\n10.1.1.1. It is possible that the speaker has an established BGP peering\nwith a router in AS 2 with router ID 10.1.1.1. The route will not be\nadvertised to that peer in AS 2.\n\nThe patch removes this check.\n\nSigned-off-by: Pradosh Mohapatra \u003cpmohapat@cumulusnetworks.com\u003e\nReviewed-by: Dinesh G Dutt \u003cddutt@cumulusnetworks.com\u003e\nReviewed-by: Shrijeet Mukherjee \u003cshm@cumulusnetworks.com\u003e\nSigned-off-by: David Lamparter \u003cequinox@opensourcerouting.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "46c0c85f66ae12463af6ca2050d2af08bddbce8b",
      "old_mode": 33188,
      "old_path": "bgpd/bgp_route.c",
      "new_id": "a919b54e9c04ab418f88e35b9845765ca26131ef",
      "new_mode": 33188,
      "new_path": "bgpd/bgp_route.c"
    }
  ]
}