The issue is related at this moment just with prefixes that we receive from peers that are agregated, full bgp table or partial table that contain aggregated prefixes are generating this issue.
> On 30 Jun 2023, at 04:12, Tim Warnock <[email protected]> wrote: > > Is this setup only for routes you're originating from the MikroTik or is > there full tables being passed on as well? > > -----Original Message----- > From: foundry-nsp <[email protected]> On Behalf Of Bogdan > Rotariu > Sent: Friday, June 30, 2023 8:42 AM > To: [email protected] > Subject: Re: [f-nsp] Netiron AS4 capabilities > > Ok, I can totally replicate the issue using Mikrotik's CHR latest 7.11beta2. > Session between a CHR and a CER2024 closes with same error "Error: Invalid > AGGREGATOR attribute length 8”. If anyone would like to do a test I would > appreciate that. > >> On 30 Jun 2023, at 00:50, Bogdan Rotariu <[email protected]> wrote: >> >> Ty, during my research I have found out that Mikrotik forces >> atomic-aggregate attribute to any announced prefixes, I guess the >> extended-length: set comes from that? This bug they acknowledge but said it >> has nothing to do with my issue and its just Brocade fault. >> >>> On 30 Jun 2023, at 00:27, Jörg Kost <[email protected]> wrote: >>> >>> Bottom line: Vote with your wallet, buy some Extreme ;-) >>> >>> In your dump e.g. there is an empty AS-Path with length 0 and then >>> Extended-Length is set anyway. >>> I think that the spontaneously flag setting, will cause problems for other >>> vendors too. >>> >>> Path Attribute - AS_PATH: empty >>> Flags: 0x50, Transitive, Extended-Length, Well-known, Complete >>> 0... .... = Optional: Not set >>> .1.. .... = Transitive: Set >>> ..0. .... = Partial: Not set >>> ...1 .... = Extended-Length: Set >>> .... 0000 = Unused: 0x0 >>> Type Code: AS_PATH (2) >>> Length: 0 >>> >>> >>> On 29 Jun 2023, at 23:13, Bogdan Rotariu wrote: >>> >>>> Yes Netiron is a real stable software, we have plenty Brocades in use and >>>> except the ones that got many sessions and occasionally have memory >>>> issues, we never had any issues. Unfortunately I cannot convince Mikrotik >>>> that they have a bug and till now I cannot see anyone else on the forum or >>>> on their discord server that are affected by this >>>> issue and more unfortunately I got my hands on devices I cannot use :-) >>>> >> > > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
