XPost: alt.comp.os.windows-11
From: wasbit@REMOVEhotmail.com
On 01/12/2025 13:47, Frank Slootweg wrote:
> wasbit wrote:
>> On 28/11/2025 19:03, Paul wrote:
>>> On Fri, 11/28/2025 3:47 AM, wasbit wrote:
> [...]
>>>> Hmmm! 19 replies & not a mention of bandwidth theft.
>>>
>>> It seems to be mostly a tale about semi-broken or half-functional kit.
>>> Since the OP has his own paid Internet service, there is no
>>> evidence of "100% leeching" going on, particularly. I bet the
>>> OP could tighten up his settings a bit.
>>
>> The OP knows he has connected to the neighbour's wifi but said nothing
>> about having permission.
>> Until clarified it is bandwidth theft.
>
> micky's *computer* *accidentily* connected to his neighbour's WiFi:
>
Whether it was accidental or not he connected to his neighbour's wifi.
Once he realised, without permission it was theft.
In the UK it is an offence under the Communications Act 2003 & possibly
the Computer Misuse Act.
It is up to the OP to clarify.
>
> This morning I rebooted and on its own, it connected to the wifi of a
> neighbor, but not to my own wifi Hmmm after 30 minutes of using his,
> it just switched to my wifi. But still not to the cable, which I
> thought would take priority, plusd last night the Troubleshooter said my
> laptop's wifi was bad too, the one that hasn't worked since February.
>
>
> So *instead of* connecting to his "cable" (wired LAN?) or WiFi, his
> *computer* (*not* micky) connected to his neighbour's WiFi.
>
> Could he have disconnected the neighbour's WiFi in those 30 minutes?
> Yes. Did he know how to do that? I don't know.
>
> As to "bandwidth theft": I'm sure his accidental use, doesn't deserve
> your harsh condemnation.
>
--
Regards
wasbit
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
