Skip to main content

Route Filtering with Different Routing Protocol

 Route Filtering with Any Routing Protocol

Route filtering is used to selectively control which routes are advertised or received from neighboring routers, helping manage traffic flows, reduce memory utilization, or enhance security. In vector-based routing protocols, filtering occurs during the advertisement of routes. In link-state protocols like OSPF, filtering typically happens at the Area Border Routers (ABRs) when routes enter or leave an area.

Example of Route Filtering in OSPF

In this example, ip prefix-list is used to create filtering rules that deny or permit specific routes. These rules are applied using the area command to control which routes enter or exit an area.

  • Technical Tip: When configuring OSPF route filtering with prefix lists, always keep in mind the hierarchical structure of areas and the flow of LSAs. Filtering usually applies at ABRs to prevent specific LSAs from being propagated across areas.

R2 Configuration:

ip prefix-list PREFIX-FILTER seq 5 deny 172.16.1.0/24

ip prefix-list PREFIX-FILTER seq 10 permit 0.0.0.0/0 le 32

router ospf 1

 area 0 filter-list prefix PREFIX-FILTER in

EIGRP Filtering

EIGRP Route Filtering can be done using distribute lists, route-maps, or access-lists. Distribute lists can be applied in inbound or outbound directions to filter updates before they are added to the routing table or before being sent to neighbors.

  • Technical Tip: Always use the correct direction (in or out) when applying distribute lists to avoid unintended filtering of important routes.

Offset List: Used in EIGRP to influence route selection by modifying the metric for a given prefix. Example: offset-list 1 in 100 Ethernet 0/0 adds 100 to the metric of the matched prefix.

OSPF Filtering

In OSPF, routes are not advertised directly; instead, LSAs are propagated. Filtering LSAs is more complex because OSPF requires all routers in an area to have identical Link-State Databases (LSDBs). Filtering typically happens through:

  • Type 3 LSA Filtering: Prevents ABRs from generating specific Type 3 LSAs (summary routes) for other areas. Example: area 34 filter-list prefix PREFIX-FILTER in.
  • Distribute Lists: Filters routes before they are installed in the local routing table but does not affect the LSDB. Example: distribute-list prefix FILTER-LIST in.
  • Technical Tip: Be prepared to explain the limitations of OSPF filtering and how it differs from other protocols like EIGRP. In particular, know that filtering in OSPF focuses on LSAs, not routes, and how distribute lists work in OSPF.

ABR LSA Suppression: You can also use the area range no-advertise option to prevent the generation of specific summary LSAs.

Database Filter: Prevents LSAs from being flooded out of a specific interface. Example:

interface Serial 1/5

ip ospf database-filter all out

Local OSPF Filtering

In scenarios where routes need to be filtered locally, distribute lists can prevent specific routes from being installed in the Routing Information Base (RIB) without modifying the LSDB. However, remember that this affects only local routing decisions and does not impact LSA propagation.

  • Technical Tip: Filtering in OSPF is often tricky since LSAs still propagate. Be ready to explain how local filtering only impacts the RIB and doesn't affect how routes are distributed across OSPF neighbors.

BGP Filtering

BGP Filtering is used to control route advertisements between Autonomous Systems. Methods include:

  • Outbound Route Filtering (ORF): Allows a router to send a prefix list to its neighbor, asking it not to send certain routes. This reduces the routing table size on both sides.
  • Prefix Lists and Route-Maps: BGP uses prefix lists and route-maps extensively for filtering inbound or outbound advertisements.
  • Technical Tip: In interviews, highlight that BGP filtering is critical in large networks for controlling routing policies and preventing the advertisement of unnecessary routes.

Summary of Technical Tips:

  • OSPF Route Filtering: Focuses on LSAs, not routes. Use distribute lists carefully, as they only affect local routing tables.
  • EIGRP Filtering: Use distribute lists and offset lists to manipulate EIGRP routing decisions effectively. Be clear about the direction (in or out) of the filtering.
  • BGP Filtering: Emphasize the importance of prefix-lists and route-maps in controlling BGP advertisements and how ORF reduces overhead.

By understanding how route filtering works in different protocols, you'll be prepared to answer both conceptual and technical questions in interviews, focusing on real-world use cases where route filtering optimizes traffic flow and network performance.

Comments

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

AS Path Prepending: Controlling Inbound Traffic in BGP

AS Path Prepending is a BGP feature used to make a specific path appear less preferred by artificially lengthening the AS path. This is done by adding your AS number multiple times to the AS path. It is a common method to influence inbound traffic from external networks. Longer AS Path = Less preferred route . Example Scenario : You have two ISPs: ISP1 (through CE1) and ISP2 (through CE2). You want inbound traffic from the internet to prefer ISP1 over ISP2. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE2 (AS Path Prepending to Make ISP2 Less Preferred) : Create a route map to prepend your AS path multiple times for CE2: route-map PREPEND_AS permit 10 set as-path prepend 65001 65001 65001 Apply this route map to the neighbor in the BGP configuration for CE2: router bgp 65001 neighbor 10.0.2.1 remote-as 65002 neighbor 10.0.2.1 ro...

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...