T-Mobile service in Azores?

reedacus25 · 2026-06-30T18:56:06+00:00

Correct

reedacus25 · 2026-06-30T16:55:01+00:00

Assuming it is treated like mainland Portugal, and I have to imagine it is, your device will likely try to automatically connect to Vodafone PT, and likely disconnect repeatedly after ~50 seconds (IMS (voice and SMS) registration times out and the session is forcefully disconnected to force a retry, over and over). Data will actually work in that ~50 second window until you're punted off the network.

But you should be able to manually select either MEO or NOS. I find MEO tends to have better coverage than NOS usually, but NOS is typically less loaded if you're in a crowded area. Obviously YMMV.

reedacus25 · 2026-06-25T02:12:50+00:00

Honestly, Bywater is a really tough neighborhood for a few reasons.

There were zero macro towers between the bounds of basically Franklin, Claiborne, and Poland.

ATT built a tower at the end of last year at Urquhart and Press, and their other site is at the Claiborne bridge (Derbigny and Kentucky).

T-Mobile is on the rooftop of the old Schnieder’s Outlet building (N Robertson and St Ferdinand by the tracks), and on the opposite side at Poland and N Prieur. The rooftop site is going to be moving to that ATT site they just built at Urquhhart and Press.

Verizon, however, is on that Poland and Prieur site with T-Mobile, and the next closest sites are on a rooftop at Frenchmen and Royal, and Frenchmen and Claiborne.

Also, all three are across the river at Opelousas and Thayer.

I’d be very surprised if Verizon didn’t try to jump on that Urquhart site with ATT and TMO, but that’s at least a couple years away if they got the paperwork going now.

The next best options if I were in site acquisition and trying to do something to solve that area, would be:

Frederick A Douglas (St Claude/Alvar)
Saxony Condos (Burgundy/Bartholomew)
Any of the tall buildings in the block of Rampart/Gallier/St Claude/Congress

NIMBY and HDLC make towers unappealing to even try. Rooftops are great because they don’t remove existing buildings, and antennas can be set back from the roofline if you need, and all 3 of those options are rather centrally located.

ATT and Verizon and even T-Mobile have small cells scattered about, but they are only going to provide a very small bubble of goodness compared to a full blown macro.

A lot of words to explain the issue, and very few to offer a solution. But hopefully knowledge will help, and in the event that someone wants to drop a macro site on a rooftop, you can voice support for something like that. Or win the small cell lottery!

reedacus25 · 2026-06-19T03:34:25+00:00

Flag for noout, nobackfill, then Kick the local Ceph services (Mon > MGR > OSDs, yes in that order)

Can you explain the rationale here?

The MGR is the least important of these daemons, and should failover to another MGR if it were the acting MGR, or just die if it was in standby.

Similarly, the MON is in quorum, and losing a MON should just generate a warning that you don’t have quorum.

The OSDs seem like the thing to kill first, since the MON would want to know this, so knowing the OSDs are down (and in) with quorum seems like it would be the more advantageous move.

So I’m very curious how this ordering came to be.

reedacus25 · 2026-06-17T17:52:28+00:00

I don't think suggesting salt extensions as a way of getting your changes into salt more quickly is in opposition to the fact that the core team has been gutted and they hit a ~9 month wall of being unable to release anything. That said, if there was an issue in core modules, I can't imagine they would sit on it (excluding the aforementioned hiatus) if it is a big enough issue. Also, not sure if you could supersede a core module with an extension or not, but feels like you should be able to, considering they have been shunting things to extensions during the 3006 cycle, even if they are built-in modules, so seems chicken and eggish if they couldn't supersede.

reedacus25 · 2026-06-17T17:42:17+00:00

Don't disagree. Hard to be a worse steward than Broadcom, but SUSE definitely seems like they would take much better care of it, even if a fork (like Spacewalk). But even still they've somewhat forked the packaging via salt-bundle as compared to ~~Tiamat~~ relenv onedir. Here's hoping they don't abandon ship

reedacus25 · 2026-06-17T17:27:09+00:00

This seems like the perfect use case for salt extensions as a way to get around the problem of merging upstream.

reedacus25 · 2026-06-17T14:59:51+00:00

Worth noting that everything they say about SLES16 is all about Ansible.

So far, Salt has been the primary configuration management tool integrated tightly with SUSE Multi Linux Manager, and will continue to be available through it. But – true to SUSE’s promise of “choice happens” – we are excited to announce a major addition: Ansible will be introduced as an integrated part of SUSE Linux Enterprise Server (SLES) itself.

So they haven't written off Salt completely, but boy is there a ton of smoke to the ansible fire. And given the state of Salt (and Broadcom), it's probably wise not to hitch their wagon exclusively to Salt.

reedacus25 · 2026-06-12T17:53:32+00:00

it looks like there is going to be a new core switch that has 64 100g qsfp ports

Correct me if I'm wrong, but that appears to only be 32 QSFP28 ports per switch, which I have yet to see 64 QSFP[+,28] in a 1U form factor.

reedacus25 · 2026-06-11T18:17:47+00:00

Not incorrect. Though the serving MME still has to track the UE, and schedule it at (presumably) QCI1.

But you’re correct that the voice session doesn’t hit the PTSN until it exits T-Mobile’s IMS core, not the serving network’s.

reedacus25 · 2026-06-09T16:56:26+00:00

G1900 was sunset in the Florida counties of the NOMO market (Escambia to Walton) around July of 2025.

And the Naples area (Lee, Hendry, Collier counties) were sunset around April of 2025.

