8800NL IPv6 on BT FTTC Keep alive needed?

[elwisty]

Just an update, and a thank you for the new firmware.

With the new firmware the IPv6 connectivity has now been up for almost three days without any keep alive processes running.

Whatever was different in the new firmware in that area seems to have solved the problem.

Two bits of feedback on the new firmware.

a) Personally I don't like the new "basic" home screen when I log in. I prefered the one that is now called advanced.
b) The old firmware did not log TELNET login successes in information mode. The new one does. My problem is that DSLstats logs in every minute to collect the statistics data, so the log fills with TELNET entries. Is there a way to disable that logging without loosing the rest?

Thanks again for the new firmware.

[billion_fan]

Just an update, and a thank you for the new firmware.

With the new firmware the IPv6 connectivity has now been up for almost three days without any keep alive processes running.

Whatever was different in the new firmware in that area seems to have solved the problem.

Two bits of feedback on the new firmware.

a) Personally I don't like the new "basic" home screen when I log in. I prefered the one that is now called advanced.
b) The old firmware did not log TELNET login successes in information mode. The new one does. My problem is that DSLstats logs in every minute to collect the statistics data, so the log fills with TELNET entries. Is there a way to disable that logging without loosing the rest?

Thanks again for the new firmware.

a) Yes we Billion UK agree hence all newer devices don't have this 'Basic' menu
b) I don't think there is a option to disable 'Telnet' login logs

[elwisty]

Final Update.

Two weeks on and IPv6 has been rock solid on my BT FTTC line.

Whatever changed in that firmware you supplied certainly worked. Thank You.

Are you planning to make it widely available?

[davews]

Not sure if this thread is of relevance. 8800NL.R2 with firmware 2.52.d12 on BT FTTC. I am finding my ipv6 drops out after 10 days or so, comes back after a reconnection. Not investigated in depth at the moment and not looked at FTTC Keep alive. Any similar reports received?

[billion_fan]

Not sure if this thread is of relevance. 8800NL.R2 with firmware 2.52.d12 on BT FTTC. I am finding my ipv6 drops out after 10 days or so, comes back after a reconnection. Not investigated in depth at the moment and not looked at FTTC Keep alive. Any similar reports received?

No similar reports on the latest firmware, but BT always have issues with IPv6 implementation even on their own home hubs, so not unheard of.
I plan on putting a 8800NL R2 on a burn test soon with our ISP Zen and will report back after the new year , (test bench currently in use and to test this issue we need at least 10 days)

[billion_fan]

Not sure if this thread is of relevance. 8800NL.R2 with firmware 2.52.d12 on BT FTTC. I am finding my ipv6 drops out after 10 days or so, comes back after a reconnection. Not investigated in depth at the moment and not looked at FTTC Keep alive. Any similar reports received?

No similar reports on the latest firmware, but BT always have issues with IPv6 implementation even on their own home hubs, so not unheard of.
I plan on putting a 8800NL R2 on a burn test soon with our ISP Zen and will report back after the new year , (test bench currently in use and to test this issue we need at least 10 days)

Just to follow up, all seems well on my 8800NL R2 with Zen as the ISP (screen shot attached)

[davews]

Thanks. With my initial test ipv6 dropped out after around 10 days. But I see it is now still up after 17 days so it looks an intermittent issue.