In reply to a post by ukhardy07:

How do you find FTTH, what pings do you get?

Not too bad, just pinged TBB with IPv4 and IPv6 shown below:

ping thinkbroadband.com

Pinging thinkbroadband.com [2a02:68:1::4] with 32 bytes of data:
Reply from 2a02:68:1::4: time=6ms
Reply from 2a02:68:1::4: time=5ms
Reply from 2a02:68:1::4: time=5ms
Reply from 2a02:68:1::4: time=5ms

Ping statistics for 2a02:68:1::4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 6ms, Average = 5ms

ping -4 thinkbroadband.com

Pinging thinkbroadband.com [80.249.99.130] with 32 bytes of data:
Reply from 80.249.99.130: bytes=32 time=5ms TTL=53
Reply from 80.249.99.130: bytes=32 time=4ms TTL=53
Reply from 80.249.99.130: bytes=32 time=4ms TTL=53
Reply from 80.249.99.130: bytes=32 time=4ms TTL=53

Ping statistics for 80.249.99.130:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 5ms, Average = 4ms

This was done before the one in my sig:
Previous TBB Speedtest (18th Dec)

The one in my sig was done on the 25th in the morning before IPv6 kicked in.

So all in all its not too bad considering it use to be between 29 and 40 ms when we was on ADSL 2+.

Paul

Edited by PaulKirby (Mon 26-Dec-16 03:20:38)

A quick question?

Has anyone got a newer firmware than the current SG4B10002244 version on their Smart Hub ?

I ask because I am starting to get TR69 binary messages and I only got loads of those before when I received a new firmware update.

So I was wondering if anyone had a newer firmware yet?

Paul

Nope and I have a new router which only applies all its firmware upgrades today. I'd have assumed it would have pushed me to a newer version if available...

Also nothing has came through over on the BT forums or testing that I can see.

I ask because I am starting to get TR69 binary messages and I only got loads of those before when I received a new firmware update.

I'm also seeing a raft of TR69 events. They started late 31 Dec (4), a fair few yesterday and 16 so far today with the majority of those just before 3am.

Example:
02:49:24, 02 Jan. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed
02:49:24, 02 Jan. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated
02:49:24, 02 Jan. InformResponse:TR69 receiving
ȴ������
)c+�� message
02:49:23, 02 Jan. ppp1:TR69 event found : 4 VALUE CHANGE
02:49:23, 02 Jan. ppp1:TR69 event found : 2 PERIODIC
02:49:22, 02 Jan. ppp1:TR69 sending Inform message
02:49:22, 02 Jan. ppp1:TR69 event found : 4 VALUE CHANGE
02:49:22, 02 Jan. ppp1:TR69 event found : 2 PERIODIC
02:49:21, 02 Jan. ppp1:TR69 sending Inform message
02:49:20, 02 Jan. ppp1:TR69 creating new session with ACS

I have to admit to not knowing what most of these mean.

In reply to a post by ukhardy07:

Nope and I have a new router which only applies all its firmware upgrades today. I'd have assumed it would have pushed me to a newer version if available...

Also nothing has came through over on the BT forums or testing that I can see.

Ah, ok.

Paul

In reply to a post by MCM:

I have to admit to not knowing what most of these mean.

Yeah, that's exactly what I was getting before the last update.
However back then I saw the following messages in the logs:

"TR69 sending DownloadResponse message" and "Download:TR69 receiving"

So its probably not an update yet.

I also got it on the Jan 2nd but at 09:03 in the morning.

What I have noticed is that they have cleared the log, so I can only go back to 12:18:33 31 Dec.

Do a view all and save the log, then open in excel scroll down to the bottom, what's your earliest date?

Paul

Certainly something seems to be happening with the logs as earlier, as I mentioned, I could see four TR69 entries dated 31 December however the earliest entry in the log of any type is now:

04:01:53 01 Jan. BR_LAN:LAN Neighbor Discovery : Host xxxx is set active

The SmartHub last started 8 Days 17 Hours 50 minutes ago. Which may have been when 2244 was installed but I seem to think it rebooted again the next day for some unknown reason.

In reply to a post by MCM:

Certainly something seems to be happening with the logs as earlier, as I mentioned, I could see four TR69 entries dated 31 December however the earliest entry in the log of any type is now:

04:01:53 01 Jan. BR_LAN:LAN Neighbor Discovery : Host xxxx is set active

The SmartHub last started 8 Days 17 Hours 50 minutes ago. Which may have been when 2244 was installed but I seem to think it rebooted again the next day for some unknown reason.

Well mine was updated on the Firmware updated: 22-Dec-2016 I did do a reboot for it to boot up with the new firmware due to it hadn't rebooted.
And also rebooted on the 24th or 25th Dec due to no IPv6 and some sluggish happenings.

Says the following up time:

Network uptime: 8 Days, 13 Hours 51 Minutes 
 System uptime: 8 Days, 13 Hours 52 Minutes

Also a reboot doesn't clear the logs, if it did then how comes I don't have logs dating back to the 24th or the 25th of December ?

I just did another exporting on the logs and it seems that its only logging about 47 hours of logs, how stupid is that, the HH4 had logs that dated weeks even months on some logs.

Paul

I just did another exporting on the logs and it seems that its only logging about 47 hours of logs, how stupid is that, the HH4 had logs that dated weeks even months on some logs.

I don't think that it is time that is controlling how long the logs are kept but rather the volume of entries. I'm currently seeing 17,252 entries covering a period of 44hrs 56 mins.

I think the problem started when ipv6 was enabled as 13,041 of the 17,252 entries are:
BR_LAN:LAN Neighbor Discovery : Host fe80::xxxx:xxxx:xxxx:xxxx is set inactive
and that before ipv6 was enabled the log "life" would have been much longer.

In reply to a post by MCM:

I just did another exporting on the logs and it seems that its only logging about 47 hours of logs, how stupid is that, the HH4 had logs that dated weeks even months on some logs.

I don't think that it is time that is controlling how long the logs are kept but rather the volume of entries. I'm currently seeing 17,252 entries covering a period of 44hrs 56 mins.

I think the problem started when ipv6 was enabled as 13,041 of the 17,252 entries are:
BR_LAN:LAN Neighbor Discovery : Host fe80::xxxx:xxxx:xxxx:xxxx is set inactive
and that before ipv6 was enabled the log "life" would have been much longer.

Well I have exported it a few times now, one being ~14K logs and another being ~16K, it might be a file size or might be a combination of file size / items / length.

I just thought it was strange being very close to 47 hours and I mean very close.

Maybe its intentional for the smart hub to remove old logs, maybe this was to make it more stable and maybe that's why the HH4 and other HH had to do their 14 day reboot?

I know BT told me it was for stability of the hub, so maybe this was true.

But yeah there is huge amounts of those types of logs.

I think I will give it a few more days or until the weekend and check again.

Paul