From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] network transfer speed
Date: Sun, 17 Jan 2021 10:51:59 +0000 [thread overview]
Message-ID: <4089242.ejJDZkT8p0@lenovo.localdomain> (raw)
In-Reply-To: <XRW6JCZV.FW2CNC5D.Q5DFCNE2@ASUQ6X7C.IZ5SFVVG.GCXWSEAD>
[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]
On Saturday, 16 January 2021 20:59:58 GMT Jack wrote:
> On 2021.01.16 15:36, thelma@sys-concept.com wrote:
> [snip.....]
>
> > 2.) The two Gentoo PC that are meters away from the switch are my
> > concern firs.
> > One is a server, another small PC run 24/7 and both negotiated speed
> > of 1000 with the switch.
>
> I may be way off base here, but if the switch is connected to a router,
> packets from one PC go to the switch and then to everything else
> connected to it, including both the other PC and the router. Is there
> any chance the router is passing packets back to the switch to get to
> the second PC? I can imagine that causing lots of problems. However,
> I would hope it is smart enough to know it doesn't need to do so, since
> both PCs show up on the same router port.
Unmanaged witches for the consumer market tend to last fewer years than they
used to. This is because their power supply as well as the components on the
circuit board are now manufactured as cheaply as possible. Good for repeat
sales, bad for the consumer.
The switch may fail outright, in which case the network fault is obvious. Or,
it may start failing intermittently. Typical failure modes are for one or
more ports to stop working altogether, or downgrade the port speed - as
observed by the OP. Removing the ethernet cable, powering down the switch,
re-inserting the ethernet cable and powering up the switch may restore the
correct operation on the port.
It was usually the case electrolytic capacitors on the circuit board could be
replaced to fix the switch, but more recently some manufactures no longer use
electrolytic capacitors - so I'm not sure repairs are even possible.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-17 10:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 6:56 [gentoo-user] network transfer speed thelma
2021-01-15 7:49 ` Hogren
2021-01-15 8:34 ` Raffaele BELARDI
2021-01-15 13:26 ` Hogren
2021-01-15 14:13 ` Michael
2021-01-15 16:38 ` thelma
2021-01-15 7:57 ` bobwxc
2021-01-15 8:27 ` Raffaele BELARDI
2021-01-15 8:42 ` bobwxc
2021-01-15 9:58 ` Michael
2021-01-15 16:51 ` thelma
2021-01-15 16:55 ` Jack
2021-01-15 17:36 ` thelma
2021-01-15 22:43 ` thelma
2021-01-16 18:55 ` Michael
2021-01-16 20:27 ` thelma
2021-01-15 8:11 ` Raffaele BELARDI
2021-01-15 22:56 ` thelma
2021-01-15 23:38 ` William Kenworthy
2021-01-16 0:49 ` Manuel McLure
2021-01-16 4:00 ` Adam Carter
2021-01-16 20:36 ` thelma
2021-01-16 20:59 ` Jack
2021-01-17 10:51 ` Michael [this message]
2021-01-18 7:57 ` Raffaele BELARDI
2021-01-18 8:46 ` J. Roeleveld
2021-01-18 9:58 ` Raffaele BELARDI
2021-01-18 10:19 ` J. Roeleveld
2021-01-18 11:41 ` bobwxc
2021-01-18 19:13 ` thelma
2021-01-19 7:46 ` Raffaele BELARDI
2021-01-19 15:15 ` thelma
2021-01-19 14:11 ` J. Roeleveld
2021-01-19 14:34 ` Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4089242.ejJDZkT8p0@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox