|
|
|
So at approximately 16:14 today, my ppp session bounced. From this point onwards, the routing of my /48 IPv6 prefix has been non-existent (the /64 prefix is fine; the ppp interface auto-configures itself without issues and pinging the IPv6 world from the router still works using this auto-configured address).
Further investigation shows no acknowledgement from the Zen side for any dhcp6c requests for auto-delegating the /48 to me.
Anyone else seeing the same symptoms? Zen, can you un-break what ever you've decided to break today with regards to IPv6 /48 delegation? Nothing has changed my side.
|
|
|
This may explain why my IPv6 has gone wonky too. I've had a few power cuts and have otherwise been messing around with my network, so I assumed it was due to this.
Looks like it might not have been something I did
|
|
|
|
Tech support emailed.
I did read somewhere that they have changed the option for how this stuff is configured, that is, it is possible for them to just statically route the /48 directly without the need for the router requesting it (how A&A do things). I'll see if they can configure this for me instead; it will save the antics I currently have to perform (restarting dhcp6c) upon each new established ppp session.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
I've got the same problem. Zen's DHCPv6 server is not responding to any requests, so you cannot delegate the /48 prefix. As Zen don't install the route to the /48 until the prefix is delegated, there's no routing to and from the /48.
I spoke to tech support around half an hour ago, who said they had no reports of any outages. They asked me to contact the IPv6 team on [email protected] enclosing any evidence. I will shortly be sending in a packet capture and log extract from my router, showing the problem. I will also point them to this thread.
|
|
|
I will shortly be sending in a packet capture and log extract from my router, showing the problem. I will also point them to this thread.
I've just e-mailed the packet capture, log and problem description to [email protected]. Hopefully this will help in getting the problem sorted out.
Now that IPv6 is a supported service, hopefully Zen will improve their monitoring to detect this sort of problem.
|
|
|
|
Thanks David. I won't bother emailing the IPv6 team then but I have logged a general support ticket on their system.
As I said in my other post on this thread, I have also taken this opportunity to requested if they can make this a static route so as not to be reliant on dhcp6c for requesting it.
|
|
|
|
The DHCPv6 server started responding again around 13:15, according to my logs. I've now successfully delegated my /48 prefix, restoring full IPv6 connectivity to my networks.
|
|
|
|
Yes, looks to be back; session just bounced and its all working again.
Did they say what was wrong?
|
|
|
Anyone else seeing the same symptoms? Zen, can you un-break what ever you've decided to break today with regards to IPv6 /48 delegation? Nothing has changed my side.
Have done at around 13:10 today . I'm not sure why it was missed on our testing, so I'll review that as well.
It was an over zealous ACL which was only meant to be blocking customers from sending RA's to our Gateways. The gateways don't respond to the RAs but it does spam the log files a lot. Will see if we can find out which CPE are doing that. Though they do seem to be making it difficult by sourcing the RAs from fe80::1 with src mac of 00:00:00:00:00:00.
The ACL has now been amended to allow the multicast sourced DHCPv6 messages through, so everything should be back to normal following a PPP session reset.
|
|
|
Yes, looks to be back; session just bounced and its all working again.
Did they say what was wrong?
It would be inappropriate for me to repost the e-mail reply I received at 13:24 verbatim, though it contained the suggestion that the problem was related to a configuration change that was made yesterday. The e-mail said that the issue should now be resolved, and that I should drop my PPP session and reconnect.
In fact, I didn't need to drop the session - my DHCPv6 daemon kept retrying and successfully delegated the prefix at 13:15 without a session drop.
|
|
|
I've got the same problem. Zen's DHCPv6 server is not responding to any requests, so you cannot delegate the /48 prefix. As Zen don't install the route to the /48 until the prefix is delegated, there's no routing to and from the /48.
Hi, if you ask the IPv6 support guys to delete and re-add your IPv6 RADIUS details it will now be rebuilt with support for static routing. This was one of the pieces of feedback we took from the trial, though it has not been retrospectively applied to the trialist accounts yet.
All new accounts should have this by default
|
|
|
Also, per my support request, they've added in a static route for my /48 so I no longer need to run dhcp6c. Nice!
|
|
|
Have done at around 13:10 today . I'm not sure why it was missed on our testing, so I'll review that as well.
It was an over zealous ACL which was only meant to be blocking customers from sending RA's to our Gateways. The gateways don't respond to the RAs but it does spam the log files a lot. Will see if we can find out which CPE are doing that. Though they do seem to be making it difficult by sourcing the RAs from fe80::1 with src mac of 00:00:00:00:00:00.
The ACL has now been amended to allow the multicast sourced DHCPv6 messages through, so everything should be back to normal following a PPP session reset.
Thanks for the explanation and welcome to the forums. Please hang around, and, assuming that you are Zen staff, please e-mail team (at) thinkbroadband.com to enquire about getting an isp tag.
Whilst you are looking at the ACLs, can you amend the ACLs to allow ICMPv6 echo request / echo reply to the gateway link local addresses from CPE link local addresses (i.e. ICMPv6 types 128 and 129 from fe80::/10 to fe80::/10)? In my experience, such traffic is blocked and I don't think my firewall rules are to blame.
Without the ability to ping6 the gateway link local addresses, the gateway monitoring code in pfSense and possibly in other routers doesn't work without manual configuration of a non-gateway monitoring target.
As has been wished for before, some way of setting rDNS for IPv6 would be very useful. In my case, delegation to a customer run authoritative DNS server would be fine, though not everyone is in a position to run a DNS server.
|
|
|
Whilst you are looking at the ACLs, can you amend the ACLs to allow ICMPv6 echo request / echo reply to the gateway link local addresses from CPE link local addresses (i.e. ICMPv6 types 128 and 129 from fe80::/10 to fe80::/10)? In my experience, such traffic is blocked and I don't think my firewall rules are to blame.
......
As has been wished for before, some way of setting rDNS for IPv6 would be very useful. In my case, delegation to a customer run authoritative DNS server would be fine, though not everyone is in a position to run a DNS server.
The ACL should permit all traffic from fe80::/10 to fe80::/10 (apart from ICMP type 135). Would you be able to email this query into the IPv6 support team ( [email protected]) along with your username and ask them to forward it onto Brandon? I'll then investigate and see if we can figure out what is happening.
With regards to rDNS, again please email the request to the IPv6 team, they'll then get this set up for you. We are working on DNS and portal tools to support IPv6 but I cannot provide a commitment for when these will be available.
Cheers for the heads up about getting flare added to my username, I'll drop thinkbroadband a line and get this added.
|
|
|
|
Thanks for fixing this so quickly!
|
|
|
|
I still have problems. It was suggested that it would help to start a new PPP session but not being very technical I do not know how to go about this.
Will Zen get round to sorting this for everyone automatically so people like me who do not understand the technicalities do not lose out?
Being on an FTTP connection I cannot just turn off the GPON Terminal like you can a normal modem if that is what is required.
Help would be appreciated because when in the past I have contacted Zen IPv6 support it has taken weeks to get a reply.
|
|
|
I still have problems. It was suggested that it would help to start a new PPP session but not being very technical I do not know how to go about this.
Sorry, resetting the PPP session is just an overly technical way is saying 'reset your connection'. A reboot of your router is the easiest way to do this.
|
|
|
|
Thanks.
Rebooting the router itself has not solved the problem. However I suppose that will not have affected the connection itself as I am on FTTP and the "modem" bit is a GPON Terminal so it will have maintained the session. If I turn off the power supply to the GPON it just goes onto battery backup and still maintains the connection. I do not really feel like doing anything else with the GPON so I guess I am stuck with the way things are.
|
|
|
|
What you really need is a feature on the Zen portal which allows you to initiate a disconnect of the PPP session from the Zen side. That would also work.
Looks like you will have to ask them to do this for you, if there's no automated way of doing it on the portal (I've not seen one).
|
|
|
Thanks.
There is no automated way of doing it so I did ring Zen support who killed the session for me but unfortunately after I reconnected the problem persists.
I had already sent an email to IPv6 support yesterday and the normal support guy said he will draw their attention to it get them to look at my email so they can sort things.
What you really need is a feature on the Zen portal which allows you to initiate a disconnect of the PPP session from the Zen side. That would also work.
Looks like you will have to ask them to do this for you, if there's no automated way of doing it on the portal (I've not seen one).
Edited by Jax2 (Thu 11-Feb-16 12:47:38)
|
|
|
|
Further Update.
Zen have done their stuff. However oddly the Thinkbroadband "Test your IPv6 Readiness Test" tells me my ISPS server does not have access to IPv6. If I run the tests on Jason Feslers site which the Thinkbroadbands test is based on it shows is no such problem and tells me my ISPS server does have IPv6 access. I wonder which is right, in other words are things running as they should or not?
|
|
|
I get the same thing. I believe TBB is at fault.
Strangely enough, I experienced this exact same issue back in May 2014. I had to go hunting in my Gmail to locate the email I sent to John, who subsequently fixed this problem.
For the record, here is what I sent (I've also now reminded myself how I diagnosed this issue!):
Query regarding IPv6 Readiness Test
I was with Andrews & Arnold running full IPv4 and native IPv6. When I was with them, I was able to run your IPv6 Readiness Test and score a full 10/10.
I have now switched to Zen Internet running a HE (Hurricane Electric) IPv6 tunnel.
On both setups, I run dnsmasq (broadband router is Linux CentOS) with this listening on both IPv4 and IPv6 local interfaces. But, I now only score 9/10 for the IPv6 Readiness Test - the part that is failing is:
Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.
I have looked at what is happening at this part of the test and it seems it is trying to resolve A and AAAA records against ds.v6ns.v6test.thinkbroadband.com:
| Text | 1
23
4 | 12:25:54.809629 IP 192.168.0.130.44976 > 192.168.0.1.53: 59202+ A? ds.v6ns.v6test.thinkbroadband.com. (51)
12:25:54.809687 IP 192.168.0.130.9411 > 192.168.0.1.53: 34418+ AAAA? ds.v6ns.v6test.thinkbroadband.com. (51)12:25:54.810126 IP 192.168.0.1.53 > 192.168.0.130.44976: 59202 ServFail 0/0/0 (51)
12:25:54.810239 IP 192.168.0.1.53 > 192.168.0.130.9411: 34418 ServFail 0/0/0 (51) |
Can you confirm if this is expected behaviour and how exactly this part of the test works? If it is the HE tunnel, I fail to see how this would affect the result of the test.
So, no surprise, I did some further testing just now using dig and it seems this issue has resurfaced.
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
| $ dig -t A ds.v6ns.v6test.thinkbroadband.com
; <<>> DiG 9.8.3-P1 <<>> -t A ds.v6ns.v6test.thinkbroadband.com
;; global options: +cmd;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 19089;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ds.v6ns.v6test.thinkbroadband.com. IN A
;; Query time: 20 msec;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Feb 11 19:50:47 2016;; MSG SIZE rcvd: 51
$ dig -t AAAA ds.v6ns.v6test.thinkbroadband.com
; <<>> DiG 9.8.3-P1 <<>> -t AAAA ds.v6ns.v6test.thinkbroadband.com
;; global options: +cmd;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 16287;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ds.v6ns.v6test.thinkbroadband.com. IN AAAA
;; Query time: 14 msec;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Feb 11 19:51:01 2016;; MSG SIZE rcvd: 51 |
Once John fixes these 2 records again, the test should be all green.
|
|
|
|
Thanks for that, very interesting. I must admit that I started to have my doubts when I realised that the other test gave different results.
|
|
|
|
I contacted John again, pointing him to this thread, and he's now fixed the A and AAAA records.
Try again and all should be good.
|
|
|
|
Thanks again, all sorted and working fine now.
|
|
|
With regards to rDNS, again please email the request to the IPv6 team, they'll then get this set up for you. We are working on DNS and portal tools to support IPv6 but I cannot provide a commitment for when these will be available.
Seems you guys have finally set my rDNS up - thanks very much for doing this!
Final point of note - you really need to map some IPv6 addresses and glue-records against your name servers and with Nominet, because currently you're only serving IPv6 reverse DNS from IPv4-only enabled infrastructure.
Domain name:
zen.co.uk
...
Name servers:
ns0.zen.co.uk 212.23.8.1
ns1.zen.co.uk 212.23.3.1
|
|
|
Final point of note - you really need to map some IPv6 addresses and glue-records against your name servers and with Nominet, because currently you're only serving IPv6 reverse DNS from IPv4-only enabled infrastructure.
A very good point! Brandon and I have just been having a chat with our Systems team, and we'll be working with them to get this resolved (pardon the pun!).
We'll also get Brandon an ISP tag sorted
Jon
|
|
|
FYI, I have just gained knowledge from Zen technical support themselves that not all of Zen's gateways are IPv6 enabled. I rebooted my router yesterday and landed up on gateway dsl9 (normally I connect to dsl6) and, on that gateway, no link level IPv6 address is presented on the ppp interface, completely breaking IPv6 connectivity (this normally shows up as "inet6 addr: fe80::1/10 Scope:Link" upon running ifconfig).
I've updated my scripts to check for this eventuality moving forward, so if it looks like I have connected to a gateway which isn't presenting an IPv6 link level address, I bounce the ppp session and re-connect.
This issue remains outstanding with the IPv6 team - namely, if I'm IPv6 enabled, and not all their gateways support IPv6, why did I land up on a gateway which does not support it?
I have to say, in my opinion, becoming increasingly more reliant on IPv6 connectivity, this is hardly a confidence boost and the kind of level of service I expected from Zen, for the premium I'm paying. Effectively, your IPv6 service might as well be in beta still, given this finding. With A&A, I never experienced issues like this and it may sway me to return to them in May once my contract is up here, because I just didn't get these kind of problems with them.
Edited by deleted (Thu 03-Mar-16 12:28:21)
|
|
|
FYI, I have just gained knowledge from Zen technical support themselves that not all of Zen's gateways are IPv6 enabled. I rebooted my router yesterday and landed up on gateway dsl9 (normally I connect to dsl6) and, on that gateway, no link level IPv6 address is presented on the ppp interface, completely breaking IPv6 connectivity (this normally shows up as "inet6 addr: fe80::1/10 Scope:Link" upon running ifconfig).
This is what I was told too (normally on dsl6, but had to have IPv6 removed as part of the troubleshooting for the throughput issue)
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?
|
|
|
|
having the same issue, my ipv4 traffic is a bit of a hit and miss today, no issues on the status page will contact Zen tho
|
|
|
|
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.
Various (Dile up) -> clara.net (Dile up) -> TELE2 (Microwave) -> ZeN (ADSL)
|
|
|
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...
ZeN Fibre Unlimited 2
|
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
|
Ok, back on dsl6 now. Hope you get all these upgrades fixed soon so all these issues can just... disappear!
|
|
|
|
I'm now monitoring the connection using TB's monitoiring tool, still no ipv6 for me but the ipv4 works fine didn't check with gateway I was on.
|
|
|
|
Mine was fixed also. Got an email from Zen about 1100hrs on Monday (when their main support is in) after I'd emailed ipv6@zen on sunday afternoon. Obviously the IPv6 team isn't in at the weekend as it's early days for them but as time goes on, I suspect they'll have full IPv6 support 24/7.
All in all, I'm very happy with Zen and will stay with them. FTTP now please.....
|
|
|
|
24/7?
|
|
|
|
24 hours a day, 7 days a week
|
|
|
|
@jongreen84
Any chance of seeing if bng1.th-lon has the same issues with v6?
I moved to it for the first time ever from dsl6.th-lon and lost v6.
|
|
|
@jongreen84
Any chance of seeing if bng1.th-lon has the same issues with v6?
I moved to it for the first time ever from dsl6.th-lon and lost v6.
Hi BNG1 is dual stacked. If you pm your username and email address I'll take a look at your connection and see if there are any issues.
Bran.
|
|
|
|
Post deleted by summat
|