Currently not getting any IPv6 (SLAC address or DHCP-PD prefix). Connected to gateway bng1

Anyone else not getting IPv6 before I go and wipe/re-config my router?

I am connected to bng1.th-lon too and no IPV6. This may also explain the disconnects / connections issues i have had over the last week or so, I have been connected (on and of of course) to the GW in Manchester for the last 10+ years.

In reply to a post by sor:

I'm also interested to know why Zen haven't enabled all of their gateways (or at least enough to cope with demand, as being moved off of dsl6 helped improve my speeds a bit, though nothing close to expected performance). Perhaps they're not confident that all CPE will handle it?

Either that or some of their gateways are running old equipment which don't support IPv6. It is quite possible, and you can't blame them, if they have old kit, and its stable etc etc...

Yes. Same problem here. It appears I'm connected but I'm not as I can't ping anything IPv6 from my router. There's no IPv6 traffic showing in the logs either and any IPv6 test site shows me as not enabled now whereas it did before.
Was working fine for a month or so since I changed and I haven't altered any config since on my side.
I've emailed ipv6@zen as I don't think their support for IPv6 is that advanced at the weekend so will wait to see what comes back.

In reply to a post by rlees85:

Connected to gateway bng1

I was also forced onto this gateway this morning. Per the code adjustment I put in place a few days ago, my router has been disconnecting and reconnecting every minute to try and get back onto a gateway which is IPv6, but consistently lands back on this one. So I've lowered the interval at which it now checks for IPv6 back to once a day.

So IPv6 is now busted, and yet I thought this was supposed to be a non-beta service. They have until early May to sort this mess out otherwise I'm migrating back to A&A.

In reply to a post by mixt:

In reply to a post by rlees85:

Connected to gateway bng1

I was also forced onto this gateway this morning. Per the code adjustment I put in place a few days ago, my router has been disconnecting and reconnecting every minute to try and get back onto a gateway which is IPv6, but consistently lands back on this one. So I've lowered the interval at which it now checks for IPv6 back to once a day.

So IPv6 is now busted, and yet I thought this was supposed to be a non-beta service. They have until early May to sort this mess out otherwise I'm migrating back to A&A.

I'm also on bng1 (though AFAIK I still have IPv6 turned off on my account). Interestingly my connection is doing much better today as far as throughput goes (the single threaded issue as discussed in the other thread).

Edited by deleted (Mon 07-Mar-16 11:15:12)

Hi,

Apologies for this. We're working on fully enabling IPv6 on bng1.th-lon and expect this to be completed this afternoon.

I've stopped bng1.th-lon from taking new sessions until this is resolved. If you reconnect your PPP now IPv6 connectivity should be restored.

Apologies again for the disruption.

Thanks,

Jon

Hi,

Apologies for this. I've disabled bng1.th-lon until the IPv6 issue is resolved, so if you drop PPP now you'll get on a different gateway.

Our steering system directs new sessions to the gateway with fewest subscribers, which is why you'll have been consistently connecting to that one.

Thanks,

Jon

Thanks Jon, but I'm now on dsl9 which doesn't support IPv6 either.

Sorry about that! We'll correct the issue with dsl9.th-lon as well. In the meantime, I've stopped new sessions connecting to dsl9.th-lon, so a disconnect/reconnect should restore it.

Understand your frustration with this, and I'll ensure the feedback on this is taken on board. Apologies again.