Kodi Community Forum

Kodi Community Forum > Support > General Support > Raspberry Pi > Lag in the LAN when Kodi (RPi3) is connected
Full Version: Lag in the LAN when Kodi (RPi3) is connected
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2

Ugaitz

2018-10-08, 00:01
hi,

I have some lag (1-4 sec) on the LAN when my RPi3 is connected in the LAN. The RPi3 is connected with ethernet and holds libreelec 8.2.5 installed.

No matters if kodi is in the main menu without playing video, the lags continues, aproximately every minute.

I leave a ping report from my PC while RPI3 is connected:

Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=1611ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=13ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=13ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121

and 1 minute later: 

Respuesta desde 8.8.8.8: bytes=32 tiempo=15ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=2172ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=15ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=14ms TTL=121
Respuesta desde 8.8.8.8: bytes=32 tiempo=15ms TTL=121

There is something that can I do to fix it?

DarrenHill

2018-10-08, 06:46
That would be much better raised at the libreelec forums directly (http://forum.libreelec.tv/) as the networking stuff is nothing to do with Kodi directly, but is handled by the LibreElec "just enough OS for Kodi" beneath it.

It's more likely to be a general network issue than anything, but it's not Kodi itself.

Ugaitz

2018-10-08, 16:39
I come from libreelec forum xDD

they say that is RPi3 ethernet, because its bad implemented, but i dont know, because everyone who has RPI3 has lags?

thank you!

graysky

2018-10-08, 16:55
On Arch ARM (RPi3) it behaves as expected.  Not sure if pinging a DNS indefinitely is the best measure of lag...
Code:
% uname -r
4.14.73-1-ARCH

% ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=23.5 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=23.3 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=119 time=23.10 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=119 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=119 time=24.2 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=119 time=24.2 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=119 time=24.1 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=119 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=119 time=23.6 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=119 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=119 time=23.1 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=119 time=24.1 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=119 time=23.2 ms

Ugaitz

2018-10-08, 17:02
Some advice to measure lags?

I can ping any ip, I will have same lags. But, if I disconnect the RPi3 the lags gone.

I ping it in my Win 10 PC

black_eagle

2018-10-08, 17:14
You aren't measuring latency in your lan like that, you are measuring the latency between the Pi and google's DNS server, across the internet.

Test pinging google and then pinging the local DNS server on my Lan from the same Pi.

Code:
Kitchen:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=119 time=28.667 ms
64 bytes from 8.8.8.8: seq=1 ttl=119 time=25.094 ms
64 bytes from 8.8.8.8: seq=2 ttl=119 time=25.568 ms
64 bytes from 8.8.8.8: seq=3 ttl=119 time=25.042 ms
64 bytes from 8.8.8.8: seq=4 ttl=119 time=25.134 ms
64 bytes from 8.8.8.8: seq=5 ttl=119 time=25.375 ms
64 bytes from 8.8.8.8: seq=6 ttl=119 time=25.208 ms
64 bytes from 8.8.8.8: seq=7 ttl=119 time=25.117 ms
^C
--- 8.8.8.8 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 25.042/25.650/28.667 ms
Kitchen:~ # ping sapphire
PING sapphire (192.168.1.125): 56 data bytes
64 bytes from 192.168.1.125: seq=0 ttl=64 time=0.818 ms
64 bytes from 192.168.1.125: seq=1 ttl=64 time=0.987 ms
64 bytes from 192.168.1.125: seq=2 ttl=64 time=0.998 ms
64 bytes from 192.168.1.125: seq=3 ttl=64 time=1.037 ms
^C
--- sapphire ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.818/0.960/1.037 ms

Do traceroute 8.8.8.8 from your Pi and you will see all the hops.

Milhouse

2018-10-10, 16:55
Disable all add-ons during your test - best to start with a clean .kodi folder, as maybe you have a badly written add-on installed that is waking up every 60 seconds or so and briefly consuming all your RPi3's limited network bandwidth, which then causes the lag for any other process that also attempts to use the same network at the same time.

Ugaitz

2018-10-10, 17:21
I have some bussy days, but i wil try it.

hat "RPi3's limited network bandwidth" can consume all routers bandwith? Because I said that the RPi3 produces the lag in all the LAN, moreover, the pings which i post it earlier was taken in my Win 10 PC while the RPi3 was connected.

I think that I didnt explain properly Wink.

Thank you all.

Milhouse

2018-10-10, 18:07
(2018-10-10, 17:21)Ugaitz Wrote: [ -> ]that the RPi3 produces the lag in all the LAN
In that case maybe the problem is your router - reboot it. Try a different router. Start eliminating the variables. It seems fairly unlikely that the RPi3 would impact the network performance of another device (which is presumably connected with 1Gbps ethernet) unless you've got a really poor router, or slow internet connection.

How certain are you that the RPi3 is the cause of the lag - are you saying you have no lag when the RPi3 is not active?

How fast is your internet connection, because that's all you are testing by pinging 8.8.8.8 - perhaps, again, you have an add-on running on the RPi3 that is periodically downloading data from the internet and consuming all your internet bandwidth which increases the ping time of other devices to internet IP addresses. The lag isn't in your LAN, as you're not testing that - the lag is in your WAN.

Ugaitz

2018-10-16, 14:39
I make a typical speed test in the browser and it say that i have 207.1 Mbps downloading and 35.63 Mbps uploading. 

And I have clean intall of libreelec (without addons, just make the SD and plug in) and I have the same lag issue. I will make some test and I will tell you what I discover.

Thank you!

Ugaitz

2018-10-17, 15:08
Ok this is the report:
  • I look that I have lags pinging to the router. Router dont reply to pings when this lags happens.
  • The lags are only when Kodi is running. (I install Raspian and no lags until I execute Kodi)
  • The lag only happens in Ethernet, not with Wifi.
  • I log the moment of the lag in the RPi, this report is when Kodi starts, because I always have lag when Kodi starts running:
    • The ping report:

      64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1.07 ms
      64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2749 ms
      64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=1727 ms
      64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=698 ms
      64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=1.13 ms
    • The Wireshark report in this period:

      54 24.756719588 192.168.0.13 → 192.168.0.1  ICMP 98 Echo (ping) request id=0x042e, seq=15/3840, ttl=64
        55 24.757742815  192.168.0.1 → 192.168.0.13 ICMP 98 Echo (ping) reply    id=0x042e, seq=15/3840, ttl=64 (request in 54)
        56 25.500387452 192.168.0.13 → 239.255.255.250 SSDP 215 M-SEARCH * HTTP/1.1
        57 25.500509170 192.168.0.13 → 239.255.255.250 SSDP 215 M-SEARCH * HTTP/1.1
        58 25.510033781 192.168.0.13 → 239.255.255.250 IGMPv2 46 Membership Report group 239.255.255.250
        59 25.573733199 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 244 Standard query 0x0000 ANY Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local, "QM" question ANY Kodi (raspberrypi)._xbmc-events._udp.local, "QM" question SRV 0 0 9777 raspberrypi.local TXT SRV 0 0 9090 raspberrypi.local TXT
        60 25.573945803 192.168.0.13 → 224.0.0.251  MDNS 224 Standard query 0x0000 ANY Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local, "QM" question ANY Kodi (raspberrypi)._xbmc-events._udp.local, "QM" question SRV 0 0 9777 raspberrypi.local TXT SRV 0 0 9090 raspberrypi.local TXT
        61 25.757974445 192.168.0.13 → 192.168.0.1  ICMP 98 Echo (ping) request id=0x042e, seq=16/4096, ttl=64
        62 25.824524847 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 244 Standard query 0x0000 ANY Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local, "QM" question ANY Kodi (raspberrypi)._xbmc-events._udp.local, "QM" question SRV 0 0 9777 raspberrypi.local TXT SRV 0 0 9090 raspberrypi.local TXT
        63 25.824729846 192.168.0.13 → 224.0.0.251  MDNS 224 Standard query 0x0000 ANY Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local, "QM" question ANY Kodi (raspberrypi)._xbmc-events._udp.local, "QM" question SRV 0 0 9777 raspberrypi.local TXT SRV 0 0 9090 raspberrypi.local TXT
        64 26.075174411 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 244 Standard query 0x0000 ANY Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local, "QM" question ANY Kodi (raspberrypi)._xbmc-events._udp.local, "QM" question SRV 0 0 9777 raspberrypi.local TXT SRV 0 0 9090 raspberrypi.local TXT
        65 26.075364775 192.168.0.13 → 224.0.0.251  MDNS 224 Standard query 0x0000 ANY Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local, "QM" question ANY Kodi (raspberrypi)._xbmc-events._udp.local, "QM" question SRV 0 0 9777 raspberrypi.local TXT SRV 0 0 9090 raspberrypi.local TXT
        66 26.276126863 192.168.0.13 → 224.0.0.251  MDNS 237 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local SRV, cache flush 0 0 9090 raspberrypi.local AAAA, cache flush fe80::369c:19e7:702d:4d7d A, cache flush 192.168.0.13 PTR _xbmc-jsonrpc._tcp.local
        67 26.276493633 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 241 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local SRV, cache flush 0 0 9090 raspberrypi.local AAAA, cache flush fe80::369c:19e7:702d:4d7d PTR _xbmc-jsonrpc._tcp.local
        68 26.280975861 192.168.0.13 → 224.0.0.251  MDNS 187 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-events._udp.local SRV, cache flush 0 0 9777 raspberrypi.local PTR _xbmc-events._udp.local
        69 26.281279402 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 207 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-events._udp.local SRV, cache flush 0 0 9777 raspberrypi.local PTR _xbmc-events._udp.local
        70 26.497192129  192.168.0.1 → 192.168.0.13 SSDP 284 HTTP/1.1 200 OK
        71 26.500846859  192.168.0.1 → 192.168.0.13 SSDP 314 HTTP/1.1 200 OK
        72 26.780215781 192.168.0.13 → 192.168.0.1  ICMP 98 Echo (ping) request id=0x042e, seq=17/4352, ttl=64
        73 26.999288348 192.168.0.13 → 192.168.0.1  TCP 74 58634 → 80 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4262126556 TSecr=0 WS=128
        74 27.002341257 192.168.0.13 → 192.168.0.1  TCP 74 54442 → 1900 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4262126559 TSecr=0 WS=128
        75 27.294122650 192.168.0.13 → 224.0.0.251  MDNS 237 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local SRV, cache flush 0 0 9090 raspberrypi.local AAAA, cache flush fe80::369c:19e7:702d:4d7d A, cache flush 192.168.0.13 PTR _xbmc-jsonrpc._tcp.local
        76 27.294393066 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 241 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-jsonrpc._tcp.local SRV, cache flush 0 0 9090 raspberrypi.local AAAA, cache flush fe80::369c:19e7:702d:4d7d PTR _xbmc-jsonrpc._tcp.local
        77 27.298689357 192.168.0.13 → 224.0.0.251  MDNS 187 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-events._udp.local SRV, cache flush 0 0 9777 raspberrypi.local PTR _xbmc-events._udp.local
        78 27.298948158 fe80::369c:19e7:702d:4d7d → ff02::fb     MDNS 207 Standard query response 0x0000 TXT, cache flush PTR Kodi (raspberrypi)._xbmc-events._udp.local SRV, cache flush 0 0 9777 raspberrypi.local PTR _xbmc-events._udp.local
        79 27.340022064 192.168.0.13 → 239.255.255.250 IGMPv2 46 Membership Report group 239.255.255.250
        80 27.820161681 192.168.0.13 → 192.168.0.1  ICMP 98 Echo (ping) request id=0x042e, seq=18/4608, ttl=64
        81 28.060027065 192.168.0.13 → 192.168.0.1  TCP 74 [TCP Retransmission] 58634 → 80 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4262127616 TSecr=0 WS=128
        82 28.060076283 192.168.0.13 → 192.168.0.1  TCP 74 [TCP Retransmission] 54442 → 1900 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4262127616 TSecr=0 WS=128
        83 28.497123305  192.168.0.1 → 192.168.0.13 SSDP 284 HTTP/1.1 200 OK
        84 28.507831976  192.168.0.1 → 192.168.0.13 ICMP 98 Echo (ping) reply    id=0x042e, seq=16/4096, ttl=64 (request in 61)
        85 28.508099319  192.168.0.1 → 192.168.0.13 ICMP 98 Echo (ping) reply    id=0x042e, seq=17/4352, ttl=64 (request in 72)
        86 28.515008677  192.168.0.1 → 192.168.0.13 TCP 74 80 → 58634 [SYN, ACK] Seq=0 Ack=1 Win=17376 Len=0 MSS=1460 WS=1 TSval=275988742 TSecr=4262126556
        87 28.515144458 192.168.0.13 → 192.168.0.1  TCP 66 58634 → 80 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4262128072 TSecr=275988742
        88 28.515011073  192.168.0.1 → 192.168.0.13 TCP 74 1900 → 54442 [SYN, ACK] Seq=0 Ack=1 Win=17376 Len=0 MSS=1460 WS=1 TSval=275988742 TSecr=4262126559
        89 28.515228468 192.168.0.13 → 192.168.0.1  TCP 66 54442 → 1900 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4262128072 TSecr=275988742
        90 28.515467790 192.168.0.13 → 192.168.0.1  HTTP 174 GET /WFADevice.xml HTTP/1.1
        91 28.515494874 192.168.0.13 → 192.168.0.1  HTTP 170 GET /RootDevice.xml HTTP/1.1
        92 28.518718303  192.168.0.1 → 192.168.0.13 ICMP 98 Echo (ping) reply    id=0x042e, seq=18/4608, ttl=64 (request in 80)
        93 28.522814959  192.168.0.1 → 192.168.0.13 TCP 66 [TCP Dup ACK 86#1] 80 → 58634 [ACK] Seq=1 Ack=1 Win=17376 Len=0 TSval=275988743 TSecr=4262127616
        94 28.522817355  192.168.0.1 → 192.168.0.13 TCP 66 [TCP Dup ACK 88#1] 1900 → 54442 [ACK] Seq=1 Ack=1 Win=17376 Len=0 TSval=275988743 TSecr=4262127616
        95 28.529803431  192.168.0.1 → 192.168.0.13 TCP 1514 HTTP/1.1 200 OK  [TCP segment of a reassembled PDU]
        96 28.529897025 192.168.0.13 → 192.168.0.1  TCP 66 58634 → 80 [ACK] Seq=105 Ack=1449 Win=32128 Len=0 TSval=4262128086 TSecr=275988744
        97 28.529941920  192.168.0.1 → 192.168.0.13 TCP 1514 80 → 58634 [ACK] Seq=1449 Ack=105 Win=17376 Len=1448 TSval=275988744 TSecr=4262128072 [TCP segment of a reassembled PDU]
        98 28.529958379 192.168.0.13 → 192.168.0.1  TCP 66 58634 → 80 [ACK] Seq=105 Ack=2897 Win=35072 Len=0 TSval=4262128086 TSecr=275988744
        99 28.529943222  192.168.0.1 → 192.168.0.13 HTTP/XML 204 HTTP/1.1 200 OK
       100 28.531200980 192.168.0.13 → 192.168.0.1  TCP 66 58634 → 80 [FIN, ACK] Seq=105 Ack=3036 Win=37888 Len=0 TSval=4262128088 TSecr=275988744
       101 28.532092227  192.168.0.1 → 192.168.0.13 TCP 66 80 → 58634 [ACK] Seq=3036 Ack=106 Win=17376 Len=0 TSval=275988744 TSecr=4262128088
       102 28.532898632  192.168.0.1 → 192.168.0.13 SSDP 314 HTTP/1.1 200 OK
       103 28.533849983  192.168.0.1 → 192.168.0.13 TCP 168 HTTP/1.1 200 OK  [TCP segment of a reassembled PDU]
       104 28.533946806 192.168.0.13 → 192.168.0.1  TCP 66 54442 → 1900 [ACK] Seq=109 Ack=103 Win=29312 Len=0 TSval=4262128090 TSecr=275988744
       105 28.535118834  192.168.0.1 → 192.168.0.13 HTTP/XML 1066 HTTP/1.1 200 OK
       106 28.535227324 192.168.0.13 → 192.168.0.1  TCP 66 54442 → 1900 [ACK] Seq=109 Ack=1104 Win=31232 Len=0 TSval=4262128092 TSecr=275988744
       107 28.536169092 192.168.0.13 → 192.168.0.1  TCP 66 54442 → 1900 [FIN, ACK] Seq=109 Ack=1104 Win=31232 Len=0 TSval=4262128093 TSecr=275988744
       108 28.537177267  192.168.0.1 → 192.168.0.13 TCP 66 1900 → 54442 [ACK] Seq=1104 Ack=110 Win=17376 Len=0 TSval=275988744 TSecr=4262128093
       109 28.636684257 192.168.0.13 → 192.168.0.1  TCP 74 54444 → 1900 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4262128193 TSecr=0 WS=128
       110 28.637841129  192.168.0.1 → 192.168.0.13 TCP 74 1900 → 54444 [SYN, ACK] Seq=0 Ack=1 Win=17376 Len=0 MSS=1460 WS=1 TSval=275988755 TSecr=4262128193
       111 28.637942795 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4262128194 TSecr=275988755
       112 28.638113941 192.168.0.13 → 192.168.0.1  HTTP 180 GET /x_wfawlanconfig.xml HTTP/1.1
       113 28.639894457  192.168.0.1 → 192.168.0.13 TCP 168 HTTP/1.1 200 OK  [TCP segment of a reassembled PDU]
       114 28.639949769 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=115 Ack=103 Win=29312 Len=0 TSval=4262128196 TSecr=275988755
       115 28.641081485  192.168.0.1 → 192.168.0.13 TCP 1514 1900 → 54444 [ACK] Seq=103 Ack=115 Win=17376 Len=1448 TSval=275988755 TSecr=4262128195 [TCP segment of a reassembled PDU]
       116 28.641125912 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=115 Ack=1551 Win=32128 Len=0 TSval=4262128198 TSecr=275988755
       117 28.641504557  192.168.0.1 → 192.168.0.13 TCP 1514 1900 → 54444 [ACK] Seq=1551 Ack=115 Win=17376 Len=1448 TSval=275988755 TSecr=4262128196 [TCP segment of a reassembled PDU]
       118 28.641535390 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=115 Ack=2999 Win=35072 Len=0 TSval=4262128198 TSecr=275988755
       119 28.642636898  192.168.0.1 → 192.168.0.13 TCP 1266 1900 → 54444 [PSH, ACK] Seq=2999 Ack=115 Win=17376 Len=1200 TSval=275988755 TSecr=4262128198 [TCP segment of a reassembled PDU]
       120 28.642663877 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=115 Ack=4199 Win=37888 Len=0 TSval=4262128199 TSecr=275988755
       121 28.643124136  192.168.0.1 → 192.168.0.13 TCP 1514 1900 → 54444 [ACK] Seq=4199 Ack=115 Win=17376 Len=1448 TSval=275988755 TSecr=4262128198 [TCP segment of a reassembled PDU]
       122 28.643153928 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=115 Ack=5647 Win=40832 Len=0 TSval=4262128200 TSecr=275988755
       123 28.644237259  192.168.0.1 → 192.168.0.13 HTTP/XML 600 HTTP/1.1 200 OK
       124 28.644271061 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [ACK] Seq=115 Ack=6181 Win=43776 Len=0 TSval=4262128201 TSecr=275988755
       125 28.644547883  192.168.0.1 → 192.168.0.13 TCP 66 1900 → 54444 [FIN, ACK] Seq=6181 Ack=115 Win=17376 Len=0 TSval=275988755 TSecr=4262128200
       126 28.648620008 192.168.0.13 → 192.168.0.1  TCP 66 54444 → 1900 [FIN, ACK] Seq=115 Ack=6182 Win=43776 Len=0 TSval=4262128205 TSecr=275988755
       127 28.649595058  192.168.0.1 → 192.168.0.13 TCP 66 1900 → 54444 [ACK] Seq=6182 Ack=116 Win=17376 Len=0 TSval=275988756 TSecr=4262128205
       128 28.821281139 192.168.0.13 → 192.168.0.1  ICMP 98 Echo (ping) request id=0x042e, seq=19/4864, ttl=64
       129 28.822326605  192.168.0.1 → 192.168.0.13 ICMP 98 Echo (ping) reply    id=0x042e, seq=19/4864, ttl=64 (request in 128)

There is something here that can make lags in the Ethernet LAN??

Thanks for your help!

popcornmix

2018-10-17, 16:37
Do you have UPnP/DLNA enabled in kodi? Does it help if you disable it?

Ugaitz

2018-10-17, 16:43
UPnP is disabled

Thank you

popcornmix

2018-10-17, 16:53
Does your router have a uPnP option? Can you disable that?

Ugaitz

2018-10-17, 17:02
Disabled, and restarted the router but issues persist.
Pages: 1 2
Kodi Community Forum > Support > General Support > Raspberry Pi > Lag in the LAN when Kodi (RPi3) is connected