Skip to main content

CCNA Recap: Routing Protocols (Distance Vector + Link State)

Distance Vector  & Link State
Interior and Exterior Gateway Protocols

——— Distance Vector ——————
           how far        which way
* good for small
* little configuration
- RIPv2 [IGP]
        - hop count, max 15
     




- EIGRP [IGP]
- neighbor adjacencies
- runs multiple protocols
- (Cisco proprietary
- ietf standard
* summary route distance 5
* internal distance 90
* external 170
        - bandwidth
                - lowest
        - Delay
            - adds those together through all the links it has to traverse
    - bandwidth + delay = feasible distance
    - unicast+multicast - 224.0.0.10
    - only those who need it

I only know what someone else told me.

hello - unreliable, multi
update -reliable uni/multi
ack - un uni
query -reliable uni/multi
reply - reliable un

— Link State ——————
AD = Administrative Distance.
 Are you up or are you down.
- up = get there
- down = no
Not hops but bandwidth cost
* scalable
* consider the speed

[These are also Interior Gateway Protocols]
* OSPF (AD = 110)
        * Enterprise
* IS-IS (AD - 115)
* provider networks
    * FP
    * OTV
        * = cisco proprietary

When adjacencies happen, a router will advertise its entire database, and each router has to have it’s own copy and they have to synchronize.

Not really advertising routes, enabling procol on those interfaces and allow the HELLOs out of them.

Shortest Path First algorithm

You’re not trying to reach the prefix

——LS———
Phase 1: Reliable flooding
 - each node knows the cost to neighbors
- each node knows the entire network topology

Phase 2: Route Calculation
- Dijkstra’s algorithm

========== =========== =========
AS - autonomous system (RFC 1930)
* independent entity, under your control

Unique AS # given by IANA
* who manage IP blocks and root servers

- BGP
    - Most popular!
    - De Facto standard!
    - Routes between one AS to another AS

ISPs have different AS numbers.
Routers know where the different numbers are (BGP, border gateway protocol)

Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more