Just in time for Hallo’ween, the lucky thirteenth post in the BGP code dive series. In this series, we’re working through the Snaproute Go implementation of BGP just to see how a production, open source BGP implementation really works. Along the way, we’re learning something about how larger, more complex projects are structured, and also something about the Go programming language. The entire series can be found on the series page.
In the last post in this series, we left off with our newly established peer just sitting there sending and receiving keepalives. But BGP peers are not designed just to exchange random traffic, they’re actually designed to exchange reachability and topology information about the network. BGP carries routing information in updated, which are actually complicated containers for a lot of different kinds of reachability information. In BGP, a reachable destination is called an NLRI, or Network Layer Reachability Information. Starting with this code dive, we’re going to look at how the snaproute BGP implementation processes updates, sorting out NLRIs, etc.
When you’re reading through code, whether looking for a better understanding of an implementation, a better understanding of a protocol, or even to figure out “what went wrong” on Continue reading
Over 90% of Microsoft's servers are based on OCP.
CenturyLink becomes a major fiber player.
ECOMP is involved too, of course.
The post Worth Reading: The Internet Needs a Security Upgrade appeared first on 'net work.
In case you are serious about going for the CCDE certification, I highly recommend you check out my friend Martin Duggan’s new lab(s) on Leanpub. His writing style is very good and its easy to follow along and i look forward to hitting this lab myself.
So go ahead and pay the man and get an additional CCDE lab for your studies. Take care!
https://leanpub.com/ccdepracticalstudies-practicelab1