* BNetworkSettings now set unspecified addresses to their empty family
specific addresses, instead of using AF_UNSPEC.
* This allows the net_server to set those addresses on the address
specific stack interface.
* Until now, only AF_UNSPEC addresses could be empty.
* Now, the unspecified IPV4/IPv6 address is considered empty, too.
* This corresponds to how the kernel modules handles this.
* _AddParameter() would ignore all BMessage::Add*() errors.
* _ConvertFromDriverParameter() would ignore most intermediate error,
but would fail badly over some incorrect settings file.
* Also, it checked for the parent value for each parameter, which
doesn't make any sense, but would add as often as there are
parameters -- which also may be none, in which case the value
got ignored.
* DNS add-on does not yet support it, the rest does.
* However, there seems to be some problems with the net_server when
changing interfaces -- not just with revert.
* And call it from the DNS client -- this is the only add-on that does
not trigger a configuration or settings update, so we have to notify
the changes manually.
* Otherwise there is nothing to it.
* Removed comment and commented out invalidation. Seems to work
just fine without it, and I cannot think of a reason why it should
be there.
* When you press the enable/disable button, it now stays disabled
for half a second before it is updated, and reenabled again.
* This is done so that the net_server has time to update its internal
state, so that it should look correct right from the start, even if
the server does not immediately react to the changes.
* Now uses the BNetworkServiceSettings::IsRunning() method.
* Added IsRevertable(), and Revert(), methods.
* Get{Interface|Network|Service}() methods are now const.
* Added variants of Interface(), and Service() that are const.
* Added new BNetworkServiceSettings::IsRunning() convenience method that
reflects the status quo rather than the settings.
* GetMessage() now checks if the only existing address is the default
wildcard address, and then omits it in the message (as it will be
created by default, anyway).
* If it does not exist yet, the sshd user is created upon enabling
the service.
* Also, it now uses kMsgIsServiceRunning to determine the current
label/function of the enable/disable button.
