On Wed, May 06, 2020 at 03:23:06PM +0100, Richard Chivers wrote:
> Hi,
>
> Thanks so much for the diff, it appears to have resolved the issue.
>
> We are now trying to establish whether we need the fix widely deployed or
> only on the box that originates with the large LSA updates, pushing it
Hi,
Thanks so much for the diff, it appears to have resolved the issue.
We are now trying to establish whether we need the fix widely deployed or
only on the box that originates with the large LSA updates, pushing it over
the 1500mtu.
We are going to run some tests, but our expectation is that
On Wed, May 06, 2020 at 09:33:11AM +0100, Richard Chivers wrote:
> Hi,
>
> Some progress has been made, we can now replicate this consistently and it
> appears that whenever a LS update exceeds the mtu (1500) we get this issue
> of lsa_check bad age.
>
> When running with the diff Claudio sent
Hi,
Some progress has been made, we can now replicate this consistently and it
appears that whenever a LS update exceeds the mtu (1500) we get this issue
of lsa_check bad age.
When running with the diff Claudio sent we start getting a bunch of errors
complaining about:
recv_ls_update: bad
Hi,
We have sent the pcap directly for the raw packets.
In terms of the above change, we haven't compiled ospf previously, we will
give it a go and see how we get on.
Are we ok to clone off the github mirror?
Cheers
Richard
On Tue, May 5, 2020 at 10:22 AM Claudio Jeker
wrote:
> On Tue, May
On Tue, May 05, 2020 at 10:51:40AM +0200, Claudio Jeker wrote:
> On Tue, May 05, 2020 at 09:07:34AM +0100, Richard Chivers wrote:
> > After some more work this morning we have managed to extract the
> > information from tcpdump of the full LS-Update packet, we couldn't see it
> > on bsd, but
On Tue, May 05, 2020 at 09:07:34AM +0100, Richard Chivers wrote:
> After some more work this morning we have managed to extract the
> information from tcpdump of the full LS-Update packet, we couldn't see it
> on bsd, but running:
>
> tcpdump -v -r ~/Downloads/ospf.pcap on osx did the trick.
>
>
On Tue, May 05, 2020 at 09:07:34AM +0100, Richard Chivers wrote:
> Another 5 or so seconds later the same LS-Update comes in with the same seq
> number. This appears to continue indefinitely. Our only fix appears to be
> restarting ospfd on the routers.
>
> Does anyone have an idea what is going
After some more work this morning we have managed to extract the
information from tcpdump of the full LS-Update packet, we couldn't see it
on bsd, but running:
tcpdump -v -r ~/Downloads/ospf.pcap on osx did the trick.
What we are seeing is that a pair of firewalls are both sending updates
like
Hi,
Following on from the OSPF issue we were seeing in 5.8, we have built a
vagrant lab with a complete replica of our production network in order to
test config against 6.6 (latest syspatch applied) and test a number of
scenarios.
All in all everything has gone well, and other than some minor
10 matches
Mail list logo
