Re: Looking for some Quagga experience to discuss 32 bit ASN + community issue with

2016-12-02 Thread Job Snijders
On Fri, Dec 02, 2016 at 09:13:25AM -0800, Eric Germann wrote: > So from reading the draft, if I’m understanding it correctly, I should > be able (with the patch) to encode the 32 bit ASN + a community in to > this as > > as32:x:y > > Is that correct? yes. I recommend you take a look at https:/

Re: Looking for some Quagga experience to discuss 32 bit ASN + community issue with

2016-12-02 Thread Eric Germann
So from reading the draft, if I’m understanding it correctly, I should be able (with the patch) to encode the 32 bit ASN + a community in to this as as32:x:y Is that correct? EKG > On Dec 2, 2016, at 2:27 AM, Job Snijders wrote: > > On Fri, Dec 02, 2016 at 09:00:57AM +, Nick Hilliard wro

Re: Looking for some Quagga experience to discuss 32 bit ASN + community issue with

2016-12-02 Thread Job Snijders
On Fri, Dec 02, 2016 at 09:00:57AM +, Nick Hilliard wrote: > Eric Germann wrote: > > Basically trying to advertise 4 byte ASN’s + communities, and then > > pick them off elsewhere in a private network. Can’t get the config > > right for the route map to import them on the “receiving” side. >

Re: Looking for some Quagga experience to discuss 32 bit ASN + community issue with

2016-12-02 Thread Nick Hilliard
Eric Germann wrote: > Basically trying to advertise 4 byte ASN’s + communities, and then > pick them off elsewhere in a private network. Can’t get the config > right for the route map to import them on the “receiving” side. yes, sounds about right. There is a massive feature deficit regarding BG