Week 9 - asheesh8/NET-150-TECH-JOURNAL GitHub Wiki
RIP LAB ----------------
R1 ---> R2
R3---> R1
R1 to R2
So basically… the packet is a RIPv2 response message which means R1 is broadcasting its routing table to R2. 2 route entries in it, first - advertising 10.10.10.0 network with subnet mask of 255.255.255.0, next hop - 10.10.20.1.....Second entry is for 192.168.10.0 - same subnet mask but metric is 2 hop since.Its more than one router away.
R3 to R1
This one is also a RIPv2 response message, so R3 is sending routing table over to R1. Only one route entry - its directly connected network 192.168.10.0 with Subnet mask of 255.255.255.0 and next hop 10.10.10.2 and metric of 1 since directly connected.
BOTH entries have address fam of 2, IPv2 - route tag is 0
TROUBLESHOOTING
Accidentally added 192.168.20.0 as a network on R2 and R3 but they weren't connected to it, had to remove it with no network 192.168.20.0
Had to uncheck all filters in simulation mode and only select RIP to see the packets clearly