Rename struct fec_tlv to struct tlv since it is just the generic
TLV header which will be used in different places shortly.
Cleanup the ldp.h header file a tiny bit.

Add missing #includes instead of assuming that some system header pulls in
the needed bits

ok deraadt@, millert@

Rewrite all packet parsers to be more careful about alignment. Until
now ldpd had no chance to run on a strict alignment architecture but
this makes ldpd happy on sparc64. Be careful to do all needed

Rewrite all packet parsers to be more careful about alignment. Until
now ldpd had no chance to run on a strict alignment architecture but
this makes ldpd happy on sparc64. Be careful to do all needed overflow
checks and try to make all parsing functions look similar.
OK michele@

show more ...

Implement the optional label request message ID TLV.
Currently on the genaration side is done.

For label release and withdraw messages make sure that a wildcard
FEC is the one and only FEC of that message. This is required by
the RFC. While it is not correct to have multiple FEC in anything
bu

For label release and withdraw messages make sure that a wildcard
FEC is the one and only FEC of that message. This is required by
the RFC. While it is not correct to have multiple FEC in anything
but label mapping messages ldpd will accept those since the RFC
is extra vague about this feature and it does not hurt.

show more ...

struct mapping_entry should just have a struct map instead of own
definition of a FEC mapping. This makes extending struct map simpler
and makes it possible to access the additional data in struct ma

struct mapping_entry should just have a struct map instead of own
definition of a FEC mapping. This makes extending struct map simpler
and makes it possible to access the additional data in struct map.

show more ...

Switch prefix in struct map to a struct in_addr instead of a u_int32_t.
Needed for further clean etc.

Move the logging of FEC changes to the LDE and print the FEC and label
information. This is more useful.
OK michele

Rename some imsg bits to make namespace collisions less likely buf to
ibuf, buf_read to ibuf_read, READ_BUF_SIZE to IBUF_READ_SIZE.

ok henning gilles claudio jacekm deraadt

Implement the missing label map recv functions and cleanup the other recv
functions a bit to make them all look more similar. All but the label req
abort message are now parsed and passed to the lde.

The host address encoding of FEC was killed in RFC5036 and we're happy
about that. OK michele@

Even though label withdraw, release, and abort requests are not fully
implemented use a correct return value so that ldpd has a chance to survive
when one of those messages are received.
OK michele@

Do not use bufferevent for something that's already covered in the imsg
buffer API. This fixes a few possible problems in session_read and does
some further cleanup in various places. Wrap msgbuf int

Do not use bufferevent for something that's already covered in the imsg
buffer API. This fixes a few possible problems in session_read and does
some further cleanup in various places. Wrap msgbuf into evbuf to add
libevent functionality and use buf_read to handle the read side of a
session. OK michele@ and dlg@ did not see anything evil

show more ...

Correctly encode FEC prefixes. This makes my test setup much happyer.
OK michele

Make send_* functions return void (and not int) as they can just succeed
or fatal().

ok claudio@

Correctly parse the host address in the FEC TLV.

ok claudio@

Length of the host address in the FEC TLV must be encoded in number
of octets.

ok claudio@

Correctly send notification messages when errors occur.

ok claudio@ laurent@

Welcome ldpd, the Label Distribution Protocol daemon.
Built using the imsg/three process framework, its main aim
is to redistribute MPLS labels between peers.

Right now it has some really basic func

Welcome ldpd, the Label Distribution Protocol daemon.
Built using the imsg/three process framework, its main aim
is to redistribute MPLS labels between peers.

Right now it has some really basic functionalities,
the basic protocol works and peers are able to exchange
labels and insert them in the kernel.
It still does not react to changes of topology.

Not yet connected to the builds.

ok claudio@ deraadt@

show more ...