What is the most effective and straightforward method for rate limiting a BGP neighbor? Little more complicated than an interface queue because there can be traffic from multiple sources, and there are overlapping subnets for multiple neighbors (but more precise /32 routes)
In addition, how about rate limiting on both an individual neighbor as well as a global basis? I.e. if we’re selling 100mbit per site, but only allowing them a maximum of 300mbit across ‘all’ sites simultaneously
@ millenium7
i am sorry don’t quite understand for the first part of your questions. can you be more specific?
for the second part,
imho, although everything is up to you as your own network operator - but I think it is better to leave your client doing their own bgp peering directly to ix. otherwise you should give a lot of thought about your network being your client transit point. it is about you and your own network capacity and capability (physically and mentally). if you think everything is good then there will be no rate limit question.
just a thought 
Let me try and clarify with a simple example using 1 company and 2 different sites (they get to the internet through my network)
My network leases transit and an IP space of 1.0.0.0/24 to CompanyX
CompanyX pays me for 150/150mbit of bandwidth to the internet
CompanyX has 2 sites that connect to my network, and I also sell them capacity into my network at 100/100mbit for each site
CompanyX is entirely in control of how they assign 1.0.0.0/24 in their own network across both sites, they are not contiguous IP blocks at each site. They advertise the individual /32 customer routes to me via BGP, hence .1 and .3 may be at SiteA but .2 is at SiteB
So I can’t just create a simple 1.0.0.0/24 rate limit, with 1.0.0.0/25 and 1.0.0.128/25 underneath it for each site respectively
I need to
My network leases transit and an IP space of 1.0.0.0/24 to CompanyX
CompanyX pays me for 150/150mbit of bandwidth to the internet
CompanyX has 2 sites that connect to my network, and I also sell them capacity into my network at 100/100mbit for each site
aaa… ok.
you have played both l2 and last mile roles.
need to
- Rate limit to a total of 150/150mbit’s for the entirety of 1.0.0.0/24 (and whatever other routes they advertise to me)
- Rate limit SiteA to 100/100mbit
- Rate limit SiteB to 100/100mbit
for number 2 and 3 is obvious. you can have it as basic interface limit.
for number 1, yes - it is a bit complicated. you need to know how many routes they sent you on both sites.
which triggers address list. then from there triggers rate limit. which then in effect - not so smooth user experience on either sites?
hmm… interesting