summaryrefslogtreecommitdiff
path: root/src/libsystemd-rtnl/test-rtnl.c
AgeCommit message (Collapse)Author
2013-12-16rtnl: replace message_append by typesafe versionsTom Gundersen
2013-12-16rtnl: support interleaved reading and writing, and rewindTom Gundersen
2013-12-16rtnl: simplify route_new()Tom Gundersen
Drop most of the arguments and instead introduce set_dst_prefixlen().
2013-12-16rtnl: simplify link_new()Tom Gundersen
Drop most of the arguments and instead introduce link_set_{flags,type}.
2013-12-16rtnl: match - only match on one type at a timeTom Gundersen
2013-12-04rtnl: add callback supportTom Gundersen
sd_rtnl_add_match allows you to add a callback function for when given types of messages are received.
2013-11-26rtnl: add preliminary support for containersTom Gundersen
For now, we only support one container type IFLA_LINKINFO, and we still lack support for parsing the containers again.
2013-11-14rtnl: add event loop integrationTom Gundersen
2013-11-14rtnl: add call_async and call_async_cancelTom Gundersen
They work in the same way as the sd-bus equivalents.
2013-11-13rtnl: start adding support for asynchronous messagingTom Gundersen
Similarly to sd-bus, add: sd_rtnl_wait sd_rtnl_process sd_rtnl_send and adapt sd_rtnl_call accordingly.
2013-11-13rtnl: rename rtnl_bus_send_with_reply_and_block() to rtnl_bus_call()Tom Gundersen
Follow the equivalent rename in sd-bus to stay as similar as possible.
2013-11-08test-rtnl: fix typoTom Gundersen
2013-11-07rtnl: headers in src/systemd/ may not include internal headersLennart Poettering
Hence including "util.h" from sd-rtnl.h is not OK. Let's minimize our headers we pull in a bit.
2013-11-04rtnl: add support for routesTom Gundersen
2013-10-29rtnl: fix sockaddr confusionTom Gundersen
2013-10-29sd-rtnl: minor fixesTom Gundersen
2013-10-27rtnl: relax the tests a bitTom Gundersen
It is a bit too optimisitc that this stuff is the same on different hosts.
2013-10-27libsystemd-rtnl: add a rtnetlink libraryTom Gundersen
This is intentionally as similar to sd-bus as possible. While it would be simple to export it, the intentions is to keep this internal (at least for the forseeable future). Currently only synchronous communication is implemented