The post Worth Reading: Why culture company matters appeared first on rule 11 reader.
Our guests are Russ White, a network architect at LinkedIn; and Sue Hares, a consultant and chair of the Inter-Domain Routing Working Group at the IETF. They discuss the history of BGP, the original problems it was intended to solve, and what might change. This is an informed and wide-ranging conversation that also covers whitebox, software quality, and more. Thanks to Huawei, which covered travel and accommodations to enable the Packet Pushers to attend IETF 99 and record some shows to spread the news about IETF projects and initiatives.
You can jump to the original post on Packet Pushers here.
The post On the ‘web: What’s Wrong with BGP appeared first on rule 11 reader.
The post Worth Reading: When the cloud deletes our data appeared first on rule 11 reader.
The post Worth Reading: The rise of fourth wave computing appeared first on rule 11 reader.
On this edition of the Network Collective’s History of Networking, Juliusz Chroboczek sits down to discuss the origins of the BABEL routing protocol. You can see the original post over on the Network Collective here.
The post The History of Networking: BABEL appeared first on rule 11 reader.
The post Worth Reading: Malware in your screen appeared first on rule 11 reader.
The post Cross Links in a Spine and Leaf appeared first on rule 11 reader.
The post Worth Reading: It’s okay to forget what you read appeared first on rule 11 reader.
The post Worth Reading: Wave System’s DPU architecture appeared first on rule 11 reader.
The post Worth Reading: Updating Surveillance Laws appeared first on rule 11 reader.
The post Worth Reading: Multitasking without Thrashing appeared first on rule 11 reader.
The post Worth Reading: The calculus of service availability appeared first on rule 11 reader.
The post Worth Reading: IoT needs a paradigm shift appeared first on rule 11 reader.
The post Worth Reading: ROI is not a cybersecurity concept appeared first on rule 11 reader.
After Daniel Walton visited the History of Networking at the Network Collective, I went back and poked at BGP permanent route oscillations just to refresh my memory. Since I spent the time, I thought it was worth a post, with some observations. When working with networking problems, it is always wise to begin with a network, so…
For those who are interested, I’m pretty much following RFC3345 in this explanation.
There are two BGP route reflectors here, in two different clusters, labeled A and D. The metric for each link is listed on the links between the RR clients, B, C, and E, and the RRs; the cost of the link between the RRs is 1. A single route, 2001:db8:3e8:100::/64 is being advertised in with an AS path of the same length from three different eBGP peering points, each with a different MED. E is receiving the route with a MED of 0, C with a MED of 1, and B with a MED of 10.
Starting with A, walk through one cycle of the persistent oscillation. At A there are two routes—
edge MED IGP Cost
C 1 4
B 10 5 (BEST)
When A runs the bestpath calculation, Continue reading