

Oh, yeah, that’s probably the more logical explanation.


Oh, yeah, that’s probably the more logical explanation.


I don’t think that was them self-censoring, I think that was them failing to markdown successfully.


The fabled write-only system


Yeah, I agree with ‘nuke first ask questions later’ when your compromised host is impacting other devices. If and only if i knew the attempts weren’t going anywhere or doing anything would I consider unicing the vm/container to see what happened.
I imagine the OS is intentionally varying TX strength on the cell radio to spoof precise location detection from the tower network, since that would be the only way to meet the stated goal.
I can’t even convince my spouse to switch to firefox to get adblocking back. Browsers are entirely transparent to most users :\


Without having access to a known good connection (or known good setup) you can’t 100%, but if you can take packet captures at the handoff to the isp equipment and the far side doesn’t receive them, that’s a pretty clear indicator to me. At the very least it would be enough for me to reach out to them and ask what’s up.


That’s because that’s actually just the down payment. The recurring comes from board seats and roles in name only later down the line.


My experience was miserable attempting to do so, to the point that it was better to just nuke everything across 4 drives and start over


That seems reasonable to me as far as implementations go. The ones where they will autoassign always just overload pd index 0 which is worse than doing nothing imo lmao


It is. How At&t handles it is they hand out only 1 /64 of the delagted /60 (by default) per explicit IA-PD request, rather than the full /60 they allocate by default (which, note, is not on a nibble boundry like it’s supposed to be, and you only get half of that as usable).
But on every gateway device I’ve used, even if you get a full /56 prefix, you still have to explicitly assign out each /64 to sub interfaces. Really, ipv6 is a bunch of great ideas which were ruined by shitty implementations everywhere.


Nah, it’s that the tooling on the infrastructure side still sucks in current year. Why tf as an AT&T customer can I not get more than one PD from upstream without editing my dhcpc conf? And why can my gateway, once getting multiple PDs, not tell me which ones I’ve assigned out to subinterfaces? Not to mention there’s still infrastructure devices which can’t have v6 management interfaces, layer3 switches which can’t act as RAs, all sorts of shit like that.


So I can address this from my experience, their mileage may vary: sometimes it’s about saving yourself time. Say if your normal daily driver is a desktop for some reason, but you’re on call to do a task. You can (in theory) do that task from your home PC or you can drive in to the office for (arbitrary round trip time) to do it ‘properly’. Even when I used windows at home /and/ had a work laptop I still maintained a VM (an ersatz air gap) for work shit on my personal PC for convince sake.


It’s not like they have a real job that requires them to do anything, so they gotta find something to fill the void


Yeah, i would not consider blocking wireguard to be even remotely (heh) acceptable in 2025. Tell your bro to go back to arguing with AT&T, maybe just with their resi service.
It doesn’t exist except there’s a script out there somewhere that will click the buttons for you iirc. No idea where it is or if it’s maintained anymore though :(
They’re probably the only reason it hasn’t popped yet: still searching for someone to hold the bag. But the longer they wait, the bigger the number gets and the less likely it is for them to find one. Eventually someone’s going to cut their losses and it’s going to be a bloodbath.


Just open a second tab in chrome and you’ll be redlining that puppy.


Obviously he should go get a Guinness instead
No, because there wouldn’t be anything connecting the two ports together. In your scenario, all each side would be able to do would be to talk to ‘cpu’, there would be no mechanism to forward traffic upstream without iptables or something similar handling that function.