Hacker News Reader

Comment by m463 | Hacker News Reader

Killing local network access is an actual bug.

related - I wonder if this is specific to esim or if this would happen with a regular sim too?

and can you just call your carrier?

I had a comcast business router and it started broadcasting an open comcast wifi access point (for comcast customers). I called and asked them to turn it off and they did.

View on HN

I just checked my phone, There were 3 verizon networks in there I don't recognize. I'm using a regular SIM.

The carrier told me to contact apple.

And in my case, I can’t exactly harass all my neighbors to disable their “free hotspot”. I should be able to control my own phone and dictate what it does/does not connect to.

> I should be able to control my own phone

That battle was lost a long time ago. I should be able to restrict (or know) what the apps do. I should be able to firewall my phone. I should be able to access the files on it.

But in the end, only apple decides this, and their decisions are self-serving.

Sheesh, a linux phone can't come fast enough.

What do you mean?

Sent from my Librem 5.

morally you cant but actually you can, go to a few thift shops, get enough routers to cover all channels, create many screaming imposter networks portal eachone to something not pretty, soon[day or 2] you will see the original network gone.

beware of FCC.

This is perfectly legal, FCC will not care.

But it will not work.

saturating the air with [SSID] at high dB across all channels absolutely will work, it compels the operator of [SSID] to turn it off and buy another router.

the high dB signal is where the FCC Will care.

There is no way ATT is going to abandon the attwifi SSID.

You did not mention exceeding Part 15 emitter limits in your previous post.

screaming was mentioned, and im not talking about making ATT abandon the attwifi SSID im talking about the end user abandoning the onsite equipment.

That’s not how 802.11 works. If your device can’t connect to a given BSSID that’s broadcasting an SSID it wants, it will put that BSSID on an ignore list and try the next one, whatever the received signal strength.

You can of course saturate the entire spectrum, but that breaks every network, not just the SSIDs you’re "waging war" against, and will probably get you a visit by the FCC sooner or later.

Maybe you could broadcast thousands of spoofed BSSIDs; I have no idea about the legality of that, and the legitimate operator of the SSID might not find that too funny and take legal action against you as well, as that would be pretty transparent denial of service on a public band.

yes you have it right. this has been done in the past, and can still be done.

legally, you dont want to do it. i have had experiences with seeing my SSID coming from a router that is not mine, and the nieghbor basically said effoff ill do what i want. in that case i did what i want as well.

What’s the problem with your neighbor using "your" SSID?

It’s not like anybody can "own" an SSID name, and if you’re using WPA, the only effect would be a few milliseconds longer of initial connection time per device.

Actively running a DoS against your neighbor might or might not be legal, but it sure is petty (and given the above, unnecessary).

when someone follows your wifi around, repeatedly changing thier SSID to match yours, they are doing it on purpose.

https://news.ycombinator.com/item?id=35449153

this is called MITM

> Killing local network access is an actual bug.

Yeah in additional to any local servers you have it would break continuity (handoff etc), it would break casting. Sounds very poorly thought through.

Reply on news.ycombinator.com