| Age | Commit message (Collapse) | Author |
|---|
|
Save a pointer to the right LSA tree in new member v->lsa_tree.
This saves us the hassle of finding the right tree in vertex_free(),
we already know it at creation time so why not tuck it in there?
This might cause problems if the ospfe side ever decides to call
area_del() with a non-empty area->lsa_tree, without correctly
initialising v->lsa_tree. But grep shows that the area's lsa_tree
is currently just initialized on the ospfe side, but never modified.
ospf6d daemons which crashed after about 1 min with malloc options
FGJ are now happy.
ok claudio@
|
|
printing IFINFO while we are actually handling an IFDELETE imsg.
|
|
length, regardless of interface type.
Allowed by RFC5340 and ok claudio@
|
|
global-scope prefixes in iface->ifa_list.
ok claudio@
|
|
|
|
jmc@ has provided a complete list of manual pages to be fixed,
and suggested using uppercase (i.e., Point-to-Point) when discussing
the protocol, and lowercase (point-to-point) otherwise.
ok jmc@
|
|
LSAs which refer to Router LSAs.
ok claudio@
|
|
Routers can now advertise prefixes with global scope throughout
an area. This paves the way towards doing SPF calculations to
generate routing tables for a single area.
ok claudio@
|
|
But in Intra-Area-Prefix LSAs, #prefixes is a 16bit value.
lsa_intra_a_pref_check() was failing on little-endian machines because
it was trying to byte-swap a 32bit value.
ok claudio@
|
|
number of bytes left in the buffer. OK stsp@
|
|
LSAs to zero. We were using the interface index, which is not quite right
for this type of LSA.
This is part of a greater scheme:
Intra-Area-Prefix LSAs referencing Router LSAs (not yet implemented)
will initially have their Link State ID hard-coded to one.
Then, as soon as we implement fragmentation of Intra-Area-Prefix LSAs,
Link State IDs for both types of Intra-Area-Prefix LSA will have to be
generated dynamically in a non-overlapping fashion.
discussed with claudio@
|
|
Print not just the area, but also the interface to the link the LSA
is generated for.
ok claudio@
|
|
of IPv6 prefixes with a Network LSA (there's another type of this LSA which
associates prefixes with a Router LSA -- this remains to be done).
Add what is necessary to allow ospf6ctl to read the new LSA type via IMSG.
ok claudio@
|
|
to the RDE.
ok claudio@
|
|
ok stsp@
|
|
|
|
if present, and that a router ID must be manually configured on
IPv6-only routers.
|
|
regardless of link type. So don't ever use source addresses from the IP
header to match known neighbours when receiving hello packets.
ok claudio@
|
|
First convert IP addresses to host-byte-order before checking which one is
smaller. Additionally fix the check to find the lowest configured IP as
suggested by the RFC.
ok claudio@
|
|
Make it smarter so that ospf6d knows the actual prefix length
configured on an interface.
ok claudio@
|
|
we had better include LSAs from iface->lsa_tree when sending
DB summaries. Fixes initial flood of link LSAs.
ok claudio@
|
|
Make it handle other types of links, too.
ok claudio@
|
|
OK claudio@
|
|
of the Link LSA is still not solved though.
|
|
attached to the LSA (saves 8 to 12 bytes per prefix and makes our life
more interesting or complex).
|
|
store the prefix to because the onwire format has the prefix compressed and
so struct lsa_prefix will no longer carry the prefix in it. Use rt_prefix
instead which is the expanded and host-byte-order version of the former.
|
|
the or-ed result of all active neighbors. freaky...
Discussed with stsp@
|
|
LSA is lost in lsa_flood. Put this in because it goes in the right direction
and ospf6d is work in progress. Add necessary framework so that we can print
Link LSA in ospf6ctl.
Diff mostly from stsp@ ospf6ctl part by myself
|
|
existing (but undocumented) flag from the usage of ospf6d;
documentation tweaks; while here, synchronize synopsis and usage.
ok claudio@
|
|
changes by myself.
|
|
killed. From Stefan Sperling
|
|
the callers should take care of getting the byte order right. While there
remove the opts[123] from the hello_hdr and use LSA_24_* to handle this
nasty fields instead. Now router LSA have the correct flags set.
|
|
work for IF_TYPE_BROADCAST networks.
Initial diff by Stefan Sperling, some additional work by myself
|
|
From Stefan Sperling
|
|
some macros to handle the 24bit insaneness.
rfc5340 syncup by Stefan Sperling, the insanity is mine
|
|
struct nbr to identify the neighbors correclty.
From Stefan Sperling stsp (at) stsp.name
|
|
possible database desciption files to the RDE. NBR_EVT_NEG_DONE sends an
imsg to the RDE to bring the RDE in the correct state for the database
exchange when doing this the wrong way the RDE will issue errors.
From ospfd (rev. 1.23 of database.c) via Stefan Sperling
|
|
|
|
Use unsigned int for msg_iovlen.
ok henning@ claudio@
|
|
|
|
|
|
option parsing. Found out the hard way by jdixon on ifstated.
ok sobrado@, jdixon@, millert@
|
|
|
|
each cmsg_len (ie. msg_controllen = sum of CMSG_ALIGN(cmsg_len). This
works now that kernel fd passing has been fixed to accept a bit of
sloppiness because of this ABI repair.
lots of discussion with kettenis
|
|
descriptors; ok hshoexer, also looked at by kettenis and henning
|
|
an extensive discussion with otto, kettenis, millert, and hshoexer
|
|
but only do the final popfile call after yyparse() is done.
This also fixes config reload on SIGHUP for some daemons.
Spotted by otto@. OK deraadt@
|
|
|
|
not a hard and fast rule (actually it's a form i abuse) but
hostname.if.5 currently uses two conflicting forms and this keeps
it consistent;
|
|
found by Igor Zinovik <zinovik@cs.karelia.ru>
|
