very slow processing of MMS received via Ting (T-Mobile)
11-03-2022, 04:55 PM
Well, the software updates had nothing to do with it, and the carrier is very relevant.
At some point in the last several weeks, Ting (a T-Mobile MVNO) or T-Mobile seems to have dropped IPv4 support. I no longer get a v4 address, nor a v4 route to their network. While processing a MMS, mmsd-tng would usually get an address like 10.168.127.17 from DNS and that would time-out since it's not accessible via public internet. Once in a while DNS would return a v6 address and that's when the message would finally get processed and delivered.
The solution is to set ForceCAres=true in ~/.mms/modemmanager/mms. That tells mmsd-tng to always do DNS via the WWAN interface so I'l always get a v6 address.
At some point in the last several weeks, Ting (a T-Mobile MVNO) or T-Mobile seems to have dropped IPv4 support. I no longer get a v4 address, nor a v4 route to their network. While processing a MMS, mmsd-tng would usually get an address like 10.168.127.17 from DNS and that would time-out since it's not accessible via public internet. Once in a while DNS would return a v6 address and that's when the message would finally get processed and delivered.
The solution is to set ForceCAres=true in ~/.mms/modemmanager/mms. That tells mmsd-tng to always do DNS via the WWAN interface so I'l always get a v6 address.
