|
Protocol »
User Datagram Protocol
(Info)
Viewing 1 - 16 of 16 captures
SNMPv2c_get_requests.cap (894 bytes)
SNMPv2c get requests are issued from a manager to an SNMP agent in order to monitor the bandwidth utilization of an interface.
path_MTU_discovery.cap (6.2 KB)
Tracepath is used to determine the MTU of the path between hosts 192.168.0.2 and .1.2. Packet #6 contains an ICMP "fragmentation needed" message, indicating the MTU for that hop is 1400 bytes. RADIUS.cap (775 bytes)
A RADIUS authentication request is issued from a switch at 10.0.0.1 on behalf of an EAP client. The user authenticates via MD5 challenge with the username "John.McGuirk" and the password "S0cc3r".
TDP.cap (2.8 KB)
P2 and PE2 exchange Tag Distribution Protocol hellos and form an adjacency over TCP port 711. LDP_adjacency.cap (5.7 KB)
PE1 and P1 multicast LDP hellos to 224.0.0.2 on UDP port 646. They then establish an adjacency on TCP port 646 and exchange labels. Auto-RP.cap (726 bytes)
Routers 2 and 3 have been configured as candidate RPs, and multicast RP announcements to 239.0.1.39. Router 1 is the RP. R1 sees the candidate RP announcements from R2 and R3, and designates R3 the RP because it has a higher IP address (3.3.3.3). R1 multicasts the RP mapping to 224.0.1.40. The capture is from the R1-R2 link. PIM-DM_pruning.cap (10.2 KB)
The multicast source at 172.16.40.10 begins sending traffic to the group 239.123.123.123, and PIM-DM floods the traffic down the tree. R4 has no group members, and prunes itself from the tree. R2 and R3 then realize they have no members, and each prunes itself from the tree. The capture shows R2 receiving the multicast traffic flooded from R1 and subsequently pruning itself every three minutes. ISAKMP_sa_setup.cap (2.0 KB)
An ISAKMP session is established prior to setting up an IPsec tunnel. Phase one occurs in main mode, and phase two occurs in quick mode.
GLBP_election.cap (8.4 KB)
Routers 1, 2, and 3 participate in a GLBP election. R1 becomes the AVG due to having the highest priority (200), and R3 becomes the standby GLBP. All three routers become AVFs. HSRP_coup.cap (3.9 KB)
Initially only routers 3 (active) and 2 (standby) are online. R1 comes online with a priority higher than R3's. R1 takes over as the active router (the coup occurs in packet #22) almost immediately. R2 is bumped down to passive and R3 becomes the standby router.
HSRP_failover.cap (3.0 KB)
R1 is the active router, R3 is the standby, and R2 is passive. R1 goes offline and R3 takes over as active after ten seconds. R2 is then promoted to the standby state.
HSRP_election.cap (3.7 KB)
The Ethernet link shared by routers 1, 2, and 3 comes online. R1 wins the HSRP election because it has a priority of 200 (versus the default of 100 held by the other two routers). R3 becomes the standby router.
RIPv1_subnet_down.cap (1.0 KB)
RIPv1 routes are being flooded on the R1-R2 link. R2's connection to 192.168.2.0/24 goes down, and the route is advertised as unreachable (metric 16) in packet #5. Capture perspective from R1's 10.0.1.1 interface. RIPv1.cap (876 bytes)
A RIPv1 router periodically flooding its database. Capture perspective from R1's 10.0.1.1 interface. RIPv2_subnet_down.cap (1.3 KB)
RIPv2 routes are being flooded on the R1-R2 link. R2's connection to 192.168.2.0/24 goes down, and the route is advertised as unreachable (metric 16) in packet #7. Capture perspective from R1's 10.0.0.1 interface. RIPv2.cap (1.7 KB)
A RIPv2 router periodically flooding its database. Capture perspective from R1's 10.0.0.1 interface. Viewing 1 - 16 of 16 captures
|
Navigation
Armory
Online Toolbox
|