Hi all,
Been fighting with this for a while now. Trying to USB tether my iPhone 12 Pro (iOS 27 dev beta) to my Beryl AX (GL-MT3000, firmware 4.8.1, OpenWrt 21.02) and it just refuses to hand out an IP. Figured I'd write up everything I've tried so far in case someone's dealt with this or has an idea.
Setup:
-
Router: GL-MT3000 (Beryl AX), firmware 4.8.1 (OpenWrt 21.02.3, kernel 5.4)
-
Phone: iPhone 12 Pro, iOS 27 beta (was on Beta 6, updated to Beta 7 partway through troubleshooting hoping it'd fix it)
What actually works:
-
Pairing goes through fine,
idevicepair pairgives meSUCCESS, trust dialog pops on the phone, and I can confirm the trust key is sitting in/var/lib/lockdown. -
The interface comes up fine too,
eth2showsRUNNINGand grabs an IPv6 link-local address no problem. -
Same phone, same cable, plugged into my Arch Linux laptop instead and it tethers instantly, no setup needed.
-
5GHz Wi-Fi repeater mode on the Beryl AX to the same phone's hotspot works totally fine, that's what I'm using right now as a workaround.
What doesn't work:
-
udhcpc -i eth2just sits there sending discover forever and never gets an offer back. No172.20.10.xaddress, ever. -
Doesn't matter if I just paired fresh two seconds ago, same result every time.
Stuff I've tried that changed nothing:
-
Manually killing and restarting
usbmuxd. -
Wiped the
tetheringinterface config and set it back to plain DHCP (MTU 1500, TTL/HL 65), reloaded the network. -
Turning Personal Hotspot off and on while staying on that settings screen, tried both before and after replugging.
-
Unplugged and replugged the cable a bunch of times with the phone unlocked and sitting on the Hotspot screen.
-
Updated from Beta 6 to Beta 7 mid-troubleshooting hoping Apple quietly fixed it. Nope, same exact behavior.
So basically everything up to the DHCP handshake looks fine (pairing, trust, link state), but the handshake itself just never finishes on the router, even though the exact same phone/cable combo works instantly on a normal Linux kernel and over Wi-Fi.
Anyone on a GL-iNet device found a way around this?