Explore >> Select a destination
|
You are here 
|
www.jamieweb.net | ||
| | | | |
www.kentik.com
|
|
| | | | | In this post we continue our look at BGP - the protocol used to route traffic across the interconnected Autonomous Systems (AS) that make up the Internet - by clarifying the difference between eBGP and iBGP and then starting to dig into the basics of actual BGP configuration. We'll see how to establish peering connections with neighbors and to return a list of current sessions with useful information about each. | |
| | | | |
blog.oddbit.com
|
|
| | | | | Last week, Oskar Stenberg asked on Unix & Linux if it were possible to configure connectivity between two networks, both using the same address range, without involving network namespaces. That is, given this high level view of the network... ...can we set things up so that hosts on the "inner" network can communicate with hosts on the "outer" network using the range 192.168.3.0/24, and similarly for communication in the other direction? | |
| | | | |
networkphil.com
|
|
| | | | | BGP is the de facto routing protocol for inter-domain routing, or in other words, the global internet. It's used to exchange routing information among autonomous systems around the entire world. Therefore, it's extremely important we do what we can to secure BGP communications, what we advertise, and the methods we use to create peering relationships.... | |
| | | | |
go.sans.org
|
|
| | | |||
