You always want to prefer customer routes over non customer routes as a service provider. Of course having a robust set of communities to let adjustments happen helps. 

Without proper tiering of routes you may see unstable routing. 

Having a standard set of customer, peer, transit set of local preferences would go a long way. Same for geographic scope of routes, only use these on same continent. Makes using a provider if you do something like anycast hard if they haul you long distance.  

- Jared 

Sent via RFC1925 compliant device

On Jul 25, 2022, at 6:49 AM, Forrest Christian (List Account) <lists@packetflux.com> wrote:


I wish they'd add one more that turns off their "prefer routes learned from a customer" rule.   I'm having to split my blocks in half and announce them that way to get them to send my traffic directly to me through our IX peering session as opposed to one of my transit providers.

I'd rather they just let shortest path selection work. 

On Sun, Jul 24, 2022, 1:43 PM Siyuan Miao <aveline@misaka.io> wrote:
They do have BGP communities ... but for black-hole only :-(

On Sun, Jul 24, 2022 at 9:39 PM Ryan Hamel <administrator@rkhtech.org> wrote:
Yes.

Ryan

-----Original Message-----
From: NANOG <nanog-bounces+ryan=rkhtech.org@nanog.org> On Behalf Of Rubens Kuhl
Sent: Sunday, July 24, 2022 12:36 PM
To: Nanog <nanog@nanog.org>
Subject: HE.net and BGP Communities

The last mention I found on NANOG about HE.net and BGP communities for traffic engineering is from April 2021 and said they provided none.

Is that still the case a year later ?


Rubens