spawn one rmcpp bridge per interface
According to the new architecture, each bridge should be a separate
process, or at the very least, be attached on a separate D-Bus
connection with a well-known name that corresponds to the channel name.
This commit brings netipmid to a state where it can be launched as:
systemctl start phosphor-ipmi-net@eth0
with a parameterized unit file and socket file that binds the socket to
the interface specified. If not launched this way, it will by default be
bound to all interfaces.
This includes the new parameterized service and socket file and the
autoconf/automake magic to install them to the correct place.
Tested-by: launch netipmid via current unit file/socket file
launch netipmid via parameterize unit file/socket file
Change-Id: Ib202015fb560da269e535f11c0ac316b17f6c262
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
diff --git a/sd_event_loop.hpp b/sd_event_loop.hpp
index a626490..54b2946 100644
--- a/sd_event_loop.hpp
+++ b/sd_event_loop.hpp
@@ -7,6 +7,15 @@
#include <boost/asio/io_context.hpp>
#include <chrono>
#include <map>
+#include <sdbusplus/asio/connection.hpp>
+
+namespace ipmi
+{
+namespace rmcpp
+{
+constexpr uint16_t defaultPort = 623;
+} // namespace rmcpp
+} // namespace ipmi
namespace eventloop
{
@@ -31,6 +40,13 @@
*/
int startEventLoop();
+ /** @brief Set up the socket (if systemd has not already) and
+ * make sure that the bus name matches the specified channel
+ */
+ int setupSocket(std::shared_ptr<sdbusplus::asio::connection>& bus,
+ std::string iface,
+ uint16_t reqPort = ipmi::rmcpp::defaultPort);
+
private:
/** @brief async handler for incoming udp packets */
void handleRmcpPacket();