Lab 7 - BGP Configuration Errors

Due: Friday at 11:55pm

Origin change events in BGP signify that a certain autonomous system (AS) has claimed authority over a block of IP addresses that were previously unallocated or previously belonged to another AS. The "new owner" will advertise the prefix(es) as belonging to it by advertising routes with the smallest possible distance metric. This will then cause other routers in the BGP subnet to change their routing tables, even if the change was not a legitimate change.

There are several types of origin change events:

A small number of origin change events occur normally as addresses are allocated or exchanged, but occasionally there will be a large number of origin change events related to a configuration error made by a router's administrator. When this happens, there will be a large number of origin change events resulting from the error that are typically followed by a large number of origin change events to correct the error.

Read the following papers, found at the UC Davis SecVis website, on how origin changes occur and how visualization techniques can be applied to detect abnormal origin changes:

Download and read each paper. The questions in the writeup are based on the contents of the papers. You do not have to download their visualization tool for this lab. There are also other network and security related tools on the SecVis website that you may find interesting, so feel free to peruse it.

Lab Writeup

  1. When might one have a legitimate origin change from unallocated addresses to an AS (O type events)?
  2. Describe how the claim ownership of owned IP addresses (C type) events differ from the claim ownership of unallocated addresses (O type) events.
  3. Describe what the hole punching (H type) event is.
  4. Why do some origin change events come in pairs and some do not? For example, the CSM (C type single AS to multiple AS) events are followed by CMS (C type multiple AS to single AS) events in the April 2001 event, so these events are paired.