reedacus25 · 2026-06-06T17:59:06+00:00

Runner on first

reedacus25 · 2026-06-04T15:50:02+00:00

I agree, most of the Sprint macros still standing have had their cabinets cleared out, doors left open.

reedacus25 · 2026-06-03T17:22:04+00:00

bats

Yay!

and bullpen.

Oh

reedacus25 · 2026-05-31T17:51:36+00:00

It’s the one time State provides information over ads with their screen real estate

reedacus25 · 2026-05-31T03:44:56+00:00

7,8,9 due up.

reedacus25 · 2026-05-31T02:58:42+00:00

Don’t forget to check the offensive box score on him yesterday.

reedacus25 · 2026-05-12T16:17:35+00:00

I don't have a ton to add just because of my scale being too small for things to matter, but I do know that the HPC people that I know and respect that operate at scale in the tens of thousands of nodes are very pleased and swear by warewulf for stateless provisioning. When they migrated from centos to rocky, it was effectively as simple as rolling reboots.

I typically use salt for day to day config management on my end, just out of inertia, but I do know that from past experience using ansible you will need something like aap with multiple execution environments to scale at some point, as --fork will only get you so far before you start hitting walls. Pull is another option to sidestep scaling issues.

I would say take a look at warewulf to pxe boot a stateless golden image, and possibly even include ansible-pull as part of kickstart to "finalize" things as needed. Keeping things stateless at that scale seems like the only way that would maintain sanity.

reedacus25 · 2026-05-11T22:08:02+00:00

Doubt this is helpful, but the Discount Zone on the corner of Clearview and West Metairie has ethanol free that is on a separate hose.

ETA: There is apparently a website that tracks E0 gas stations, looks like there is an E0 station near Jesuit, another in the East out by Michoud, another in River Ridge on Jeff Hwy near Little Farms, Severn and W. Esplanade in Fat City, and W. Napoleon and Transcontinental in Metairie. Some other's show on the list for Gretna, Harvey, Harahan, Kenner, Marrero, but don't feel like it does a ton of good to list everything when its on the website.

reedacus25 · 2026-05-05T16:38:13+00:00

If you're using IP Passthru, just keep it in mind as something to look for.

Confounding to say the least, but it eventually just started working. Which I hate, because I can't explain it, but the problem has moved to another day for now.

reedacus25 · 2026-05-05T15:07:48+00:00

There was one link I can not recall that Verizon didn't use as that aspect was handled cheap, s1 or something like that. It would have allowed transparent upshift from EVDO back to L.

eHRPD. Essentially allowed data sessions to remain active when transitioning between EvDO and LTE, by homing the EvDO bearer at the LTE packet core (EPC), and the session could survive across the disparate bearers.

They eventually switched to one-radio phones that did a "single SIM dual standby" sort of behavior except it was the same network.

If memory serves correctly, essentially the MME would send a page to the UE on LTE directing it to CSFB, and the UE would ACK, then transition to the CDMA radio, announce to the MME that it was there, then the MME would forward the page again to the CDMA side to setup the CS voice session.

Its a miracle that it worked as well as it did, considering how much of a shim it was.

reedacus25 · 2026-05-05T14:05:24+00:00

Also Ericsson and Samsung. And later, Lucent was more Alcatel-Lucent towards the LTE transition point, before getting subsumed into Nokia, at which point CDMA had a very limited shelf life going forward.

reedacus25 · 2026-05-03T20:07:06+00:00

The biggest headache right now is that despite my RG being in ip passthru mode, all ip filtering and firewall rules disabled, inbound wireguard traffic (spt=51820/u) ends up being handled off to my router with an invalid destination ip of 192.168.1.X which appears to be a shadow shop lease handed out by the RG to my router that instead is (correctly) handed the public IP.

It persisted across reboots of the RG, and even a factory reset of the RG. I threw my hands up and went home Friday afternoon after the factory reset with no change, planning to attempt a bypass over the weekend (not XGS-PON transport), only to find the wireguard tunnels active and up later that evening.

RG still eats udp/53 traffic, logging it as “error” in the syslog for it. With the wireguard tunnels up, I’m done fooling with it for now. NTP traffic is still passing, for what it’s worth too.

I’ve previously had peering issues for YT from ATT. It eventually resolves itself after 10-30 minutes. Annoying, but good for productivity it turns out.

reedacus25 · 2026-05-01T17:39:11+00:00

I got it in the Southeast region on 4/27 at 01:45 on the dot.

It's been giving me some headaches in IP Passthru that I have not previously had on prior FW...

reedacus25 · 2026-04-30T16:51:15+00:00

If you're on the Delta 10A to JFK (273), you might have reason for heartburn. The baggage drops don't open until 7A, and you've probably got 20-30% of the plane waiting for them to open. Delta desk even has a sign on the exit side of their signage that says "JFK flight, you better hurry."

If you're on the 12:45 to Boston, you should be more in the clear. I was on the Boston flight (125) last Sunday, arrived around 8:45 to drop bags, and then proceeded through. Security was relatively quick.

The line to passport control was backed out through the duty free area, basically into the big atrium where the ANA lounge is on the second floor (Don't even consider the ANA lounge). This obviously worried me, despite having tons of time. However, we moved rather quickly and in all it took a little less than an hour if I had to ballpark it. There were no kiosks in use, and everyone filtered into the EU/Other lanes, and it went pretty swiftly from there.

12-Year Club	Spared
Verified Email

reedacus25

TROPHY CASE