| Age | Commit message (Collapse) | Author |
|---|
|
The code generating LSAs for PTP OSPF links is buggy. The old behavior
is that it generates PTP link if there is a full/ptp neighbor and stub
link if there isn't. According to RFC 2328, the correct behavior is to
generate stub link in both cases (in the first case together with PTP
link).
And because of buggy detection of unnumbered networks, for numbered
networks the code creates stub links with 0.0.0.0/32.
|
|
|
|
|
|
|
|
|
|
very large packets (if configured).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
metric = 1. Now it's metric of most distant component.
|
|
|
|
|
|
|
|
|
|
|
|
Bugfix of some debugging commands.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
are in single database. This avoids duplication of external LSAs and
fixes bug in external LSA distribution.
|
|
Origination of summary LSA works.
Routing table calculation works.
Virtual links works.
Well, I hope, OSPF is fully compatible with RFC2328!!!!
|
|
This makes the adjacency forming faster.
Minor code clean up.
|
|
This helps to faster establish the adjacency.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
interfaces.
|
|
Bugfix - E bit was not unset on stub areas.
|
|
|
