Technical Discussion
  >> Hardware Issues

Register (or login) on our website and you will not see this ad.

  Print Thread
Standard User BarkingMad
(regular) Wed 22-Aug-18 08:04:35
Print Post

Loss of connection

[link to this post]
Has anyone got any suggestions as to why this may be happening?

I have the following set-up

YouView box hardwired to power line extender with wifi capability. This extender also has DVD connected to it and other wireless devices. The other end of the power line is connected to a BIPAC 8800 NL R2. The power line extender is currently TPLink AV1300.

I've noticed the Ipad freeze/wait when visiting web pages and at the same time the YouView box report it has lost internet connection. I've downloaded iNetTools to the Ipad to perform a ping to the router. Last night the tool reported....

Note: Ping from Ipad to TPlink AV1300 to BIPAC 8800NL R2 via wifi on 21 Aug @ 19:27

PING ( 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
64 bytes from icmp_seq=28 ttl=32 time=43.939 ms
64 bytes from icmp_seq=29 ttl=32 time=9.487 ms
64 bytes from icmp_seq=30 ttl=32 time=5.901 ms
Request timeout for icmp_seq 31
64 bytes from icmp_seq=32 ttl=32 time=33.270 ms
64 bytes from icmp_seq=33 ttl=32 time=4.685 ms
64 bytes from icmp_seq=34 ttl=32 time=38.975 ms
64 bytes from icmp_seq=35 ttl=32 time=3.951 ms
64 bytes from icmp_seq=36 ttl=32 time=8.557 ms
64 bytes from icmp_seq=37 ttl=32 time=33.118 ms
64 bytes from icmp_seq=38 ttl=32 time=5.089 ms
64 bytes from icmp_seq=39 ttl=32 time=11.330 ms
64 bytes from icmp_seq=40 ttl=32 time=40.242 ms
64 bytes from icmp_seq=41 ttl=32 time=9.873 ms
64 bytes from icmp_seq=42 ttl=32 time=7.470 ms
64 bytes from icmp_seq=43 ttl=32 time=39.305 ms
64 bytes from icmp_seq=44 ttl=32 time=11.139 ms
64 bytes from icmp_seq=45 ttl=32 time=8.565 ms
64 bytes from icmp_seq=46 ttl=32 time=41.101 ms
64 bytes from icmp_seq=47 ttl=32 time=17.894 ms
64 bytes from icmp_seq=48 ttl=32 time=7.835 ms
64 bytes from icmp_seq=49 ttl=32 time=28.847 ms
64 bytes from icmp_seq=50 ttl=32 time=9.006 ms
64 bytes from icmp_seq=51 ttl=32 time=4.083 ms
64 bytes from icmp_seq=52 ttl=32 time=35.077 ms
64 bytes from icmp_seq=53 ttl=32 time=5.892 ms
64 bytes from icmp_seq=54 ttl=32 time=4.094 ms
64 bytes from icmp_seq=55 ttl=32 time=40.610 ms
64 bytes from icmp_seq=56 ttl=32 time=4.254 ms
64 bytes from icmp_seq=57 ttl=32 time=1.811 ms
64 bytes from icmp_seq=58 ttl=32 time=39.758 ms
64 bytes from icmp_seq=59 ttl=32 time=8.931 ms
64 bytes from icmp_seq=60 ttl=32 time=8.292 ms
64 bytes from icmp_seq=61 ttl=32 time=35.995 ms
64 bytes from icmp_seq=62 ttl=32 time=8.594 ms
64 bytes from icmp_seq=63 ttl=32 time=9.022 ms
64 bytes from icmp_seq=64 ttl=32 time=40.021 ms
64 bytes from icmp_seq=65 ttl=32 time=4.582 ms
64 bytes from icmp_seq=66 ttl=32 time=5.487 ms
64 bytes from icmp_seq=67 ttl=32 time=40.350 ms
64 bytes from icmp_seq=68 ttl=32 time=5.065 ms
64 bytes from icmp_seq=69 ttl=32 time=2.791 ms
64 bytes from icmp_seq=70 ttl=32 time=42.929 ms
64 bytes from icmp_seq=71 ttl=32 time=28.808 ms

--- ping statistics ---
72 packets transmitted, 43 received, 40.28% packet loss
round-trip min / avg / max = 1.811 / 11.056 / 43.939 ms

The problem occurred again whislt connected to the TPLink wirelessly but I connected to the 8800 via wifi and got these results....

Note: Ping from Ipad to BIPAC 8800NL R2 via wifi on 21 Aug @ 20:06

Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from icmp_seq=5 ttl=32 time=9.115 ms
64 bytes from icmp_seq=6 ttl=32 time=10.692 ms
64 bytes from icmp_seq=7 ttl=32 time=16.579 ms
64 bytes from icmp_seq=8 ttl=32 time=6.968 ms
64 bytes from icmp_seq=9 ttl=32 time=4.370 ms
64 bytes from icmp_seq=10 ttl=32 time=87.164 ms
64 bytes from icmp_seq=11 ttl=32 time=10.149 ms
64 bytes from icmp_seq=12 ttl=32 time=9.425 ms

--- ping statistics ---
14 packets transmitted, 8 received, 42.86% packet loss
round-trip min / avg / max = 4.370 / 11.033 / 87.164 ms

Initially, I thought I had a TPLink wireless issue but since the Youview box is hard wired to the TpLink and also exprienced problems I thought I had power line issue. However, since I can connect to the 8800 via wifi and still see dropped pings suggest a problem with the 8800.

The 8800 ysstem logs show no issues and the 8800 has been up for weeks. The frmware is upto date. The TPlink status lights stayed green throughout the loss of connectivity.

I'm at home during the day and don't see any problems. Problems tend to occur in the evening.

Any thoughts / suggestions?

Thank you
  Print Thread

Jump to