Kodi Community Forum

(2018-11-06, 22:44)jmerrilljr Wrote: [ -> ]Here is the dmesg | pasteinit: http://ix.io/1raX. #1016 plays fine. #1016x does not. 

iperf -c 10.0.1.55 -u -P 1 -i 1 -p 5001 -f G -b 100.0M -t 10 -T 1

Can you test TCP with iperf rather than UDP?

This doesn't look good:

text:


[   19.362489] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0

[   19.362505] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[   19.362509] pcieport 0000:00:1c.0:   device [8086:9c14] error status/mask=00001000/00002000

[   19.362513] pcieport 0000:00:1c.0:    [12] Timeout               

[   22.571954] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0

[   22.571976] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[   22.571983] pcieport 0000:00:1c.0:   device [8086:9c14] error status/mask=00001000/00002000

[   22.571991] pcieport 0000:00:1c.0:    [12] Timeout               

[   22.751504] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0

No idea what is causing that at the moment. Unfortunately the log spam has resulted in the log buffer being truncated.

Can you add log_buf_len=16M to your kernel command line, then boot with #1022 (4.18.14, no problems) and run dmesg | pastebinit, then upgrade to #1106 (4.19.1, kernel errors) and again run dmesg | pastebinit, pasting both links here - hopefully this time we'll have complete kernel logs for both a working and non-working kernel. I'll then be able to do some digging. It looks like 4.19 introduced quite a number of r8169-related bugs.

@jmerrilljr once more thing that might help: if you can test all of the 4.19-rc test builds (there were 8, rc1-rc8) it might help narrow down the range that includes the breaking commit. You can find links to the 4.19-rc test builds in PR2937. Start with 4.19-rc1 and if that doesn't have the problem then test the next release ie. 4.19-rc2. Post which release of 4.19-rc is the first with the problem. Thanks.

Also, can you describe what your PC is connected to - what type of cable (CAT5, CAT5e etc.), what type of switch (make/model/brand).

(2018-11-07, 15:17)Milhouse Wrote: [ -> ]@jmerrilljr once more thing that might help: if you can test all of the 4.19-rc test builds (there were 8, rc1-rc8) it might help narrow down the range that includes the breaking commit. You can find links to the 4.19-rc test builds in PR2937. Start with 4.19-rc1 and if that doesn't have the problem then test the next release ie. 4.19-rc2. Post which release of 4.19-rc is the first with the problem. Thanks.

Also, can you describe what your PC is connected to - what type of cable (CAT5, CAT5e etc.), what type of switch (make/model/brand).

 Milhouse, I am running cat6 cable from a Belkin 5D5141-5v4 switch. All my tests have been run on the same 30 gig .mkv file. Other than that I am pretty much lost and overwhelmed. I will try the quoted 4.19 -rc test builds.

(2018-11-07, 15:12)Milhouse Wrote: [ -> ]

(2018-11-06, 22:44)jmerrilljr Wrote: [ -> ]Here is the dmesg | pasteinit: http://ix.io/1raX. #1016 plays fine. #1016x does not. 

iperf -c 10.0.1.55 -u -P 1 -i 1 -p 5001 -f G -b 100.0M -t 10 -T 1

Can you test TCP with iperf rather than UDP?

This doesn't look good:

text:
[ 19.362489] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:00:1c.0

[ 19.362505] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 19.362509] pcieport 0000:00:1c.0: device [8086:9c14] error status/mask=00001000/00002000

[ 19.362513] pcieport 0000:00:1c.0: [12] Timeout

[ 22.571954] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0

[ 22.571976] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 22.571983] pcieport 0000:00:1c.0: device [8086:9c14] error status/mask=00001000/00002000

[ 22.571991] pcieport 0000:00:1c.0: [12] Timeout

[ 22.751504] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0

No idea what is causing that at the moment. Unfortunately the log spam has resulted in the log buffer being truncated.

Can you add log_buf_len=16M to your kernel command line, then boot with #1022 (4.18.14, no problems) and run dmesg | pastebinit, then upgrade to #1106 (4.19.1, kernel errors) and again run dmesg | pastebinit, pasting both links here - hopefully this time we'll have complete kernel logs for both a working and non-working kernel. I'll then be able to do some digging. It looks like 4.19 introduced quite a number of r8169-related bugs.  

