> If this is true, then falling back to DHCP would seem to be required
> for many Qualcomm based devices. This seems to be a recently
> introduced 'bug' as older QMI devices did not need this workaround.
Do you think we should try to figure out which Qualcomm device is
misbehaving or should the feature just be reverted?
It would seem that this only affects devices introduced in the last
several years. The QMI code is from 2012, and the devices Marcel tested
this with worked fine.
Perhaps we should have plugins/udevng.c maintain a database of all the
'dhcp-required' devices and set this property accordingly. Running DHCP
takes time, so if it can be avoided, you get online a bit faster...
The other option is to add some fallback mechanism in ConnMan and print
a fat warning into the log. But I don't this idea.
Sounds like a least preferred option to me as well.