Well, my migration back to IDNet from Vivaciti (LLU) was supposed to happen today by 6:00pm. I had a couple of line drops during the day, which is quite unusual, so I thought was the work being done in the exchange. It seems this was not so and I am still chugging away on Vivaciti.
I did contact IDNet support at around 5:00pm to see if they had any more information but I have not received a reply so I guess I will be on Vivaciti for a while longer.
Don't ya just love BT (NOT!)
Do Vivaciti have BT products? If so have you tried your IDNet log in details. When switching BT products both connections remain live for awhile so I'm just applying a bit of lateral thinking which maybe completely wrong.
Steve
Yes, I did try once or twice but to no avail. I think I will try again.
Adrian
I believe it can be up to 11.59 on the migration day.
It could be, but LLU swaps tend to be in office hours due to the lift and shift required.
Just tried again but nothing. It doesn't really matter as I still have internet access, and maybe it will still happen today.
When I moved from Home Highway to ADSL way back at the beginning of time BT managed to leave me with no broadband and no phone on a Friday afternoon! :bawl:
Quote from: Steve on Jan 04, 2013, 18:24:24
It could be, but LLU swaps tend to be in office hours due to the lift and shift required.
Indeed and that's my experience unless the Openreach engineers are trying to clear a backlog or clock up some overtime ;D
How odd! Just got an e-mail from IDNet telling me my order has been completed!
Methinks BT may have cocked this one up well and truly. I'll try once more. I wonder which of my neighbours has just lost his broadband ;D
Interesting, I'm using a Billion 7800N router and if I disable IPv6 and enter my IDNet IPv4 number manually rather than relying on getting it automatically, everything works. How strange.
Anything different in router settings required other than username etc.
Maybe the cable has been labelled wrong
VPI should be 0 and VCI should be 38
All settings are correct. I'll try re-enabling IPv6. When I had the router set to get the IPv4 number automatically it did get the correct number.
Also set to PPPoA Adrian?
I was on Vivaciti for a time (O2 Wholesale) and the settings were the same as for a BT Wholesale connection but just worth checking.
Quote from: pctech on Jan 04, 2013, 18:20:46
I believe it can be up to 11.59 on the migration day.
Just to give them all time to sod off home for the weekend. ::)
Quote from: Simon on Jan 04, 2013, 19:00:39
Just to give them all time to sod off home for the weekend. ::)
As it's Friday and the first week of the year they probably clocked off at 2
Maybe Bernard Cribbins was waiting for a phone line to be installed when he wrote 'Right Said Fred' http://www.youtube.com/watch?v=z7Bvd33V9dQ
;D
The issue seems to be that if I enable IPv6 I still get sync and it seems to authenticate but then drops the connection, but maintains sync with the exchange.
Do IDNet automatically allocate IPv6 or is it something I need to request as I suspect it's the absence of an IPv6 number that is causing the problem?
Hi Adrian,
This is well over my head, but I don't know if it might help to pick the bones of this thread:
http://www.idnetters.co.uk/forums/index.php?topic=30007.0
The ipv6 is normally allocated automatically.
If you put your old details in now it still works ok Adrian?
You will get sync from the exchange but it sounds as though they've haven't done the cable move
I just did a traceroute to www.idnet.net and it went directly rather than through o-bit, the network Vivaciti use so I guess the move is complete.
Good news.
I wouldn't worry about IPv6 yet, that's another minefield, it works on IDNet with certain routers most of the time but with other makes of routers it's an episode of endless frustration.
The annoying thing is that Billion boast of the fact that the 7800N works with IDNet, but as you say, it's not a disaster if it doesn't work.
One of the reasons for moving back to IDNet was to get native IPv6, so I at least now have a little project to work on :)
Quote from: Adrian on Jan 04, 2013, 22:18:00
The annoying thing is that Billion boast of the fact that the 7800N works with IDNet, but as you say, it's not a disaster if it doesn't work.
One of the reasons for moving back to IDNet was to get native IPv6, so I at least now have a little project to work on :)
I bloody hope it does, I'm getting FTTC next Thursday and that's my router :D
The 7800N works with IPv6 and IDNet
I know it's working now as I'm typing this, and my last years worth of whinges :D
I wonder why I am having problems then :(
Check for updated firmware on the Billion site http://www.billion.uk.com/esupport/index.php?/Knowledgebase/List/Index/79/bipac-7800n
Quote from: Adrian on Jan 05, 2013, 12:37:02
I wonder why I am having problems then :(
It works automatically once enabled on the 7800N (no messing required), if it doesn't support have not yet allocated you any IPv6 addresses.
A bit of experimenting shows that I do sometimes get a brief connection, such as a few seconds, and I can briefly access a web site but only it would seem by IPv4, then I get disconnected. Once in a while I get a sustained connection but cannot access the internet from my Mac, so something clearly isn't right.
I have the latest router firmware but I will wait for a response from IDNet support, hopefully on Monday.
Hmm, Brian at IDNet confirmed that the IPv6 stuff is/was allocated at sign up. I have given him details of what I am seeing here but so far no reply.
I have reinstalled the 1.06g firmware and even gone back to 1.06f.dc1. I have tried factory resets but no change so I am now officially completely stumped.
In the immortal words of Blackadder, WIBBLE! ???
I'm running the later firmware but had no issues with the one your using.
My wan config IPv6 enable,IPv6 address ::, Obtain IPv6 address automatically, DNS - blank
IPv6 autoconfig- server enable,stateless
Latest firmware is 1.06g which I have, other settings are the same as yours, Steve.
I have just tried to reconnect with IPv6 and everything is working normally. Literally seconds later I had an e-mail from Brian at IDNet support to tell me they had allocated another IPv6 address range. Another e-mail has just told me that the problem seems to have been that original IPv6 range didn't look right.
Full marks to IDNet support :)
Thanks for letting us know. :thumb: