Denis Kenzior
2018-09-24 21:17:41 UTC
Hi Giacinto,
command in this case after a timeout. However, this seems to also be
completely against the MBIM specification. If the device signals that
no IP configuration details are available, then DHCP is implied.
However, most MBIM devices do not support DHCP anyway. So this is bizarre.
The fact that you get IP details after a minute also implies that this
has nothing to do with the network wanting DHCP done by the host (like
you posit in your other email on the subject).
Regards,
-Denis
Dear all,
I have stepped into a very slow networks, that takes almost 1 minute to
assign an IP address once the MBIM CONNECT DONE is returned.
Under these conditions, the call to IP_CONFIGURATION returns all empty
values, and the driver sets the connection method to 'dhcp'.
But this modem does not support DHCP, so is there a way out of this?
Can the driver set the method to kind of 'waiting', and query
periodically, let's say every 500ms or every second?
You can try and have mbim_ip_configuration_cb retry the IP_CONFIGURATIONI have stepped into a very slow networks, that takes almost 1 minute to
assign an IP address once the MBIM CONNECT DONE is returned.
Under these conditions, the call to IP_CONFIGURATION returns all empty
values, and the driver sets the connection method to 'dhcp'.
But this modem does not support DHCP, so is there a way out of this?
Can the driver set the method to kind of 'waiting', and query
periodically, let's say every 500ms or every second?
command in this case after a timeout. However, this seems to also be
completely against the MBIM specification. If the device signals that
no IP configuration details are available, then DHCP is implied.
However, most MBIM devices do not support DHCP anyway. So this is bizarre.
The fact that you get IP details after a minute also implies that this
has nothing to do with the network wanting DHCP done by the host (like
you posit in your other email on the subject).
Regards,
-Denis