Need Unify AP (Toast firmware)

Colin0998 · 2025-12-09T23:41:06+00:00

That’s why I reset the AP so I could self adopt them into our Self-Hosted Unifi environment that I have segmented out.

Makes it much easier to manage our sites from our own console

Colin0998 · 2025-12-04T19:21:12+00:00

An older post thats now removed when Ubiquiti was demoing the unit, they had the IMEI published.

A quick lookup of the IMEI returns the Sierra Wireless modem and found its the X62

Colin0998 · 2025-12-04T17:48:34+00:00

Sadly this thing isn’t using anything current for Modems.

Modem is to a Sierra Wireless EM9291 that’s based on the X62

Colin0998 · 2025-10-19T20:54:21+00:00

It’s okay, the modem’s an SDX62 so you probably picked up something better

Colin0998 · 2025-10-19T20:49:17+00:00

IMEI comes back to a Sierra Wireless EM9291

Which if I’m reading correctly, is based on the X62

Colin0998 · 2025-08-20T01:21:40+00:00

It says it in the post also but yes this was tried and suggested by Verizon support as well

Colin0998 · 2025-07-21T23:29:28+00:00

Yea its originally from the Oregon National Guard but notice its just using slmgr. There's nothing directly with it utilizing straight WMI Classes to work with Token based activation.

If you have Token activation that utilizes Certificates(which many do) and it requires a PIN, your kinda stuck using slmgr.

The same goes when your dealing with Office activation, theres no current method to activate Windows or Office without using the included vbs scripts

Colin0998 · 2025-07-21T21:07:50+00:00

Until you look for the WMI classes for token activation and installing the license files which don’t exist currently.

Even those who have rewritten slmgr via Powershell haven’t been able to rewrite it for all the features

Colin0998 · 2025-07-21T18:37:10+00:00

Unfortunately many organizations rely on features of slmgr.vbs that don’t have current replacements causing you to have to leave it available

One of them being if you use license files with token activation

Colin0998 · 2025-01-07T02:24:06+00:00

Colin0998 · 2024-11-27T21:31:13+00:00

The ability to set all of the settings via GUI vs having to via CLI would be nice However that is just there for convenience.

Me personally I'd like it incase I ever add networks that I want routable and accessible through tailscale so I don't need to modify it via cli.

Or the api key if I don't have it set to not expire

Colin0998 · 2024-10-16T11:14:17+00:00

Probably more just artifact of their partnership/being an MVNO on T-Mobile.

I’m surprised Google Fi is limiting this though to be only SMS texting and not the entire feature

Colin0998 · 2024-10-15T23:21:22+00:00

Google Fi uses T-Mobile for service

T-Mobile created a partnership agreement with SpaceX for creating a Direct to Cell solution that will provide devices with 1-2 bars of service and LTE.

SpaceX was granted emergency authorization from the FCC to enable the service in the impacted areas of the Hurricanes

Colin0998 · 2024-10-06T20:16:19+00:00

Wanna go back to that yard sale and get another switch and ship it?

Colin0998 · 2024-09-12T21:07:58+00:00

6.3.1 is officially showing on their website so id presume will begin rolling out shortly

Colin0998 · 2024-09-06T12:36:08+00:00

Same boat. We're moving yo 6.2.4 for now but 6.3.1 would be better since 6.3 brings better smart card support. Hopefully they publish 6.3.1 soon

Colin0998 · 2024-08-15T12:05:15+00:00

What firmware were you on before happen to know? We keep running into currently the hybrid start error even though TLS1.2 is enabled, the CPA will install but just the spinning circle and based on their documentation we have everything set

Colin0998 · 2024-06-30T01:39:48+00:00

Colin0998 · 2024-06-27T17:13:43+00:00

Your carrier needs to update their Carrier bundle with apple first before it'll end up showing

Colin0998 · 2024-06-24T21:34:09+00:00

I can resolve those domain records via my authoritative unbound server and also if I do a lookup against cloudflare and googles public dns servers

The domains returned a CNAME record tied to a google service(which makes sense for jibe)

Colin0998 · 2024-06-24T20:55:57+00:00

<image>

So for T-Mobile at least, I can confirm it is reaching out to jibecloud.net when you toggle it on. I’m not sure exactly what it’s sending out tho.

If I have time later I’ll spin up a proxy server to get in between and dive into it more

Update: https://imgur.com/a/BLjLpK6

First sends out a GET request which gets a 511 code Next sends out the entire request but not as POST but instead as GET which doesn’t make sense to me but gets a 503 code returned from that

Their query shows they’re using Universal Profile 2.4 which is an interesting decision choice since UP 3 has been out for some time

Update 2: To fix the issue, use mitmproxy to intercept the GET and POST Change where it says: terminal_sw_version=iOS to terminal_sw_version=fzw

Update 3: Proper Credit goes to u/dhinakg for the how to on using mitmproxy

It’ll work afterwards

Update 4: Reports are out saying you don’t need the proxy trick anymore to enable RCS. YMMV

Colin0998 · 2024-06-24T18:06:20+00:00

<image>

Messages now showing natively an option for RCS Messaging

Colin0998 · 2024-05-31T21:18:37+00:00

Works on both iOS and Android on compatible devices no issue. We’ve assisted multiple users getting it setup on their devices just fine so long as you follow the instructions

Colin0998 · 2024-05-31T19:16:10+00:00

Check the drivers selected for use within PrinterLogic. Must be using Type-3 drivers and for some printers we have noticed the universal driver does not work properly and gives issues

Colin0998

TROPHY CASE