= Сообщение: 4622 из 7440 ============================================= IPV6 = От : Tony Langdon 3:633/410 26 Jun 17 08:37:00 Кому : Michiel van der Vlist 26 Jun 17 08:37:00 Тема : Re: List of IPv6 nodes FGHI : area://IPV6?msgid=3079.fido-ipv6@3:633/410+1db597ea На : area://IPV6?msgid=2:280/5555+594fc40a = Кодировка сообщения определена как: ASCII ================================== ============================================================================== -=> Michiel van der Vlist wrote to Tony Langdon <=-
TL> It's a bit of a challenge keeping anything going ATM. :/
MvV> Yeah, I could not help noticing that your IPv4 is unresponsive as well MvV> on occasion.
Yeah, one of the mobile links sometimes loses routing, and I have to reset the link to get it all working again. :(
TL>> Hopefully this will be resolved in the next few days.
MvV>> Indeed let us hope...
TL> Yes, it's up to the various telcos involved to sort out the mess now,
MvV> Various? As in "more than two"? It is not jus your Internet Access MvV> Provider that has problems?
The whole issue was a combination of 3 parties I suspect.
The ISP, who provide the service.
NBNCo, who own and manage the new broadband access network.
The telco who own the majority of exchanges and DSLAMS in the country.
Now, customers normally access ISPs via one of the access networks. In the past, that was owned by a small number of telcos (one of which owned most of the country, and a couple of smaller ones who had some equipment). The new network is owned by a government entity, NBNCo.
So what _should have happened is:
1. NBNCo to switch the pair from the exchange to the NBN VDSL port. This is done at the pillar across the road.
2. ISP ensure service can be delivered over the new feed.
3. Some time later, the old telco disconnects the line from the DSLAM port.
From what I can tell, something went wrong with the first step, and the changeover of the line didn't happen properly (it is still connected to the exchange getting dial tone and ADSL sync). The ISP, however, got word that it was done and initiated the rest of the process. Step 3 happened about 90 minutes after I got the text message saying all is good. Because the telco pulled the plug on the DSLAM, the line is now useless, except for phone calls and dialup, but there's no point putting a LAN on dialup not even sure if there is a dialin number these days), it was tough in the 90s with the much lower traffic back then, today it's totally impractical.
Hopefully I'll hear something within the next hour, now that it's Monday morning.
TL> before I can fix my AAAA records. :/ I can't even remove the AAAA TL> records, because access is so fragmented and limited. It really is TL> cobbled together! :)
MvV> Bugger...
Yah I don't have effective web access on the machines with the passwords. :/
