> ==From: Marek Brudka <mbrudka@xxxxxxxxx> .. > ==The bad thing is DHCP. It seems, that cdc_ncm driver somehow consumes DHCP > ==replies. I had to manually setup wwan0 interface as well as routing > ==using the result > ==of Hayes command > == > ==AT^DHCP? > ==^DHCP: > ==EC684764,F8FFFFFF,E9684764,E9684764,356002D4,366002D4,43200000,43200000 > ==OK Are we sure that this firmware supports DHCP? It's not uncommon for modem firmwares to lack such support, and I find this a much more likely explanation than the driver somehow messing up the DHCP replies while letting other packets through. Unfortunately there is no easy way to tell for sure if a specific feature is enabled or not in a specific firmware. Is it possible to get a snoop from Windows while connecting, using the modem in the same mode? That would tell us whether the Windows software depends on DHCP or is using the AT^DHCP command. Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
