very slow processing of MMS received via Ting (T-Mobile)

[treebeard]

The timing may be coincidental, but after upgrading bookworm today I find that every MMS I receive takes several (2-20) minutes to process.  A common factor is that I'm seeing "GSocketClient: Address enumeration completed (out of addresses)" in the log from mmsd-tng.  Each time this happens, there is a 1 minute timeout and it happens multiple times for every MMS.

Is anyone else seeing this after a very recent upgrade?

mmsd-tng did get upgraded from 1.11-1 to 1.12-1 but I've tried reverting to the old version with no effect.  My carrier is Ting (T-Mobile) but don't know if that's relevant.

[treebeard]

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.

[traut]

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.

On the modem, did you upgrade the Quectel firmware beyond 01.003? Newer versions make T-Mobile IPv6-only.

[treebeard]

On the modem, did you upgrade the Quectel firmware beyond 01.003? Newer versions make T-Mobile IPv6-only.

That's interesting news - I did switch to 03.006 sometime before that and may not have tested MMS.  Where did you hear this and do you know why it happened?

[traut]

That's interesting news - I did switch to 03.006 sometime before that and may not have tested MMS.  Where did you hear this and do you know why it happened?

Looked through the release notes for instances of "TMO".

[treebeard]

That's interesting news - I did switch to 30.006 sometime before that and may not have tested MMS.  Where did you hear this and do you know why it happened?

Looked through the release notes for instances of "TMO".

Sure enough, it was changed in v30.003.  I don't see any indication of it being done for any other carrier.  Weird!p, li { white-space: pre-wrap; }

[traut]

Sure enough, it was changed in v30.003.  I don't see any indication of it being done for any other carrier.  Weird!

My shallow understanding of it is that T-Mobile made a big push to go IPv6 because IPv4 space cost money, and if they can get you to be IPv6-only, they’ll translate everything from the IPv4 outside world, and have their DNS servers give you IPv6 addresses for everything. With the side-effect of forcing users to use those DNS servers.