v0.13.4
-
Changed
- VintageNet configurations are normalized on load now rather than on use.
For various reasons, it's useful to support multiple ways of specifying
network configurations, but internally VintageNet always converts to one way
to simplify use. If you callVintageNet.get_configuration/1
or
VintageNet.get/2
to look at the config, you'd see the original form and not
the normalized one. Now you get the normalized one. - Add
:reason
to theVintageNet.Technology.Null
. VintageNet usesNull
to
make network interfaces stay unconfigured when requested or when there's an
error. The:reason
key helps you know why rather than forcing you to dig
through logs.
- VintageNet configurations are normalized on load now rather than on use.
-
Fixes
- When reseting a network configuration to defaults, a settings file was
written and immediately erased. That doesn't happen any more.
- When reseting a network configuration to defaults, a settings file was