nanog mailing list archives
Re: "Peering Router"
From: Mark Tinka via NANOG <nanog () lists nanog org>
Date: Tue, 12 May 2026 07:49:40 +0200
On 08/05/2026 22:12, Seth Mattinen via NANOG wrote:
I personally don't mix transit and peering duties on the same device. I have a dedicated router for peering sessions and a dedicated router for each transit provider. I find it easier to manage and it limits scope if one of them has a problem or needs an update since it only affects its own playground.
This.A dedicated peering router also ensures you eliminate providing transit to a peer if you make a configuration error, as the peering router neither carries the DFZ nor 0/0, ::/0.
Mark. _______________________________________________NANOG mailing list https://lists.nanog.org/archives/list/nanog () lists nanog org/message/XKAEPSAWJDU67EDCJJLQLINP4ISWRWSM/
Current thread:
- Re: "Peering Router" Mike Hammett via NANOG (May 04)
- Re: "Peering Router" Mike Hammett via NANOG (May 04)
- Re: "Peering Router" Chris Woodfield via NANOG (May 04)
- <Possible follow-ups>
- Re: "Peering Router" Phil Bedard via NANOG (May 04)
- Re: "Peering Router" Seth Mattinen via NANOG (May 08)
- Re: "Peering Router" Mark Tinka via NANOG (May 11)
- Re: "Peering Router" Bryan Holloway via NANOG (May 12)
- Re: "Peering Router" Brandon Butterworth via NANOG (May 12)
- Re: "Peering Router" Mark Tinka via NANOG (May 11)
- Re: "Peering Router" Mike Hammett via NANOG (May 04)
