On 20/Apr/20 16:26, adamv0...@netconsultings.com wrote:
>
> Interesting, so it is an MTU problem after all, I take it there’s no
> way to adjust the BPF (Berkeley Packet Filter) limit to let the 6020B
> sized PSNPs through?
>
Probably could - but I'd prefer solutions that don't mess with the bas
Subject: Re: IS-IS Error (FRR)
So we've been discussing this on Slack.
It seems the packet handlers for IS-IS in FRR and how they work on FreeBSD is
not completely optimized (not an issue on Linux).
FRR-based IS-IS on FreeBSD is sending PSNP's that are 6,020 bytes large.
However, Fre
;>
>> *From:*NANOG *On Behalf Of *Mark Tinka
>> *Sent:* Friday, April 17, 2020 11:05 AM
>> *To:* nanog@nanog.org
>> *Subject:* IS-IS Error (FRR)
>>
>>
>>
>> Hi all.
>>
>> I'm almost there getting IS-IS to work without issue. I'm now
Just shooting in the dark, Isn’t the PSNP padded to some ISIS defined max MTU
and that somehow fails due to mismatch on em0 L2 MTU?
adam
From: NANOG On Behalf Of Mark Tinka
Sent: Friday, April 17, 2020 11:05 AM
To: nanog@nanog.org
Subject: IS-IS Error (FRR)
Hi all.
I'm almost
Hi all.
I'm almost there getting IS-IS to work without issue. I'm now faced with
the following error log:
2020/04/17 10:02:01 ISIS: IS-IS bpf: could not transmit packet on em0:
Input/output error
2020/04/17 10:02:01 ISIS: [EC 67108865] ISIS-Snp (1): Send L2 PSNP on
em0 failed
This repeats every
5 matches
Mail list logo