# Using BGP NO\_EXPORT Community to Filter Transit Routes

DevFeed: [Using BGP NO\_EXPORT Community to Filter Transit Routes](<https://devfeed.tech/articles/using-bgp-no-export-community-to-filter-transit-routes-11078.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/10/bgp-labs-no-export/>)

Published: 2024-10-14T05:25:00Z

Content type: tutorial

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [autonomous](<https://devfeed.tech/tags/autonomous.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [community](<https://devfeed.tech/tags/community.md>), [filter](<https://devfeed.tech/tags/filter.md>), [github](<https://devfeed.tech/tags/github.md>), [netlab](<https://devfeed.tech/tags/netlab.md>)

## AI overview

This tutorial explains how to use the BGP NO_EXPORT community to filter transit routes and help prevent an autonomous system from leaking them. It also describes starting the lab with GitHub Codespaces or local infrastructure and running netlab up.

## Source excerpt

In previous BGP policy lab exercises, we covered several mechanisms you can use to ensure your autonomous system is not leaking transit routes (because bad things happen when you do, particularly when your upstream ISP is clueless). As you probably know by now, there's always more than one way to get something done with BGP. Today, we'll explore how you can use the NO_EXPORT community to filter transit routes. Click here to start the lab in your browser using GitHub Codespaces (or set up your own lab infrastructure). After starting the lab environment, change the directory to policy/d-no-export and execute netlab up.