Je suis d'accord avec MarseilleMee. En France the regulatory pressure is strong. But attention: the cheap French v6 is often from operators who peer at France-IX and SFINX only. If you need global v6 tables, verify their upstreams. Some have only v6 default plus France-IX routes. Pas bon for full tables.
Member
Istanbul to Europe v6 is growing fast. Turk Telekom and Vodafone TR both pushing v6 to meet EU connectivity requirements for data residency. If you have Turkish traffic at all, consider a split: European v4 heavy, Turkish v6 heavy. Improves both ratios.
Fine. Look at the German incumbent's wholesale division and their 2023 v6 capacity build. Not naming the ASN but it's in the RIPE database with 40+ v6 /32s and a 2021 date on their first RPKI ROA. Their ratio against DTAG is public knowledge if you know where to look. That's all I'm saying.
This.
PfSense has RPKI support in FRR package now. Go to Services > FRR > BGP > RPKI tab. You need a validator, routinator is easiest. I run mine on the same Pentium III that handles my NAS because routinator uses 200MB RAM. Download, enable, point FRR at localhost:3323. Weekend project as GeorgeNmp said.
Member
I terraform FRR configs across six POPs. The community documentation is indeed better than Bird2. But Bird2's v6 route filtering syntax is cleaner. Trade-offs.
For wendy's problem: have you considered just... announcing more v6 prefixes? If you have PI space, split your /48 into more specific /52s or /56s. Some upstreams count prefix count in ratio calculations, not just bandwidth. Check your contract.
Member OP
You beautiful monster. I checked. The draft rate card says "IPv6 traffic volume" not "IPv6 prefix count." But my current contract says "IPv6-enabled prefixes" in the ratio clause. This might be the lever. I have a /44. If I announce more specifics from the same /44, does that count? Need to verify with my upstream.
Same /44 more specifics won't help if they're filtering on RIR allocation boundaries. Most do. The count is usually unique allocated blocks, not more specifics. Nice try though.
This thread went from transit pricing to prefix games to RPKI setup. Classic networking forum. I'm just here to say if anyone needs mail deliverability help on v6, the big three gmail/outlook/yahoo all accept v6 SMTP now but your PTR and RPKI need to be clean. More v6 transit means more v6 mail reputation to manage.
Following.
