did u run a ping to google, talktalk or bbc etc concurrently with the gateway IP address to eliminate the QoS issue a previous poster described?

A router connects networks together by definition, so yes the gateway is on a different subnet to your pc, but is on the same subnet as the WAN side of your router.

I think the concurrent test would prove the issue is outside your jurisdiction if both pings fail at the same time, seeing as you've swap tested the router, cable and filter.

In reply to a post by Myth:

did u run a ping to google, talktalk or bbc etc concurrently with the gateway IP address to eliminate the QoS issue a previous poster described?

I did not run the concurrent test. However, the issue is resolved now, so I cannot repeat the test.

I get your point about the WAN, thanks.

Hi Robby,

I understand this is under investigation with the Members Forum (and yes theres only one OCE called mark so it would be me)

Please ensure your updating your thread on the TTMF with the info you ahve posted here to ensure we have full visibility of this (some sections are maanged by Multiple OCE, Braodband partcularly, so it may not be myself that next reaches your thread to reply, there is however only one OCE managing external sites so at present I am the only OCE aware of the above.)

Cheers

Mark
TalkTalk Online Community Department

In reply to a post by TALKTALK_SUPPORT:

I understand this is under investigation with the Members Forum (and yes theres only one OCE called mark so it would be me)

I have updated the TT member forum to say that the issue is resolved now. A different OCE has replied to that, so I assume that thread is considered closed over there.

However, I still have no idea what caused the network problems in the first place. Can you shed some light on this? I also do not know if my posting on the TT member forum instigated the repair work, or if this was done independently. Do you know?

In reply to a post by Zarjaz:

The 50 sobs would be for a Talktalk 'cube' engineer.

FYI and more correctly, "Qube". (As in http://qubegb.com/index.htm )

Hi Mark,

sadly the issue reappeared last night. I observed packet loss from about 5pm to at least 10pm. This morning the connection seems to be fine again. Can we try to get to the bottom of this?

I have updated the TT member forum thread with the appropriate details.

Cheers,
Robert

In reply to a post by Myth:

did u run a ping to google, talktalk or bbc etc concurrently with the gateway IP address to eliminate the QoS issue a previous poster described?

As the issue reappeared last night, I could do this concurrent test now. These ping runs with 200 packets each were all started within 2 seconds of each other. The overall results are:

--- www.l.google.com ping statistics ---
200 packets transmitted, 130 received, 35% packet loss, time 199505ms
rtt min/avg/max/mdev = 30.368/33.412/37.272/2.703 ms

--- www.bbc.net.uk ping statistics ---
200 packets transmitted, 139 received, 30% packet loss, time 203548ms
rtt min/avg/max/mdev = 19.881/20.618/21.661/0.395 ms

--- www.talktalk.co.uk ping statistics ---
200 packets transmitted, 145 received, 27% packet loss, time 213599ms
rtt min/avg/max/mdev = 27.158/27.940/32.812/0.613 ms

--- 78.147.240.1 ping statistics ---
200 packets transmitted, 146 received, 27% packet loss, time 199595ms
rtt min/avg/max/mdev = 16.628/17.512/18.279/0.368 ms

The data for my ADSL port at that time was

IP Address 78.147.243.223
Gateway IP Address 78.147.240.1

So the last ping result is for the port's gateway IP.

Can you extract something useful from that data?

i think u missed the point slightly, sorry

edit: re-reading.... yes you eliminated QoS within the gateway as the issue, but do the below as well:

I was saying do the test concurrently with the LAN ip (which we believe is 100% fine), the WAN IP (which is the other side of the router (your responsibility) which I think is 100% fine, the gateway (which is the first hop outside of your control) and any of the major websites.

Then at the moment u see packet loss, look along and you can see if all the places failed at that moment or just the bbc, or both bbc and gateway, or all 4 etc etc. I was not interested in averages, but showing that at the exact moment pings fail to the gateway, they also fail at bbc, but are OK on both sides of your router.

This would show there is an error (pings fail to websites) and that the error occurs outside of your sphere of responsibility (router is fine, gateway onwards fails). As you didnt ping anything that had 100% success (your IP address) at the same time all your experiment shows is that you have an issue, it doesn't narrow down who's responsibility it is as it stands

hope this makes sense

Edited by deleted (Fri 27-Jul-12 19:43:53)

Hi Myth,

the LAN IP and WAN IP would both have 0% packet loss.

These four ping commands send out 1 ping per second (independently), and as far as I could tell, there was no correlation between the times at which the various ping commands encountered a lost packet.

At the moment all seems to be working fine again, just keeping my fingers crossed!!!

In reply to a post by Zarjaz:

The 50 sobs would be for a Talktalk 'cube' engineer.

I just found this on the tt site BT engineer charges Or are they misleading customers