From Newsgroup: comp.os.linux.misc

Related long thread.

ANYway ... the problem of the roughly 30-minute
drop-outs was "solved".

Not by some obscure config-file settings but just
by getting a different brand/chipset of wifi dongle.

LIKE TP-Link, it's my go-to, but even the latest
updates didn't solve it.

SO, got a NetGear with a somewhat newer different
chipset.

No more drop-outs :-)

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-09-20, c186282 wrote:

Related long thread.

ANYway ... the problem of the roughly 30-minute
drop-outs was "solved".

Not by some obscure config-file settings but just
by getting a different brand/chipset of wifi dongle.

LIKE TP-Link, it's my go-to, but even the latest
updates didn't solve it.

SO, got a NetGear with a somewhat newer different
chipset.

Again, you're focusing on the wrong names. You don't call it "NetGear
with a somewhat different chipset", you call it by the chipset
manufacturer name :-)

No more drop-outs :-)

--
Nuno Silva
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 9/20/26 04:02, Nuno Silva wrote:

On 2026-09-20, c186282 wrote:

Related long thread.

ANYway ... the problem of the roughly 30-minute
drop-outs was "solved".

Not by some obscure config-file settings but just
by getting a different brand/chipset of wifi dongle.

LIKE TP-Link, it's my go-to, but even the latest
updates didn't solve it.

SO, got a NetGear with a somewhat newer different
chipset.

Again, you're focusing on the wrong names. You don't call it "NetGear
with a somewhat different chipset", you call it by the chipset
manufacturer name :-)

Not even interested. Works, so it WORKS.
Two TP-Link units did not. Clearly a
driver/chipset issue - but incredibly
obscure.

No more drop-outs :-)

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-09-21, c186282 wrote:

On 9/20/26 04:02, Nuno Silva wrote:

On 2026-09-20, c186282 wrote:

Related long thread.

ANYway ... the problem of the roughly 30-minute
drop-outs was "solved".

Not by some obscure config-file settings but just
by getting a different brand/chipset of wifi dongle.

LIKE TP-Link, it's my go-to, but even the latest
updates didn't solve it.

SO, got a NetGear with a somewhat newer different
chipset.

Again, you're focusing on the wrong names. You don't call it "NetGear
with a somewhat different chipset", you call it by the chipset
manufacturer name :-)

Not even interested. Works, so it WORKS.
Two TP-Link units did not. Clearly a
driver/chipset issue - but incredibly
obscure.

Trust me, it becomes much less obscure if you focus on the chipset
manufacturer instead of the name that is in the box.
--
Nuno Silva
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

In article <118r0h4$3s7cd$2@dont-email.me>,
Nuno Silva <nunojsilva@invalid.invalid> wrote:
...

Trust me, it becomes much less obscure if you focus on the chipset >manufacturer instead of the name that is in the box.

It is probably good policy in general to *not* trust some anonymous online poster - unless/until you have some idea of his or her credentials.
--
No puppet.
No puppet.
You're a puppet.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 21/09/2026 05:02, c186282 wrote:

On 9/20/26 04:02, Nuno Silva wrote:

On 2026-09-20, c186282 wrote:

Related long thread.

ANYway ... the problem of the roughly 30-minute
drop-outs was "solved".

Not by some obscure config-file settings but just
by getting a different brand/chipset of wifi dongle.

LIKE TP-Link, it's my go-to, but even the latest
updates didn't solve it.

SO, got a NetGear with a somewhat newer different
chipset.

Again, you're focusing on the wrong names. You don't call it "NetGear
with a somewhat different chipset", you call it by the chipset
manufacturer name :-)

-a Not even interested. Works, so it WORKS.

I have found netgear among the more unreliable routers in my life
TP link not much better.
Dlink was pretty good.

-a Two TP-Link units did not. Clearly a
-a driver/chipset issue - but incredibly
-a obscure.

No more drop-outs :-)

--
rCLThere are two ways to be fooled. One is to believe what isnrCOt true; the other is to refuse to believe what is true.rCY

rCoSoren Kierkegaard

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 9/21/26 07:21, The Natural Philosopher wrote:

On 21/09/2026 05:02, c186282 wrote:

On 9/20/26 04:02, Nuno Silva wrote:

On 2026-09-20, c186282 wrote:

Related long thread.

ANYway ... the problem of the roughly 30-minute
drop-outs was "solved".

Not by some obscure config-file settings but just
by getting a different brand/chipset of wifi dongle.

LIKE TP-Link, it's my go-to, but even the latest
updates didn't solve it.

SO, got a NetGear with a somewhat newer different
chipset.

Again, you're focusing on the wrong names. You don't call it "NetGear
with a somewhat different chipset", you call it by the chipset
manufacturer name :-)

-a-a Not even interested. Works, so it WORKS.

I have found netgear-a among the more unreliable routers in my life
TP link not much better.
Dlink was pretty good.

Used to use DLink ... not sure why I stopped.
Remember they were good. MIGHT have been
crappy caps in the power supplies ... remember
having to fix two large-ish switches, lucky
I salvaged parts off old motherboards.

Never had any major issues with NetGear routers.
Started buying lots of TP-Link stuff seven or
eight years ago, again 'satisfied'. Office ...
biz cable connection ... used a software router,
"IP Fire", despite the funny name - more than
adequate. Ran it on a SuperMicro mini-box.

My particular little wifi issue - and I'm not
gonna take the time to try and find the exact
chip-set but it was two different TP-Link
units - I put this down to some subtle driver
issues, MAYbe unique to MX or the Debiverse
in general. In this case a NetGear "NightHawk"
that can allegedly use extra-speed wifi even
though I have no good way to send it ... the
drop-outs went away.

Issues that only happen RARELY are hell to
track down. Every few minutes, MAYbe you
will spot something.

Alas I cannot get reliable 'wired' internet
where I can buy my own gateway/router. Once
the DSL went, that was the end of it. Stuck
with wireless internet forever. Still considering
a StarLink unit as an aux, maybe even primary.
The price seems OK. Do have limited 'good'
mounting locations alas.

-a-a Two TP-Link units did not. Clearly a
-a-a driver/chipset issue - but incredibly
-a-a obscure.

No more drop-outs :-)

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 22/09/2026 07:11, c186282 wrote:

Never had any major issues with NetGear routers

People used to give them to me after a thunderstorm to 'see if I could
fix them' I never could.
DSL all shot to fuck.
I still have one I use as a wifi point. Wifi and Ethernet still work
--
"What do you think about Gay Marriage?"
"I don't."
"Don't what?"
"Think about Gay Marriage."


--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-09-21, Kenny McCormack wrote:

In article <118r0h4$3s7cd$2@dont-email.me>,
Nuno Silva <nunojsilva@invalid.invalid> wrote:
...

Trust me, it becomes much less obscure if you focus on the chipset >>manufacturer instead of the name that is in the box.

It is probably good policy in general to *not* trust some anonymous online poster - unless/until you have some idea of his or her credentials.

Sorry if that came across as a too strong statement. It does seem to be
quite true regarding hardware support.

But, if your reply is more than just a remark on trust, and there's a
reason you find this to be off the mark regarding WLAN NICs, I'd like to
know.
--
Nuno Silva
--- Synchronet 3.22a-Linux NewsLink 1.2