Vero 4K + network speed major disappointment

Wuffzack · 19 September 2018 18:44

I have received my Vero 4K+. Coming from a Minix U9 (Amlogic S912) with LibreELEC the Vero 4K+ network speed is a major disappointment.

Yes, the ethernet switch, where the box is connected, says the link speed is 1GBit/s.
But the performance is more in the 100 MBit/s range. Here are some iperf3 results:

root@osmckino:~# iperf3 -c whs.box
Connecting to host whs.box, port 5201
[  4] local 10.1.0.41 port 33776 connected to 10.1.0.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  9.24 MBytes  77.5 Mbits/sec   65   4.24 KBytes
[  4]   1.00-2.00   sec  8.34 MBytes  70.0 Mbits/sec   55   8.48 KBytes
[  4]   2.00-3.00   sec  12.8 MBytes   107 Mbits/sec   68   7.07 KBytes
[  4]   3.00-4.00   sec  11.6 MBytes  97.5 Mbits/sec   63   7.07 KBytes
[  4]   4.00-5.00   sec  13.0 MBytes   109 Mbits/sec   63   7.07 KBytes
[  4]   5.00-6.00   sec  14.3 MBytes   120 Mbits/sec   66   14.1 KBytes
[  4]   6.00-7.00   sec  12.6 MBytes   106 Mbits/sec   71   7.07 KBytes
[  4]   7.00-8.00   sec  10.3 MBytes  86.2 Mbits/sec   72   4.24 KBytes
[  4]   8.00-9.00   sec  9.00 MBytes  75.4 Mbits/sec   89   4.24 KBytes
[  4]   9.00-10.00  sec  8.80 MBytes  73.8 Mbits/sec   85   7.07 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   110 MBytes  92.2 Mbits/sec  697             sender
[  4]   0.00-10.00  sec   110 MBytes  92.1 Mbits/sec                  receiver

I have actually skipped the Vero 4K because of the 100 MBit/s network speed, and thought the 4K+ would be perfect. But high demanding HFR 4K streams push it to the limit. It stutters like hell. The S912 box with LibreElec and working 1GBit/s network plays everythig fine.

The question is - why is the network so slow on my Vero 4K+?
Is there anything I can change to increase performance?

Moderator note: I’ve reformatted your iperf3 figures to show more clearly the large number of retries.

Tom_Doyle · 19 September 2018 19:11

Hi,

How/where is whs.box connected to the network.

Ideally it needs to be connected directly to your router on a gigabit connection.

Thanks Tom.

sam_nazarko · 19 September 2018 19:28

Sorry to hear you’ve experienced a problem with the network speed.

This isn’t expected. Let’s get this fixed.

Can you try on a different switch or environment as a test?

Cheers

Sam

Smurphy · 19 September 2018 20:39

What Box do you have?
very often, the Box you get from your ISP is a “cheapo something” that is quite slow.
Also - the overall speed of the communication between 2 devices is determined by the slowest device in the path of the data flow. Eventually you could make a small drawing on how your network is setup.
You can also connect the Vero straight to the NAS (back to back) to see if the NAS is the bottle-neck, or your Box (You will have to manually configure the network interfaces in that case though).

Fact is - on the below tests I did, I have 2 Kids streaming data from the NAS while I do the test (Watching Movies with Kodi on their devices). The results would be better if I redo the tests with no one watching something …
So - the Vero 4K+ is really fast (Ethernet side). I bet your equipment is bad.

My Equipment here is:

NAS: HP Microserver gen8, 16GB Ram, Xeon® CPU E3-1220L V2, 16TB Raid5 Array
Switch: Zyxel SG1900-16 16 Port Managed Gigabit Switch.
All cables through ethernet using Category 6 (Cat6) double shielded cables.

