There are several descriptions here for the steps taken in this thread.
"Logging in through my phone first and then cloning my phones MAC" is quite different from what I described as steps.
It is a "cat and mouse" game (Squid game?) to be detected or not. Any little thing can reveal the presence of an unwanted travel router.
They probably answer with a TTL=1 , so the packets cannot be routed further down, unless you reset also the incoming TTL number. And the TTL of the smartphone probably is 32, and for the router it is 64, so switching them is enough to blacklist that MAC address.
The GL.inet router SFT1200 cannot handle any DFS channel with 4.7.2beta or any 4.3.x version , only version 4.3.21 did connect to DFS channels.
Or even worse, as I'm in favor of the clever use of travel routers, I still do have to block them from time to time, because they ruin my wifi infrastructure, and the wifi access for them and others nearby.
If MSC is using some professional wifi controller, the GL.inet router will be identified even before you hit the first key. Devices at startup send lots of packets in a certain sequence, and it's a fingerprint. (DHCP info, NTP check, firmware upgrade check, cloud mgmt connect, MWAN3 checks, TTL used, respons to PING, respons to port 123, .... )