The WFLY-184 fix rejects the combination of any-ipv6-address and java.net.preferIPv4Stack=true in Stage.RUNTIME, but does so during service installation rather than in service start. The effect of this is failures occur even if the interface resource isn't being used; e.g. on a host controller.

This also leads to inconsistent behavior between "add" and "write-attribute", as the write-attribute handler doesn't install the service, and thus doesn't fail. It just sets reload-required.

Fix is to move the check into NetworkInterfaceService.start() and to make those services ON_DEMAND so the check won't occur until the interface is actually needed.