>
> IIRC, Comcast uses "local-as 7922" path rewriting for all enterprise EDI
> customers
> running BGP off of regional CRANs, unless I'm mistaken. So if your
> regional CRAN
> is as7015 (for New England), even if your physical circuit and BGP session
> land
> on a local SUR in your area, you have
On Wed, Sep 11, 2019 at 12:29:58PM -0400, Ross Tajvar wrote:
>
> I'm curious how this works and why it's done this way. I have a friend who
> has transit from AS7922 (the remote AS in his BGP sessions are all 7922),
Are you sure your friend has transit from as7922? It sounds like your friend is
>
> Unlike AS2914 which purely interconnects with AS7922, it seems that AS3356
> also has direct interconnections to the various Comcast subsidiary
> networks which are hidden from the DFZ through no-export communities.
I'm curious how this works and why it's done this way. I have a friend who
ha
On Tue, Sep 10, 2019 at 04:42:10PM +, Martijn Schmidt wrote:
> Hi Will,
>
> Unlike AS2914 which purely interconnects with AS7922, it seems that AS3356
> also has direct interconnections to the various Comcast subsidiary networks
> which are hidden from the DFZ through no-export communities..
server not reflecting their reality
I'm seeing odditiies when trying to traffic-engineering my way around an AS
3356-to-7922 performance issue.
I buy transit from 3356 and announce my /19 to 3356. I set traffic engineering
community 65000:7922 to supress announcement of it from 3356 to 7922.
W
I'm seeing odditiies when trying to traffic-engineering my way around an AS
3356-to-7922 performance issue.
I buy transit from 3356 and announce my /19 to 3356. I set traffic engineering
community 65000:7922 to supress announcement of it from 3356 to 7922.
When I do that, at route-server.newyork
6 matches
Mail list logo
