Am 2014-04-20 23:49, schrieb Karl E. Jorgensen:
On Sun, Apr 20, 2014 at 01:01:53PM +0200, email@example.com wrote:
maybe you have a clue about the issues im having since several
My Homeserver is running Debian Jessy right now, the network issues
where there with wheezy aswell.
after a fresh boot my network behaves like it should archiving near
gbit speeds which is nice, after a random amount of uptime though my
throughput degrades below 100mbit network speeds (about ~3.5MB/s)
i measured using iperf.
You don't explicitly say... Does a reboot "cure" the problem
Yep thats exactly what a reboot does for me, i tenad to reboot about
once every 2-3 days because of this issue, not something you would
expect from a unix OS :D
If so, does a "ifdown eth0" + "ifup eth0" have the same effect?
necessary: Unplug and re-plug the cable between "ifdown" and
"ifup"...) [A full reboot is a bit like a sledge hammer... very
I have yet to try this, will report back when i have the performance
problem again and try it
- Asus P8H67-M PRO
- Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz
- 16 GB DDR3 Ram (2*8GB Kingston ram)
- Intel Corporation 82541PI Gigabit Ethernet Controller
- TP-Link 8-Port gbit switches (2 of em between home-server and
*two* switches between server and clients? Sounds a bit unusual - at
least for a home set-up...
Well im a Console Collector and my Linux Server is right behind my
Home Entertainment area in the living room. thats where the first
switch is located to hook all the entertainment stuff up to the lan,
then there is one uplink line going to the other end of the room where
the 2. switch is located, connecting my Desk PC, Laptop, printer, wifi
ap and internet Gateway to the lan aswell.
Ive tried diffrent things so far:
- Switched from a switched cabling setup to Crosslink.
Hm... AFAIK modern network cards tend to adjust themselves to both
"normal" and cross-over cables (which I believe that "crosslink"
Jup i wasnt clear enough here i guess, i connected the client (one at
a time) with the server directly using a normal off the shelf patch
cable, i just call it crosslinking because no switch is in between
- Swapped out the cheap asrock motherboard with asus
- Changed from onboard realtek network chip to PCI Intel Gbit card
Hm.. That would likely rule out any network card issues.
- Reinstalled OS several times
.. which would most likely rule out any OS bugs. But not
Jup i guess (wheezy and jessy)
- Testing from diffrent clients (Win 7, Linux Mint, Debian, Ubuntu)
... which would then most likely rule out administrator mistakes:
is sufficient differently from anything else to make it difficult to
make the same mistake across platforms.
And Hardware issues on my client aswell since they all are diffrent
chipset network hardware
- Downloading vendor drivers and using them instead of the kernel
Nothing so far had worked to get my gbit speeds stable over a few
When you measure the speed, between which two points do you measure
client -> tp-link -> tp-link -> server
or with direct connection circumventing the switches
client -> server
I'm concerned about the TWO TP-Link switches: The diagnostics you
done so far does not appear to rule them out.... Does your traffic
have to pass through both of them? If so, how are they switches
imho i ruled them out with directly connecting my client(s) one at a
time to the server using an patch cable circumventing those switches
in question. The reported degration in network speed happens there
Based on what you have written, my main suspects would be the two
switches - with a focus on the "nearest" switch...
im open to ANY suggestions here even if they involve building a
custom kernel or other magical hakkery ;D
Well - it looks like you have put a fair amount of effort into
this.... But until the problem is narrowed down, this would probably
be as likely to resolve the problem as a goat sacrifice ... You
haven't got a spare goat, have you? :-)
Mhm i have a few gots (Long Goat, Feather Goat etc...)
Dunno if they count as spare's?
Hope this helps
Jup defenetely, a few more ideas and things i should gather to help
debugging pinpointed :)
 I'm assuming eth0 here....
 A live one would constitute a "hot spare", right? Yeah. Tangent.
Karl E. Jorgensen