v0.7.5

• Bug fixes
  • Fix routing table error when configuring multiple interfaces of the same
    type.
  • Fix VintageNet.info for when it's called before vintage_net is loaded.

v0.7.4

• Bug fixes
  • Fix VintageNet.info crash when displaying AP mode configurations
  • Save configurations using the :sync flag to reduce the chance that they're
    lost on ungraceful power offs. I.e., people pulling the power cable after
    device configuration.

v0.7.3

• Improvements
  • Scrub VintageNet.info/0 output to avoid accidental disclosure of WiFi
    credentials
  • Support options to deconfigure/2 to mirror those on configure/2
  • Prefix udhcpc logs with interface to more easily blame problematic
    networks
  • Support IPv4 /32 subnets
  • Various documentation fixes and improvements

v0.7.2

• Bug fix
  • Remove noisy log message introduced in v0.7.1

v0.7.1

This release fixes an issue where the Internet-connectivity checking code could
crash. It was automatically restarted, but that had a side effect of delaying a
report that the device was connected AND breaking mdns_lite. Both the crash
and the restart issue were fixed. The mdns_lite side effect was due to its
multicast group membership being lost so this would affect other multicast-using
code.

• Bug fixes

  • Fix :timeout_value crash in the InternetConnectivityChecker
  • Force clear IPv4 addresses when the DHCP notifies a deconfig event. This
    occurs on a restart and is quickly followed by a renew. However, if
    applications don't see this bounce and don't reregister their multicast
    listeners on affected IPv4 address, they'll lose the subscription.

• Improvements

  • Added check for nerves_network and nerves_init_gadget. If your project
    pulls these in, it will get a moderately friendly notice to remove them.

v0.7.0

This release moves network technology implementations (WiFi, wired Ethernet,
etc.) into their own projects. This means that they can evolve at their own
pace. It also means that we're finally ready to support the
VintageNet.Technology behaviour as part of the public API so that VintageNet
users can add support for network technologies that we haven't gotten to yet.

IMPORTANT: This change is not backwards compatible. You will need to update
existing projects to bring in a new dependency. The runtime is backwards
compatible. I.e., If you have a networking configuration saved in VintageNet, it
will be updated on load. It won't be re-saved, so if you need to revert an
update, it will still work. The next save, though, will use the new naming.

If you're using VintageNet.Technology.Gadget, do the following:

1. Add {:vintage_net_direct, "~> 0.7.0"} to your mix.exs dependencies.
   You'll notice that references to "gadget" have been replaced with the word
   "direct". We think the new naming is more accurate.
2. Replace all references to VintageNet.Technology.Gadget in your code to
   VintageNetDirect. Be aware of aliases and configuration.
3. If you passed options when configurating the network, the :gadget key is
   now :vintage_net_direct. Most users don't pass options.

If you're using VintageNet.Technology.Ethernet, do the following:

1. Add {:vintage_net_ethernet, "~> 0.7.0"} to your mix.exs dependencies.
2. Replace all references to VintageNet.Technology.Ethernet in your code to
   VintageNetEthernet. Be aware of aliases and configuration.

If you're using VintageNet.Technology.WiFi, do the following:

1. Add {:vintage_net_wifi, "~> 0.7.0"} to your mix.exs dependencies.
2. Replace all references to VintageNet.Technology.WiFi in your code to
   VintageNetWiFi. Be aware of aliases and configuration. Also, the "F" is
   capital.
3. The :wifi key in the network configuration is now :vintage_net_wifi.

v0.6.6

• Bug fixes

  • Fix warning from Dialyzer when making wild card subscriptions. Code was also
    added to more thoroughly validate properties paths to raise on subtle issues
    that won't do what the programmer intends.

• New features

  • Added VintageNet.match/1 to support "gets" on properties using wildcards.

v0.6.5

• New features
  • Support wild card subscriptions to properties. This makes it possible to
    subscribe to things like ["interface", :_, "addresses"] where the :_
    indicates that any value in the second position should match. That
    particular subscription would send a message whenever an IP address anywhere
    gets added, changed, or removed.

v0.6.4

• Improvements
  • Added the ["interface", ifname, "eap_status"] property for EAP
    events. EAP is currently only supported on WiFi, but is anticipated for
    wired Ethernet too.

v0.6.3

This release renames the WiFi mode names. The old names still work so it's a
backwards compatible update. The new names are :ap and :infrastructure
instead of :host and :client. These names match the mode names in the IEEE
specifications and usage elsewhere.

• New features
  • Support static IPv4 configurations for a default gateway and list of name
    resolvers. See :gateway and :name_servers parameters.
  • Support ad-hoc WiFi networking (IBSS mode)