Cool, I’ll give it a look, thanks 

Aaron

On Jun 10, 2024, at 6:24 PM, Peter Potvin <peter.potvin@accuristechnologies.ca> wrote:


That was resolved a couple years back I believe, I'm receiving Google's IPv6 DNS prefix (2001:4860::/32) from Cogent currently but it goes via 6453 before entering 15169's network.

Peter

On Mon, Jun 10, 2024 at 5:53 PM Aaron1 <aaron1@gvtc.com> wrote:
Also related to Cogent and v6… I recall having Google v6 DNS reachability issue through Cogent previously… is that still a problem?

Aaron

On Jun 10, 2024, at 4:48 PM, Peter Potvin via NANOG <nanog@nanog.org> wrote:


Cogent stopped offering anything larger than a /31 IPv4 and /127 IPv6 on new DIA circuits earlier this year, when previously they provided a /29 IPv4 and /112 IPv6 without issue at no additional cost. Now they expect you to pay additional for this functionality, including for redundant sessions. Unfortunately I have not heard of any success stories for people getting around this as of yet. YMMV

Kind regards,
Peter Potvin


On Mon, Jun 10, 2024 at 17:43 Justin Wilson (Lists) <lists@mtin.net> wrote:
I am trying to get our Cogent rep to give us a /124 to peer on a Cogent circuit with.  We have multipl routers we want to peer to a cogent transit circuit with.on.

Does anyone have the magic words or a circuit ID example you are doing multiple BGP conenctions on a single circuit?



Justin Wilson
j2sw@mtin.net


https://j2sw.com (AS399332)
https://blog.j2sw.com - Podcast and Blog