I have no idea how to access my kernel command line. Also iperf can't connect to libreelec via TCP. I must be doing something wrong. Thanks for all your help.

(2018-11-07, 18:19)jmerrilljr Wrote: [ -> ]I have no idea how to access my kernel command line. Also iperf can't connect to libreelec via TCP. I must be doing something wrong. Thanks for all your help.

TCP should be the default for iperf - you're telling it to test UDP by using the -u option. You're also limiting the bandwidth to 100Mb (which you'll probably never see with UDP even without kernel issues).

I'd suggest using the following iperf options on the client:

text:


iperf -c 10.0.1.55 -t 60 -i 10

On the server, you only need:

text:


iperf -s

To access your kernel command line, you need to edit /flash/syslinux.cfg.

To make the /flash partition writeable, you first need to run mount -o remount,rw /flash.

You can use vi or nano to edit /flash/syslinux.cfg.

Make a backup of your current file with:

text:


cp /flash/syslinux.cfg /flash/syslinux.cfg.bak

The kernel command line is the line that begins with APPEND so if your current file looks like:

text:


DEFAULT linux

PROMPT 0



LABEL linux

 KERNEL /KERNEL

 APPEND boot=LABEL=System disk=LABEL=Storage quiet

then you need to change /flash/sylinux.cfg to be:

text:


DEFAULT linux

PROMPT 0



LABEL linux

 KERNEL /KERNEL

 APPEND boot=LABEL=System disk=LABEL=Storage quiet log_buf_len=16M

Obviously, if you get this wrong and corrupt the contents of this file you may have a non-booting system which you can recover using LibreELEC booted from a memory stick (you'll need to boot into live live mode, enable ssh, login with ssh and your internal HDD/SSD will be available via the /media path - restore syslinux.cfg from your syslinux.cfg.bak backup) then reboot from HDD/SSD.

Only make this change if you are confident about making the change.

(2018-11-07, 18:39)Milhouse Wrote: [ -> ]

(2018-11-07, 18:19)jmerrilljr Wrote: [ -> ]I have no idea how to access my kernel command line. Also iperf can't connect to libreelec via TCP. I must be doing something wrong. Thanks for all your help.

TCP should be the default for iperf - you're telling it to test UDP by using the -u option. You're also limiting the bandwidth to 100Mb (which you'll probably never see with UDP even without kernel issues).

I'd suggest using the following iperf options on the client:

text:


iperf -c 10.0.1.55 -t 60 -i 10

On the server, you only need:

text:


iperf -s

To access your kernel command line, you need to edit /flash/syslinux.cfg.

To make the /flash partition writeable, you first need to run mount -o remount,rw /flash.

You can use vi or nano to edit /flash/syslinux.cfg.

Make a backup of your current file with:

text:


cp /flash/syslinux.cfg /flash/syslinux.cfg.bak

The kernel command line is the line that begins with APPEND so if your current file looks like:

text:


DEFAULT linux

PROMPT 0



LABEL linux

KERNEL /KERNEL

APPEND boot=LABEL=System disk=LABEL=Storage quiet

then you need to change /flash/sylinux.cfg to be:

text:


DEFAULT linux

PROMPT 0



LABEL linux

KERNEL /KERNEL

APPEND boot=LABEL=System disk=LABEL=Storage quiet log_buf_len=16M

Obviously, if you get this wrong and corrupt the contents of this file you may have a non-booting system which you can recover using LibreELEC booted from a memory stick (you'll need to boot into live live mode, enable ssh, login with ssh and your internal HDD/SSD will be available via the /media path - restore syslinux.cfg from your syslinux.cfg.bak backup) then reboot from HDD/SSD.

Only make this change if you are confident about making the change. 

 I can make the/flash partition writable but nano gives me a new file.

(2018-11-07, 19:00)jmerrilljr Wrote: [ -> ]

(2018-11-07, 18:39)Milhouse Wrote: [ -> ]

(2018-11-07, 18:19)jmerrilljr Wrote: [ -> ]I have no idea how to access my kernel command line. Also iperf can't connect to libreelec via TCP. I must be doing something wrong. Thanks for all your help.

TCP should be the default for iperf - you're telling it to test UDP by using the -u option. You're also limiting the bandwidth to 100Mb (which you'll probably never see with UDP even without kernel issues).

I'd suggest using the following iperf options on the client:

text:


iperf -c 10.0.1.55 -t 60 -i 10

On the server, you only need:

text:


iperf -s

To access your kernel command line, you need to edit /flash/syslinux.cfg.

To make the /flash partition writeable, you first need to run mount -o remount,rw /flash.

You can use vi or nano to edit /flash/syslinux.cfg.

Make a backup of your current file with:

text:


cp /flash/syslinux.cfg /flash/syslinux.cfg.bak

The kernel command line is the line that begins with APPEND so if your current file looks like:

text:


DEFAULT linux

PROMPT 0



LABEL linux

KERNEL /KERNEL

APPEND boot=LABEL=System disk=LABEL=Storage quiet

then you need to change /flash/sylinux.cfg to be:

text:


DEFAULT linux

PROMPT 0



LABEL linux

KERNEL /KERNEL

APPEND boot=LABEL=System disk=LABEL=Storage quiet log_buf_len=16M

Obviously, if you get this wrong and corrupt the contents of this file you may have a non-booting system which you can recover using LibreELEC booted from a memory stick (you'll need to boot into live live mode, enable ssh, login with ssh and your internal HDD/SSD will be available via the /media path - restore syslinux.cfg from your syslinux.cfg.bak backup) then reboot from HDD/SSD.

Only make this change if you are confident about making the change.   

 I can make the/flash partition writable but nano gives me a new file.  

Is this the correct iperf output?:

Last login: Wed Nov  7 12:15:18 on ttys001
Johns-iMac-2:~ johnmerrill$ iperf -c 10.0.1.55 -t 60 -i 10
connect failed: Connection refused
Johns-iMac-2:~ johnmerrill$ ssh [email protected]
[email protected]'s password: 
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (official): 8.2.5 (Generic.x86_64)
LibreELEC:~ # iperf -c 10.0.1.55 -t 60 -i 10
Connecting to host 10.0.1.55, port 5201
[  4] local 10.0.1.55 port 57746 connected to 10.0.1.55 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-10.00  sec  31.1 GBytes  26.7 Gbits/sec    0   3.25 MBytes       
[  4]  10.00-20.00  sec  31.6 GBytes  27.1 Gbits/sec    0   3.25 MBytes       
[  4]  20.00-30.00  sec  31.5 GBytes  27.0 Gbits/sec    0   3.25 MBytes       
[  4]  30.00-40.00  sec  31.7 GBytes  27.2 Gbits/sec    0   3.25 MBytes       
[  4]  40.00-50.00  sec  31.1 GBytes  26.7 Gbits/sec    0   3.25 MBytes       
[  4]  50.00-60.00  sec  31.2 GBytes  26.8 Gbits/sec    0   3.25 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec   188 GBytes  26.9 Gbits/sec    0             sender
[  4]   0.00-60.00  sec   188 GBytes  26.9 Gbits/sec                  receiver

iperf Done.
LibreELEC:~ #

@Milhouse, Will ProjectM addon be rebuilt? Looks like @spiff has updated it recently, https://forum.kodi.tv/showthread.php?tid...pid2786215.

(2018-11-07, 19:28)jmerrilljr Wrote: [ -> ]

(2018-11-07, 19:00)jmerrilljr Wrote: [ -> ]

(2018-11-07, 18:39)Milhouse Wrote: [ -> ]TCP should be the default for iperf - you're telling it to test UDP by using the -u option. You're also limiting the bandwidth to 100Mb (which you'll probably never see with UDP even without kernel issues).

I'd suggest using the following iperf options on the client:

text:


iperf -c 10.0.1.55 -t 60 -i 10

On the server, you only need:

text:


iperf -s

To access your kernel command line, you need to edit /flash/syslinux.cfg.

To make the /flash partition writeable, you first need to run mount -o remount,rw /flash.

You can use vi or nano to edit /flash/syslinux.cfg.

Make a backup of your current file with:

text:


cp /flash/syslinux.cfg /flash/syslinux.cfg.bak

The kernel command line is the line that begins with APPEND so if your current file looks like:

text:


DEFAULT linux

PROMPT 0



LABEL linux

KERNEL /KERNEL

APPEND boot=LABEL=System disk=LABEL=Storage quiet

then you need to change /flash/sylinux.cfg to be:

text:


DEFAULT linux

PROMPT 0



LABEL linux

KERNEL /KERNEL

APPEND boot=LABEL=System disk=LABEL=Storage quiet log_buf_len=16M

Obviously, if you get this wrong and corrupt the contents of this file you may have a non-booting system which you can recover using LibreELEC booted from a memory stick (you'll need to boot into live live mode, enable ssh, login with ssh and your internal HDD/SSD will be available via the /media path - restore syslinux.cfg from your syslinux.cfg.bak backup) then reboot from HDD/SSD.

Only make this change if you are confident about making the change.   

 I can make the/flash partition writable but nano gives me a new file.   

Is this the correct iperf output?:

Last login: Wed Nov  7 12:15:18 on ttys001
Johns-iMac-2:~ johnmerrill$ iperf -c 10.0.1.55 -t 60 -i 10
connect failed: Connection refused
Johns-iMac-2:~ johnmerrill$ ssh [email protected]
[email protected]'s password: 
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (official): 8.2.5 (Generic.x86_64)
LibreELEC:~ # iperf -c 10.0.1.55 -t 60 -i 10
Connecting to host 10.0.1.55, port 5201
[  4] local 10.0.1.55 port 57746 connected to 10.0.1.55 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-10.00  sec  31.1 GBytes  26.7 Gbits/sec    0   3.25 MBytes       
[  4]  10.00-20.00  sec  31.6 GBytes  27.1 Gbits/sec    0   3.25 MBytes       
[  4]  20.00-30.00  sec  31.5 GBytes  27.0 Gbits/sec    0   3.25 MBytes       
[  4]  30.00-40.00  sec  31.7 GBytes  27.2 Gbits/sec    0   3.25 MBytes       
[  4]  40.00-50.00  sec  31.1 GBytes  26.7 Gbits/sec    0   3.25 MBytes       
[  4]  50.00-60.00  sec  31.2 GBytes  26.8 Gbits/sec    0   3.25 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec   188 GBytes  26.9 Gbits/sec    0             sender
[  4]   0.00-60.00  sec   188 GBytes  26.9 Gbits/sec                  receiver

iperf Done.
LibreELEC:~ # 

 No. You host the server on the same computer you cannect to - that only tests Linux's local network which is fast :-)

(2018-11-08, 00:04)fritsch Wrote: [ -> ]

(2018-11-07, 19:28)jmerrilljr Wrote: [ -> ]

(2018-11-07, 19:00)jmerrilljr Wrote: [ -> ] I can make the/flash partition writable but nano gives me a new file.   

Is this the correct iperf output?:

Last login: Wed Nov  7 12:15:18 on ttys001
Johns-iMac-2:~ johnmerrill$ iperf -c 10.0.1.55 -t 60 -i 10
connect failed: Connection refused
Johns-iMac-2:~ johnmerrill$ ssh [email protected]
[email protected]'s password: 
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (official): 8.2.5 (Generic.x86_64)
LibreELEC:~ # iperf -c 10.0.1.55 -t 60 -i 10
Connecting to host 10.0.1.55, port 5201
[  4] local 10.0.1.55 port 57746 connected to 10.0.1.55 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-10.00  sec  31.1 GBytes  26.7 Gbits/sec    0   3.25 MBytes       
[  4]  10.00-20.00  sec  31.6 GBytes  27.1 Gbits/sec    0   3.25 MBytes       
[  4]  20.00-30.00  sec  31.5 GBytes  27.0 Gbits/sec    0   3.25 MBytes       
[  4]  30.00-40.00  sec  31.7 GBytes  27.2 Gbits/sec    0   3.25 MBytes       
[  4]  40.00-50.00  sec  31.1 GBytes  26.7 Gbits/sec    0   3.25 MBytes       
[  4]  50.00-60.00  sec  31.2 GBytes  26.8 Gbits/sec    0   3.25 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec   188 GBytes  26.9 Gbits/sec    0             sender
[  4]   0.00-60.00  sec   188 GBytes  26.9 Gbits/sec                  receiver

iperf Done.
LibreELEC:~ #   

 No. You host the server on the same computer you cannect to - that only tests Linux's local network which is fast :-)  

Then my iMac is the server and my chromebox is the client? I get this:

Last login: Wed Nov  7 17:32:44 on ttys001
Johns-iMac-2:~ johnmerrill$ iperf -s
bind failed: Address already in use
Johns-iMac-2:~ johnmerrill$

(2018-11-07, 19:28)jmerrilljr Wrote: [ -> ]Is this the correct iperf output?:

Yes, and 3.25MBytes/sec over a wired connection is really poor.

Edit: 3.25Mbytes is the congestion window and not relevant. The test results are bogus. I was clearly having a bad day yesterday...

(2018-11-07, 18:11)jmerrilljr Wrote: [ -> ]

(2018-11-07, 15:17)Milhouse Wrote: [ -> ]@jmerrilljr once more thing that might help: if you can test all of the 4.19-rc test builds (there were 8, rc1-rc8) it might help narrow down the range that includes the breaking commit. You can find links to the 4.19-rc test builds in PR2937. Start with 4.19-rc1 and if that doesn't have the problem then test the next release ie. 4.19-rc2. Post which release of 4.19-rc is the first with the problem. Thanks.

Also, can you describe what your PC is connected to - what type of cable (CAT5, CAT5e etc.), what type of switch (make/model/brand).

 Milhouse, I am running cat6 cable from a Belkin 5D5141-5v4 switch. All my tests have been run on the same 30 gig .mkv file. Other than that I am pretty much lost and overwhelmed. I will try the quoted 4.19 -rc test builds. 

#419RC1 has the problem. Log: http://ix.io/1rh0. Hope this helps.

(2018-11-08, 00:04)fritsch Wrote: [ -> ] No. You host the server on the same computer you cannect to - that only tests Linux's local network which is fast :-)

Hmm yeah. The Mac should be running the iperf server, and I assumed the server was 10.0.1.55. The LE client should be running iperf -c ip-address-of-Mac -t 60 -i10.

New LibreELEC.tv Leia build #1107: Generic
(Supercedes previous build)

SHA256 Checksum: 4edc4e1fa42a9a3fede9e25c13addbb5cbf02007644ed1955e4687699f3b3fdf (Generic)

text:
# uname -a

Linux NUC 4.19.1 #1 SMP Wed Nov 7 21:03:52 GMT 2018 x86_64 GNU/Linux



# lsb_release

LibreELEC (Milhouse): devel-20181107210230-#1107-g1a60beb [Build #1107]



# Kodi version

(18.0-RC1 Git:5a42446). Platform: Linux x86 64-bit

Based on tip of LibreELEC.tv master (1a60beb, changelog) and tip of XBMC master (5a42446, changelog) with the following modifications:

• Includes latest kodi-platform master (e8574b8)
  
• Includes latest libcec master (009d54b, ahead +4)
  
• Includes latest libnfs master (6dfc87d, ahead +10)
  
• Includes latest p8-platform master (1eb12b1, ahead +1)
  
• Includes latest addons: inputstream.adaptive (d1bb1eb, +3), inputstream.rtmp (ce7f559), peripheral.joystick (2008fdc, +1), peripheral.xarcade (f09a0e7, +1), pvr.argustv (609a2e7, +2), pvr.demo (964686d), pvr.dvblink (47cbff0, +2), pvr.dvbviewer (a9b204e, +8), pvr.filmon (f736ab4, +2), pvr.hdhomerun (a9d7309, +1), pvr.hts (f4ea60f, +2), pvr.iptvsimple (90a8d6f, +1), pvr.mediaportal.tvserver (e4a9dae, +2), pvr.mythtv (ca6620b, +2), pvr.nextpvr (7e36106, +2), pvr.njoy (4467cac, +1), pvr.octonet (203f800), pvr.pctv (e28a90f, +2), pvr.stalker (a99ad5e, +2), pvr.teleboy (484db31), pvr.vbox (6ed2f63, +2), pvr.vdr.vnsi (6bbdb78), pvr.vuplus (d77458b, +2), pvr.wmc (e00c895, +2), pvr.zattoo (41268ee), vfs.libarchive (6d39012), vfs.sftp (6749200)
  
• Include [env] compare (perma): TESTING: increase timeout to ensure OS is able to create core dump/crash log
  
• Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
  
• Include [env] patch: kodi: use upstream repo for Milhouse RPi builds
  
• Include [env] patch: kodi: remove annoying, excessively repetitive addon logging
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] patch: rev hack for kodi
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, peripheral.joystick/xarcade, other)
  
• Include [env] PR:3077 (perma): kodi: use project specific cputemp scripts for all projects
  
• Include [env] PR:3084 (perma): linux (RPi/Generic): update to linux-4.19.1
  
• Include [env] PR:3089 (perma): iptables: update to iptables-1.8.1
  

Build Highlights:

1. Reintroduce crazycat: update to 2018-11-04
   

Build Details:

1. LibreELEC.tv:
   • HACK: fix audio for WP1 (PR:3080, 2 commits, 2 files changed)
     
   • librespot: update to 96557b4 (PR:3086, 2 commits, 6 files changed)
     
   • WeTek_Core/WeTek_Play: fixup libcec support (PR:3091, 1 commit, 2 files changed)
     
   • crazycat: update to 2018-11-04 (PR:3088, 3 commits, 4 files changed)
     
2. XBMC:
   • [GUI] reinitialize addon path after returning with .. directory item (PR:14803, 1 commit, 1 file changed)
     
3. libcec:
   • Modifies NSIS script to call EventGhost to install the plugin (PR:375, 2 commits, 9 files changed)
     
   • fixed: don't poll samsung TVs. issue #424 (f87328d)
     
   • fixed: creating windows installer (009d54b)
     
4. pvr.dvbviewer:
   • Add file flags to StreamReader as suggested by FernetMenta (c2e97a1)
     
   • Move more classes to dvbviewer namespace (f98999f)
     
   • Add support for (on-the-fly) transcoding of recordings (0025954)
     
   • appveyor: run apt-get update (8dd1ddb)
     
   • fix 32 bits time_t (e801485)
     
   • Bump version to 3.7.5 (a9b204e)
     
5. Additional commits/pull requests/changes not yet merged upstream:
   • Updated: [env] PR:3089 (perma): iptables: update to iptables-1.8.1
     

(2018-11-08, 01:07)Milhouse Wrote: [ -> ]

(2018-11-08, 00:04)fritsch Wrote: [ -> ] No. You host the server on the same computer you cannect to - that only tests Linux's local network which is fast :-)

Hmm yeah. The Mac should be running the iperf server, and I assumed the server was 10.0.1.55. The LE client should be running iperf -c ip-address-of-Mac -t 60 -i10.  

 Brew installed an old version of iperf on my Mac so i need to install iperf3 to be compatible with libre. 



LibreELEC (official): 8.2.5 (Generic.x86_64)
LibreELEC:~ # iperf -c 10.0.1.62 -t 60 -i 10
Connecting to host 10.0.1.62, port 5201
[  4] local 10.0.1.55 port 55330 connected to 10.0.1.62 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-10.00  sec   112 MBytes  94.2 Mbits/sec    0   91.9 KBytes       
[  4]  10.00-20.00  sec   112 MBytes  93.9 Mbits/sec    0   91.9 KBytes       
[  4]  20.00-30.00  sec   112 MBytes  93.9 Mbits/sec    0   91.9 KBytes       
[  4]  30.00-40.00  sec   112 MBytes  94.1 Mbits/sec    0    116 KBytes       
[  4]  40.00-50.00  sec   112 MBytes  93.9 Mbits/sec    0    116 KBytes       
[  4]  50.00-60.00  sec   112 MBytes  93.9 Mbits/sec    0    116 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec   672 MBytes  94.0 Mbits/sec    0             sender
[  4]   0.00-60.00  sec   672 MBytes  93.9 Mbits/sec                  receiver

iperf Done.
LibreELEC:~ #

Whew!!!!