next: Can an NMDevice subclass tell l3cfg to not commit the IP config?
In the next branch, when NMDevice calls the subclass's
act_stage3_ip_config_start, can the subclass later notify NMDevice that IP configuration is done, i.e. as if by returning
NM_ACT_STAGE_RETURN_IP_DONE in the
main branch? This return value implied that the configuration had already been committed. Or should maybe
nm_device_devip_set_state_full() be extended with a commit type parameter or similar, to tell NMDevice not to commit the new IP configuration?
The use case for this is when IWD is configured to do the IP configuration on its own and NM should ideally just treat that interfaces IP configuration as external. I managed to produce a proof of concept for this in my tree in balrog-kun/NetworkManager@bf89825a and I was trying to adapt that for
Is this even something that NM should support? In the IWD case it's definitely useful since, for example, P2P isn't supported at all in IWD when the
NetworkConfigurationEnabled setting is false (since P2P implies DHCP, mandated directly by the P2P spec).