TG582n Fibre router - Ethernet switch issues under load

Hi,

I have the Plusnet supplied Technicolor TG582n FTTC router. I have a wired PC, laptop and homeplug in the three usable ports and connected to the homeplugs are an Xbox, sky box and other living room devices.

I upgraded to FTTC in September and noticed i'd occasionally drop out of games but I didn't know why. When black ops 2 was released it started to happen more often and once it starts to happen it will keep occurring until I reboot the router. I don't know if the code in that game is particular inefficient (a good chance) but when I'm host and I search for a game the switch often shuts down.

I know the switch is going down because I have a ping going from the wired PC to the router, bbc and plus.net and all three drop. The router logs don't show anything. If I cancel the search the router starts to respond again so its not rebooting itself or anything like that.

I'll paste some pings below but I was wondering if anyone has had these sorts of issues before or has any other advice?

Thanks in advance.

Duncan

Logs and broadband quality meter graph from 2nd December.

Quality meter link

Router
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2456ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.254: bytes=32 time=729ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1026ms TTL=64
Reply from 192.168.1.254: bytes=32 time=469ms TTL=64
Reply from 192.168.1.254: bytes=32 time=746ms TTL=64
Reply from 192.168.1.254: bytes=32 time=829ms TTL=64
Reply from 192.168.1.254: bytes=32 time=905ms TTL=64
Reply from 192.168.1.254: bytes=32 time=370ms TTL=64
Reply from 192.168.1.254: bytes=32 time=328ms TTL=64
Reply from 192.168.1.254: bytes=32 time=48ms TTL=64
Reply from 192.168.1.254: bytes=32 time=81ms TTL=64
Reply from 192.168.1.254: bytes=32 time=191ms TTL=64
Reply from 192.168.1.254: bytes=32 time=155ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=117ms TTL=64
Reply from 192.168.1.254: bytes=32 time=19ms TTL=64

Plus.net
Reply from 212.159.9.2: bytes=32 time=15ms TTL=247
Reply from 212.159.9.2: bytes=32 time=2130ms TTL=24
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.159.9.2: bytes=32 time=2668ms TTL=24
Reply from 212.159.9.2: bytes=32 time=2115ms TTL=24
Reply from 212.159.9.2: bytes=32 time=2027ms TTL=24
Reply from 212.159.9.2: bytes=32 time=1552ms TTL=24
Reply from 212.159.9.2: bytes=32 time=249ms TTL=247
Reply from 212.159.9.2: bytes=32 time=245ms TTL=247
Reply from 212.159.9.2: bytes=32 time=104ms TTL=247
Reply from 212.159.9.2: bytes=32 time=376ms TTL=247

BBC
Reply from 212.58.241.131: bytes=32 time=7ms TTL=246
Reply from 212.58.241.131: bytes=32 time=8ms TTL=246
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.241.131: bytes=32 time=2048ms TTL=246
Reply from 212.58.241.131: bytes=32 time=1645ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2115ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2497ms TTL=246
Reply from 212.58.241.131: bytes=32 time=1552ms TTL=246
Reply from 212.58.241.131: bytes=32 time=249ms TTL=246
Reply from 212.58.241.131: bytes=32 time=245ms TTL=246
Reply from 212.58.241.131: bytes=32 time=34ms TTL=246
Reply from 212.58.241.131: bytes=32 time=376ms TTL=246
Reply from 212.58.241.131: bytes=32 time=580ms TTL=246

In reply to a post by dmaidmen:

I know the switch is going down because I have a ping going from the wired PC to the router, bbc and plus.net and all three drop.

To be pedantic, your pings don't prove the switch function is faulty. Running a ping to another device on your LAN would confirm if it's the switch or routing functions that are flaky.

To be less pedantic, certainly looks like there's something wrong!

Hi there,

A member of our products team who is responsible for the hardware we supply would be happy to help you diagnose this.

Would it be OK if we gave you a call on Monday perhaps to go through a few things?

Thanks Adam. PM Sent.