Here is the Data of my connection:
Vero2k to NAS:
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 4] local 10.0.2.250 port 5001 connected with 10.0.3.242 port 51056
[ ID] Interval       Transfer     Bandwidth
[ 4] 0.0-10.0 sec 1.02 GBytes   878 Mbits/sec
[ 5] local 10.0.2.250 port 5001 connected with 10.0.3.242 port 51057
[ 5] 0.0-10.0 sec 1023 MBytes   858 Mbits/sec

Other way around: NAS → Vero4k
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[ 4] local 10.0.3.242 port 5001 connected with 10.0.2.250 port 24044
[ ID] Interval       Transfer     Bandwidth
[ 4] 0.0-10.1 sec 1009 MBytes   841 Mbits/sec
[ 5] local 10.0.3.242 port 5001 connected with 10.0.2.250 port 24224
[ 5] 0.0-10.0 sec 1.01 GBytes   867 Mbits/sec

Wuffzack · 19 September 2018 22:14

whs.box is connected with 4 Gigabit cables (link aggregation) to a TP-Link T1600G-52TS smart managed switch.
The Vero 4K is connected to the same switch.
Here is an iperf3 result from a PC connected to the same TP-Link switch:
C:\AutoStart>iperf3 -c whs.box
Connecting to host whs.box, port 5201
[ 4] local 10.1.0.12 port 52478 connected to 10.1.0.10 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 113 MBytes 950 Mbits/sec
[ 4] 1.00-2.00 sec 113 MBytes 949 Mbits/sec
[ 4] 2.00-3.00 sec 113 MBytes 949 Mbits/sec
[ 4] 3.00-4.00 sec 113 MBytes 948 Mbits/sec
[ 4] 4.00-5.00 sec 112 MBytes 942 Mbits/sec
[ 4] 5.00-6.00 sec 113 MBytes 949 Mbits/sec
[ 4] 6.00-7.00 sec 113 MBytes 949 Mbits/sec
[ 4] 7.00-8.00 sec 112 MBytes 942 Mbits/sec
[ 4] 8.00-9.00 sec 113 MBytes 948 Mbits/sec
[ 4] 9.00-10.00 sec 113 MBytes 950 Mbits/sec

