tree b6ff62a15bd06d7caf0ac48ed541868e1c16af2c
parent d5afb2caeb6e797f0f0920eaf857a6d63f194cbe
author Ed Tanous <edtanous@google.com> 1613078915 -0800
committer Ed Tanous <ed@tanous.net> 1613178027 +0000

Bind dev server to ipv4 only

On systems that don't support ipv6, or systems that don't have an ipv6
address, binding to all ipv6 addresses can fail.  Because this is just
the dev server, it's perfectly reasonable to limit to ipv4 addresses
only.

This failure has been reported by several people over time, but it was only
recently that I root caused this as their problem.

This should have no effect on the BMC itself, as the bmc is using socket
activation, and completely bypasses this code path.

Tested:
Launched bmcweb on a system that was previously failing because of a
bind error, and observed that I could launch bmcweb and have it work
correctly.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ife6b051aa62d62e1691c5221d8ddee0b9bd012c0