What are people doing to avoid the following? We mark customer routes with communities, set a higher local preference and weight.
IP transit customer peers with us on pe3 and pe4, we add bgp community (eg xxx:1000) and set local preference to 200. Customer advertises /22.
Provide edge routers pe1 and pe2 are also offered customer prefixes at a public internet exchange but our higher local preference wins out so:
- We only advertise prefixes to our upstreams when they contain community xxx:1000. This would withdraw their prefixes and subsequently their IP transit, should we not learn their prefix via the direct peering session.
- Local preference is higher for prefix received via direct peering link, so we can restrict customer to subscribed speed.
Customer now however additionally advertises /24 subnets via internet exchange but filters them from our direct peering session. Whilst his /24 subnets aren't advertised upstream to our providers, our infrastructure routes according to longest prefix match so we send customer traffic back via internet exchange where we don't have restrictions.
We're currently having to add prefix filters, to each router at public IXs, to discard routes containing customer's ASNs. This is very laborious, anyone have clever suggestions?