Cogent BGP session more than 1 router ipv6
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
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
From what I recall both HE and Google over v6 are not accessible via Cogent
On Mon, Jun 10, 2024 at 17:53 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
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
We were able to get a /28 from cogent for peering on ipv4. I believe we are paying for this, but our rep is not getting the concept of it in ipv6. He says he can only order a /127 or /48. I don’t mind paying. I Justin Wilson j2sw@mtin.net — https://j2sw.com (AS399332) https://blog.j2sw.com - Podcast and Blog
On Jun 10, 2024, at 5:47 PM, Peter Potvin <peter.potvin@accuristechnologies.ca> 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 <mailto: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 <mailto:j2sw@mtin.net>
— https://j2sw.com <https://j2sw.com/> (AS399332) https://blog.j2sw.com <https://blog.j2sw.com/> - Podcast and Blog
We’ve had success with multiple VLAN tagged handoffs/BGP sessions w/ Cogent with various customers of ours in similar scenarios. Perhaps you can ask for multiple VLANs each with a /31 + /127 + BGP sessions.
On Jun 11, 2024, at 07:35, Justin Wilson (Lists) <lists@mtin.net> wrote:
We were able to get a /28 from cogent for peering on ipv4. I believe we are paying for this, but our rep is not getting the concept of it in ipv6. He says he can only order a /127 or /48. I don’t mind paying. I
Justin Wilson j2sw@mtin.net
— https://j2sw.com (AS399332) https://blog.j2sw.com - Podcast and Blog
On Jun 10, 2024, at 5:47 PM, Peter Potvin <peter.potvin@accuristechnologies.ca> 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 <mailto: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 <mailto:j2sw@mtin.net>
— https://j2sw.com <https://j2sw.com/> (AS399332) https://blog.j2sw.com <https://blog.j2sw.com/> - Podcast and Blog
That doesn't even make any sense. IPv4 is a contended resource, but IPv6 is not. They're already double-dipping by charging for the extra BGP sessions. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com ----- Original Message ----- From: "Peter Potvin via NANOG" <nanog@nanog.org> To: "Justin Wilson (Lists)" <lists@mtin.net> Cc: nanog@nanog.org Sent: Monday, June 10, 2024 4:47:37 PM Subject: Re: Cogent BGP session more than 1 router ipv6 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
On 6/12/24 05:51, Mike Hammett wrote:
That doesn't even make any sense. IPv4 is a contended resource, but IPv6 is not. They're already double-dipping by charging for the extra BGP sessions.
Perhaps, is the issue that what customers are paying for is the ability to have multiple BGP sessions against a wider address scope than standard p2p toward the same Cogent edge router, rather than just paying for the wider address scope space itself? In other words; p2p BGPv6 session = free; p2mp BGPv6 session = $$. Mark.
participants (8)
-
Aaron1 -
Andrew Hoyos -
Dovid Bender -
Justin Wilson (Lists) -
Mark Tinka -
Mike Hammett -
Mike Lyon -
Peter Potvin