[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 1.10 GBytes 948 Mbits/sec sender
[ 4] 0.00-10.00 sec 1.10 GBytes 948 Mbits/sec receiver

iperf Done.

Wuffzack · 19 September 2018 22:23

Hi Sam,
I tried a D-Link switch between the Vero 4K+ and the TP-Link switch, in case the Vero doesn’t like the TP-Link. No change.

The working S912 box is connected with the same cable and to the same switches, no problems. Same for Nvidia Shields with Kodi, also great iperf3 results.
As an additional note, I also have a cheap chinese Amlogic S905X box with LibreELEC, the case looks a lot like a Vero.
Although only 100 mbit/s, it somehow feels “snappier” on network operations than the Vero 4K+.
There must be something special in my Network, the Vero 4K+ somehow does not like at all.

Wuffzack · 19 September 2018 22:37

Sam,

I just checked the port settings in the TP-Link switch. They are still at default settings:
Speed: auto
Duplex: auto
Flow control: disable
Jumbo: disable

Any suggestion for changes?

WilliamG · 19 September 2018 22:53

For the record, I’m going through numerous switches and access points around my house, and this is the results from a 2014 iMac to the Vero 4K+, with Cat5e throughout.

osmc@verob:~$ iperf3 -c 192.168.0.6 -R
Connecting to host 192.168.0.6, port 5201
Reverse mode, remote host 192.168.0.6 is sending
[  4] local 192.168.0.62 port 44315 connected to 192.168.0.6 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   109 MBytes   916 Mbits/sec                  
[  4]   1.00-2.00   sec   112 MBytes   939 Mbits/sec                  
[  4]   2.00-3.00   sec   112 MBytes   939 Mbits/sec                  
[  4]   3.00-4.00   sec   110 MBytes   923 Mbits/sec                  
[  4]   4.00-5.00   sec   111 MBytes   935 Mbits/sec                  
[  4]   5.00-6.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   6.00-7.00   sec   112 MBytes   939 Mbits/sec                  
[  4]   7.00-8.00   sec   112 MBytes   941 Mbits/sec                  
[  4]   8.00-9.00   sec   112 MBytes   939 Mbits/sec                  
[  4]   9.00-10.00  sec   111 MBytes   932 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.00  sec  1.09 GBytes   935 Mbits/sec                  sender
[  4]   0.00-10.00  sec  1.09 GBytes   935 Mbits/sec                  receiver

And from my 2014 Mac mini:

osmc@verob:~$ iperf3 -c 192.168.0.5 -R
Connecting to host 192.168.0.5, port 5201
Reverse mode, remote host 192.168.0.5 is sending
[  4] local 192.168.0.62 port 42141 connected to 192.168.0.5 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   112 MBytes   935 Mbits/sec                  
[  4]   1.00-2.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   2.00-3.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   3.00-4.00   sec   112 MBytes   939 Mbits/sec                  
[  4]   4.00-5.00   sec   112 MBytes   941 Mbits/sec                  
[  4]   5.00-6.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   6.00-7.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   7.00-8.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   8.00-9.00   sec   112 MBytes   940 Mbits/sec                  
[  4]   9.00-10.00  sec   112 MBytes   940 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.00  sec  1.09 GBytes   940 Mbits/sec                  sender
[  4]   0.00-10.00  sec  1.09 GBytes   940 Mbits/sec                  receiver

Hardware switches/access points:

Apple Macs connected to…
Trendnet TEG-S80G - I’m going through several of these connected to…
Asus RT-AC68U - which in turn is connected to…
Zyxel C1100Z - which in turn is connected to…
Another Trendet TEG-S80G - which is connected to…

OSMC Vero 4K+ !

fzinken · 20 September 2018 00:11

Suggest to check what is negotiated. For that easiest is to install ethtool via sudo apt-get install ethtool
Than run ethtool eth0

Wuffzack · 20 September 2018 01:24

root@osmckino:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: ug
        Wake-on: d
        Current message level: 0x0000003d (61)
                               drv link timer ifdown ifup
        Link detected: yes

Wuffzack · 20 September 2018 01:39

Just tried an USB Gigabit Ethernet adapter. Playback is smooth, where internal port stuttered. iPerf3 results much better (not as good as real Gigabit, but good enough), no retries. Same switch, same cables:

root@osmckino:~# iperf3 -c whs3
Connecting to host whs3, port 5201
[  4] local 10.1.0.11 port 58412 connected to 10.1.0.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  21.7 MBytes   182 Mbits/sec    0    214 KBytes
[  4]   1.00-2.00   sec  22.8 MBytes   192 Mbits/sec    0    214 KBytes
[  4]   2.00-3.00   sec  22.1 MBytes   185 Mbits/sec    0    214 KBytes
[  4]   3.00-4.00   sec  22.1 MBytes   185 Mbits/sec    0    214 KBytes
[  4]   4.00-5.00   sec  22.0 MBytes   185 Mbits/sec    0    214 KBytes
[  4]   5.00-6.00   sec  21.7 MBytes   182 Mbits/sec    0    214 KBytes
[  4]   6.00-7.00   sec  22.1 MBytes   185 Mbits/sec    0    214 KBytes
[  4]   7.00-8.00   sec  22.1 MBytes   185 Mbits/sec    0    214 KBytes
[  4]   8.00-9.00   sec  22.1 MBytes   185 Mbits/sec    0    214 KBytes
[  4]   9.00-10.00  sec  22.1 MBytes   185 Mbits/sec    0    214 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   221 MBytes   185 Mbits/sec    0             sender
[  4]   0.00-10.00  sec   220 MBytes   185 Mbits/sec                  receiver

iperf Done.

However, the plan was not to use an USB Ethernet adapter…

fzinken · 20 September 2018 01:44

Just wondered that this time you used whs3 instead of whs.box but assuming their are the same target.
Only suggestions I have right now is to try enable/disable flow control on the port to see any differences.

Also a iperf try from Vero towards e.g. your Notebook or any other device would be interesting (while I would assume the same bad results).

Wuffzack · 20 September 2018 10:28

Yes, both resolve to the same IP address.

Tried it. Makes no improvement.

Very bad results. This is iperf server running on Vero:

 D:\NB\iPerf>iperf3 -c 10.1.0.41
Connecting to host 10.1.0.41, port 5201
[  4] local 10.1.0.14 port 60851 connected to 10.1.0.41 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  2.62 MBytes  22.0 Mbits/sec
[  4]   1.00-2.00   sec  4.12 MBytes  34.6 Mbits/sec
[  4]   2.00-3.00   sec  4.62 MBytes  38.7 Mbits/sec
[  4]   3.00-4.00   sec  3.88 MBytes  32.5 Mbits/sec
[  4]   4.00-5.00   sec  11.8 MBytes  98.5 Mbits/sec
[  4]   5.00-6.00   sec  1.62 MBytes  13.6 Mbits/sec
[  4]   6.00-7.00   sec  4.75 MBytes  39.9 Mbits/sec
[  4]   7.00-8.00   sec  1.25 MBytes  10.5 Mbits/sec
[  4]   8.00-9.00   sec  1.25 MBytes  10.5 Mbits/sec
[  4]   9.00-10.00  sec  4.75 MBytes  39.8 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.00  sec  40.6 MBytes  34.1 Mbits/sec                  sender
[  4]   0.00-10.00  sec  40.5 MBytes  34.0 Mbits/sec                  receiver

iperf Done.

fzinken · 20 September 2018 10:33

Well doesn’t look good. So either a issue on the Vero hardware or a incompatibility with the switches (would be strange for two different brands).
Just to ensure one more topic I assume you have disabled the wireless interface of the Vero?

Also ethtool -S eth0 output would be interisting

Wuffzack · 20 September 2018 10:36

Yes, Wireless is disabled.

fzinken · 20 September 2018 10:39

Check the ethtool -s eth0 also for the record can you give exact model of the two switches you tested. I saw TP-Link and D-Link but not the models.

Wuffzack · 20 September 2018 10:41

Just forced the switch to 100 mbit/s. Results are much better (no retries):

root@osmckino:~# iperf3 -c whs3
Connecting to host whs3, port 5201
[  4] local 10.1.0.41 port 50905 connected to 10.1.0.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  12.6 MBytes   105 Mbits/sec    0    242 KBytes
[  4]   1.00-2.00   sec  11.5 MBytes  96.1 Mbits/sec    0    272 KBytes
[  4]   2.00-3.00   sec  11.2 MBytes  93.8 Mbits/sec    0    272 KBytes
[  4]   3.00-4.00   sec  11.2 MBytes  94.3 Mbits/sec    0    273 KBytes
[  4]   4.00-5.00   sec  11.2 MBytes  93.8 Mbits/sec    0    273 KBytes
[  4]   5.00-6.00   sec  11.3 MBytes  94.7 Mbits/sec    0    273 KBytes
[  4]   6.00-7.00   sec  11.2 MBytes  93.6 Mbits/sec    0    273 KBytes
[  4]   7.00-8.00   sec  11.2 MBytes  94.1 Mbits/sec    0    273 KBytes
[  4]   8.00-9.00   sec  11.2 MBytes  94.3 Mbits/sec    0    273 KBytes
[  4]   9.00-10.00  sec  11.2 MBytes  94.3 Mbits/sec    0    273 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   114 MBytes  95.4 Mbits/sec    0             sender
[  4]   0.00-10.00  sec   112 MBytes  94.2 Mbits/sec                  receiver

iperf Done.

Wuffzack · 20 September 2018 10:47

TP-Link is a JetStream 48-Port Gigabit Smart Switch T1600G-52TS. The D-Link is an older 24 port unmanaged Gigabit switch, don’t know the exact type.

root@osmckino:~# ethtool -S eth0
NIC statistics:
     mmc_tx_octetcount_gb: 0
     mmc_tx_framecount_gb: 0
     mmc_tx_broadcastframe_g: 0
     mmc_tx_multicastframe_g: 0
     mmc_tx_64_octets_gb: 0
     mmc_tx_65_to_127_octets_gb: 0
     mmc_tx_128_to_255_octets_gb: 0
     mmc_tx_256_to_511_octets_gb: 0
     mmc_tx_512_to_1023_octets_gb: 0
     mmc_tx_1024_to_max_octets_gb: 0
     mmc_tx_unicast_gb: 0
     mmc_tx_multicast_gb: 0
     mmc_tx_broadcast_gb: 0
     mmc_tx_underflow_error: 0
     mmc_tx_singlecol_g: 0
     mmc_tx_multicol_g: 0
     mmc_tx_deferred: 0
     mmc_tx_latecol: 0
     mmc_tx_exesscol: 0
     mmc_tx_carrier_error: 0
     mmc_tx_octetcount_g: 0
     mmc_tx_framecount_g: 0
     mmc_tx_excessdef: 0
     mmc_tx_pause_frame: 0
     mmc_tx_vlan_frame_g: 0
     mmc_rx_framecount_gb: 80866
     mmc_rx_octetcount_gb: 33317047
     mmc_rx_octetcount_g: 33317047
     mmc_rx_broadcastframe_g: 595
     mmc_rx_multicastframe_g: 1389
     mmc_rx_crc_errror: 0
     mmc_rx_align_error: 0
     mmc_rx_run_error: 0
     mmc_rx_jabber_error: 0
     mmc_rx_undersize_g: 0
     mmc_rx_oversize_g: 0
     mmc_rx_64_octets_gb: 693
     mmc_rx_65_to_127_octets_gb: 57198
     mmc_rx_128_to_255_octets_gb: 1647
     mmc_rx_256_to_511_octets_gb: 1600
     mmc_rx_512_to_1023_octets_gb: 1728
     mmc_rx_1024_to_max_octets_gb: 18000
     mmc_rx_unicast_g: 78882
     mmc_rx_length_error: 0
     mmc_rx_autofrangetype: 0
     mmc_rx_pause_frames: 0
     mmc_rx_fifo_overflow: 0
     mmc_rx_vlan_frames_gb: 0
     mmc_rx_watchdog_error: 0
     mmc_rx_ipc_intr_mask: 2147385342
     mmc_rx_ipc_intr: 0
     mmc_rx_ipv4_gd: 80248
     mmc_rx_ipv4_hderr: 0
     mmc_rx_ipv4_nopay: 6
     mmc_rx_ipv4_frag: 0
     mmc_rx_ipv4_udsbl: 0
     mmc_rx_ipv4_gd_octets: 31826227
     mmc_rx_ipv4_hderr_octets: 0
     mmc_rx_ipv4_nopay_octets: 276
     mmc_rx_ipv4_frag_octets: 0
     mmc_rx_ipv4_udsbl_octets: 0
     mmc_rx_ipv6_gd_octets: 0
     mmc_rx_ipv6_hderr_octets: 0
     mmc_rx_ipv6_nopay_octets: 0
     mmc_rx_ipv6_gd: 0
     mmc_rx_ipv6_hderr: 0
     mmc_rx_ipv6_nopay: 0
     mmc_rx_udp_gd: 2637
     mmc_rx_udp_err: 0
     mmc_rx_tcp_gd: 77611
     mmc_rx_tcp_err: 0
     mmc_rx_icmp_gd: 0
     mmc_rx_icmp_err: 0
     mmc_rx_udp_gd_octets: 596592
     mmc_rx_udp_err_octets: 0
     mmc_rx_tcp_gd_octets: 29624675
     mmc_rx_tcp_err_octets: 0
     mmc_rx_icmp_gd_octets: 0
     mmc_rx_icmp_err_octets: 0
     tx_underflow: 0
     tx_carrier: 0
     tx_losscarrier: 0
     vlan_tag: 0
     tx_deferred: 0
     tx_vlan: 0
     tx_jabber: 0
     tx_frame_flushed: 0
     tx_payload_error: 0
     tx_ip_header_error: 0
     rx_desc: 0
     sa_filter_fail: 0
     overflow_error: 0
     ipc_csum_error: 0
     rx_collision: 0
     rx_crc: 0
     dribbling_bit: 0
     rx_length: 0
     rx_mii: 0
     rx_multicast: 0
     rx_gmac_overflow: 0
     rx_watchdog: 0
     da_rx_filter_fail: 0
     sa_rx_filter_fail: 0
     rx_missed_cntr: 0
     rx_overflow_cntr: 0
     rx_vlan: 0
     tx_undeflow_irq: 0
     tx_process_stopped_irq: 0
     tx_jabber_irq: 0
     rx_overflow_irq: 0
     rx_buf_unav_irq: 0
     rx_process_stopped_irq: 0
     rx_watchdog_irq: 0
     tx_early_irq: 0
     fatal_bus_error_irq: 0
     rx_early_irq: 1905
     threshold: 64
     tx_pkt_n: 120965
     rx_pkt_n: 80866
     normal_irq_n: 40505
     rx_normal_irq_n: 37171
     napi_poll: 40502
     tx_normal_irq_n: 3411
     tx_clean: 41580
     tx_reset_ic_bit: 117555
     irq_receive_pmt_irq_n: 0
     mmc_tx_irq_n: 0
     mmc_rx_irq_n: 0
     mmc_rx_csum_offload_irq_n: 0
     irq_tx_path_in_lpi_mode_n: 0
     irq_tx_path_exit_lpi_mode_n: 0
     irq_rx_path_in_lpi_mode_n: 0
     irq_rx_path_exit_lpi_mode_n: 0
     phy_eee_wakeup_error_n: 0
     ip_hdr_err: 0
     ip_payload_err: 0
     ip_csum_bypassed: 0
     ipv4_pkt_rcvd: 0
     ipv6_pkt_rcvd: 0
     rx_msg_type_ext_no_ptp: 0
     rx_msg_type_sync: 0
     rx_msg_type_follow_up: 0
     rx_msg_type_delay_req: 0
     rx_msg_type_delay_resp: 0
     rx_msg_type_pdelay_req: 0
     rx_msg_type_pdelay_resp: 0
     rx_msg_type_pdelay_follow_up: 0
     ptp_frame_type: 0
     ptp_ver: 0
     timestamp_dropped: 0
     av_pkt_rcvd: 0
     av_tagged_pkt_rcvd: 0
     vlan_tag_priority_val: 0
     l3_filter_match: 0
     l4_filter_match: 0
     l3_l4_filter_no_match: 0
     irq_pcs_ane_n: 0
     irq_pcs_link_n: 0
     irq_rgmii_n: 7

Smurphy · 20 September 2018 10:53

Looks good. Same here, and my vero has no speed issues.
Waiting for a pcap from a different user/thread tonight (@pascal) - will see if something is visible in there.
If you know how to provide a packet capture on the communication between Vero and NAS - please provide one. Would say - at least 100MB - so we can see complete sessions etc. and analyze over large chunks.

Let us know where to download it.

fzinken · 20 September 2018 11:30

Could you (only when you have time) check if both send and receive are OK when you force 100Mbit?
Also please check if it works if you not force it on the switch but from the Vero with ethtool -s eth0 speed 100 duplex full autoneg off