Sort by new | name | popular

Packet Captures

EIGRP_subnet_up.cap 1.3 KB

Submitted Sep 14, 2009

R4's 192.168.4.0/24 subnet is brought online. R1 receives updates from both R2 and R3 (only R2's update is shown in the capture). The poison-reverse in packet #9 informs R2 not to use R1 as a path to 192.168.4.0/24. The capture perspective is from R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 15 Duration: 18s Downloads: 5234

EIGRP_subnet_down.cap 1.8 KB

Submitted Sep 14, 2009

R4's interface to 192.168.4.0/24 goes down and the route is advertised as unreachable. Queries are issued by all routers to find a new path to the subnet but none exists, and the route is removed from the topology. Capture perspective is from R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 21 Duration: 23s Downloads: 3888

EIGRP_goodbye.cap 1.3 KB

Submitted Sep 14, 2009

R2 designates its interface facing R1 as passive. The final hello message from R2 (packet #9) has all its K values set to 255, designating the message as a "goodbye." Capture perspective is from R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 15 Duration: 43s Downloads: 4626

EIGRP_adjacency.cap 5.1 KB

Submitted Sep 14, 2009

Formation of an EIGRP adjacency between routers R1 and R2. Capture point is R1's 10.0.0.1 interface.

EIGRP Ethernet IP

Packets: 53 Duration: 104s Downloads: 5704

EIGRPv2_subnet_transition.cap 5.3 KB

Submitted Sep 14, 2009

R4's 2001:db8:0:400::/64 subnet goes down, then comes back up roughly thirty seconds later. Capture perspective from R1's 2001:db8:0:12::1 interface.

EIGRP Ethernet IPv6

Packets: 49 Duration: 65s Downloads: 4019

EIGRPv2_adjacency.cap 4.1 KB

Submitted Sep 14, 2009

Routers 1 and 2 form an EIGRPv2 adjacency and exchange IPv6 routes.

EIGRP Ethernet IPv6

Packets: 31 Duration: 52s Downloads: 4208