More Aussie Broadband Numptyness
The quality of aussiebroadband "support" /cough/ continues to amaze me, apparently, now they can not even read.
On Monday 27/1/25, my automated network monitoring and control scripting emailed me saying that it has disabled IPv6 on the router as it was repeatedly failing route testing (after 8hrs).
On Monday 27/1/25, my automated network monitoring and control scripting emailed me saying that it has disabled IPv6 on the router as it was repeatedly failing route testing (after 8hrs).
Despite automated down/up's and even a few reboots that the scripting randomly sleeps before taking actions, delaying more time between more actions and has action failure counts and blah blah blah before even dropping DSL failing over to 4G for a while then trying again, and blah blah blah, never mind, it's a complex long script I wrote back in my TPG days when some port cards were intermittently faulty.
Great to know my TPG days script still works though since I never actually noticed any problems until Christmas when I was on a VoIP call that dropped and wouldn't immediately re-establish, a little digging revealed the problems.
Anyway, it reported no response past the router for IPv6, so after other actions that failed it automatically disabled IPv6 and there it remained disabled until I manually re-enable it and suspend the cron job.
Since IPv4 is working fine (at present) I knew it wasn't NBN, it is not a local router issue, given I've got a few lying around (advantages of being in Telco) and tested a couple of them over Christmas (different brands/models) - the issues remained.
A traceroute shows nothing going past my router outbound, external inbound traceroutes show the routers assigned (WAN) IP address has a path to it, but the assigned LAN /48 subnet, does not, it appears to not go inside aussieBB's network, a friend in the U.S. also checked using his network and confirmed, he even suggested it's lost routes.
So now the Ticket
The Responses...
Please note, I have thus far no issue with the L 1 CSR, who IMO did his job, he saw the request, realised it needed to go up the chain and spoke to L 2 as he should, I'm pretty sure he is as dumbfounded as I am with L 2's response (I've highlighted in bold above what aussie broadband level 2 couldn't understand)
Un-fucking-believable.....
Anyway, ipv6 worked fine by looks of it until early afternoon Monday 27th Jan. (AEST). On Feb 9 they responded saying they ran ping plotter for a few days .. W T A F .. I'm also told they see data flow, NFI how, because the data sure as hell aint coming from here or getting to here, of course I asked if they were seeing this data flow to the routed subnet LAN IP (provided to them), and not on the assigned WAN IP - I got no response to that other than they have finally sent it to networking for them to take a look, if they see data on my routed /48, then it's dual assigned to also another customer, look, shit happens, I've seen this thing in the past, it can happen if there is no checks and balances and things go awry, so now we await the noc's response, if they say its routed, then my response will be to double check for a filter on the BNG, and check that there's also not a filter excluding it from BGP announces, because this is looking a little suss to me.
I'm not beyond considering my router is still at fault, but rebooted, reset, port reset, reconfigured, and problem remains, I mean, maybe my router has been infected by some AI secretly having a mind of its own and saying a big F.U. ignoring my configurations, really, I have, of course there is more of a chance of me being the sole powerball winner, but, yeah...
Feb 13 Well that was useless, the twats in NOC also can't read, want me to reboot my modem, kick my connection and see if that fixes it /sigh/ like I aint done that 20 times already...
I think its past a joke and is now time for the TIO, will also include my suspicions and exactly who they should be looking at.
On Feb 14, about 8PM ipv6 actually started working again - for about 2 hours, around 10PM it vanished back into the never ether.
I was able to do some traces from a server in the U.S. back to here, this shows why I'm adamant it's their network, be it a configuration error, or deliberate action (it's no secret my outspokenness about their IPv6 cluelessness has pissed some of them off, and I'm aware the name of one of them, who just happens to be in networking, just sayin...), but I am trying hard to give them the benefit of the doubt, just that, that gets harder to do as each day and response passes.
Inbound traceroute to ::10 when IPv6 was working
Inbound traceroute to ::10 when IPv6 stopped again 2 hours later
As you see, ABB network doesn't know where to send that /48s traffic, it's almost like it's pulled from iBGP.
Finally, February 21, I was right, it wasn't routed...
Last night I get a message that alludes to my IPOA not requesting the delegated range - WTF I said... I have run static IPv6 configuration for 3 years (along with static IPv4 which has only failed a few times) with these clowns using the /48 they issued me, and although they are clueless at rDNS delegating (remember how when you tried to enter a slave DNS server or update existing DNS's their form would on submit wipe out all your IPv6 ranges disabling IPv6 - and taking over a YEAR to fix it, yes, absolute n00bs) but since they fixed that IPv6 routing at least has worked - until 3 weeks ago, now after 3 years all of a sudden it seems I have to run dhcp delegation for them to issue and route the traffic to me, so despite their claims nothings changed, three weeks ago now, something did change in their network, and to top it off, they are now prefixing me a /64 on a range above what was assigned in my /48 to the servers - had this remained a /48 routing, or at least the first /64 in that /48, things would have resumed working hours before they did once changing my 3 year old static setting to delegated but it didn't because of the out of range narrower assignment, this was an annoyance, but an easy enough fix (since I disabled IPv6 on all but one device after this clusterfuck occurred, finally IPv6 has now been working for some 14 hours ... ohh darnit, now I've gone and jinxed it....
There is one positive thing about aussiebroadband, they make TPG and Telstra look absolutely amazing!
I'm glad their advertising has removed the No BS motto, because these fools are full of bullshit.
Great to know my TPG days script still works though since I never actually noticed any problems until Christmas when I was on a VoIP call that dropped and wouldn't immediately re-establish, a little digging revealed the problems.
Anyway, it reported no response past the router for IPv6, so after other actions that failed it automatically disabled IPv6 and there it remained disabled until I manually re-enable it and suspend the cron job.
Since IPv4 is working fine (at present) I knew it wasn't NBN, it is not a local router issue, given I've got a few lying around (advantages of being in Telco) and tested a couple of them over Christmas (different brands/models) - the issues remained.
A traceroute shows nothing going past my router outbound, external inbound traceroutes show the routers assigned (WAN) IP address has a path to it, but the assigned LAN /48 subnet, does not, it appears to not go inside aussieBB's network, a friend in the U.S. also checked using his network and confirmed, he even suggested it's lost routes.
So now the Ticket
/prompted ticket Q's removed, selected "other"/ This is not an NBN issue, it is an aussiebroadband issue. please have networking check to ensure my framed route exists for my ipv6 range. there is no ipv6 connectivity in or out bound, however the routers assigned IP does respond, but using third party shows there is no route to my /48 subnet. its been like this all week apparently according to logs. /traceroutes removed/ please have network ops ensure it is still assigned, or remove whatever filter was put in place last weekend, I have my suspicions but will give the benefit of doubt for time being.
The Responses...
Please note, I have thus far no issue with the L 1 CSR, who IMO did his job, he saw the request, realised it needed to go up the chain and spoke to L 2 as he should, I'm pretty sure he is as dumbfounded as I am with L 2's response (I've highlighted in bold above what aussie broadband level 2 couldn't understand)
Un-fucking-believable.....
Anyway, ipv6 worked fine by looks of it until early afternoon Monday 27th Jan. (AEST). On Feb 9 they responded saying they ran ping plotter for a few days .. W T A F .. I'm also told they see data flow, NFI how, because the data sure as hell aint coming from here or getting to here, of course I asked if they were seeing this data flow to the routed subnet LAN IP (provided to them), and not on the assigned WAN IP - I got no response to that other than they have finally sent it to networking for them to take a look, if they see data on my routed /48, then it's dual assigned to also another customer, look, shit happens, I've seen this thing in the past, it can happen if there is no checks and balances and things go awry, so now we await the noc's response, if they say its routed, then my response will be to double check for a filter on the BNG, and check that there's also not a filter excluding it from BGP announces, because this is looking a little suss to me.I'm not beyond considering my router is still at fault, but rebooted, reset, port reset, reconfigured, and problem remains, I mean, maybe my router has been infected by some AI secretly having a mind of its own and saying a big F.U. ignoring my configurations, really, I have, of course there is more of a chance of me being the sole powerball winner, but, yeah...
Feb 13 Well that was useless, the twats in NOC also can't read, want me to reboot my modem, kick my connection and see if that fixes it /sigh/ like I aint done that 20 times already...
I think its past a joke and is now time for the TIO, will also include my suspicions and exactly who they should be looking at.
On Feb 14, about 8PM ipv6 actually started working again - for about 2 hours, around 10PM it vanished back into the never ether.
I was able to do some traces from a server in the U.S. back to here, this shows why I'm adamant it's their network, be it a configuration error, or deliberate action (it's no secret my outspokenness about their IPv6 cluelessness has pissed some of them off, and I'm aware the name of one of them, who just happens to be in networking, just sayin...), but I am trying hard to give them the benefit of the doubt, just that, that gets harder to do as each day and response passes.
Inbound traceroute to ::10 when IPv6 was working
1 2602:ffc5:60::232 (2602:ffc5:60::232) 0.313 ms 0.135 ms 0.125 ms 2 2604:6600::275 (2604:6600::275) 1.648 ms 1.693 ms 1.541 ms 3 2604:6600:0:5::1 (2604:6600:0:5::1) 4.158 ms 4.041 ms 3.999 ms 4 2604:6600:ffff::2 (2604:6600:ffff::2) 0.569 ms 2604:6600:ffff::7 (2604:6600:ffff::7) 0.471 ms 2604:6600:ffff::2 (2604:6600:ffff::2) 0.573 ms 5 hu0-6-0-27.ccr41.lax04.atlas.cogentco.com (2001:550:2:18::60:1) 1.373 ms * ae5-244.cr8-lax2.ip6.gtt.net (2001:668:0:3:ffff:2:0:7a9) 1.181 ms 6 ae6.edge7.lax1.sp.lumen.tech (2001:1900:4:3::501) 1.137 ms 2.330 ms 2001:550:2:18::18d:2 (2001:550:2:18::18d:2) 0.956 ms 7 HundredGigE0-0-0-21.bng1.454stp.qld.aussiebb.net (2403:5800:1701:8::2) 151.529 ms HundredGigE0-0-0-20.bng1.454stp.qld.aussiebb.net (2403:5800:1701:7::2) 151.476 ms 151.330 ms 8 2403-580a-7fff-1f3e-cc6f-52fc-f803-54ed.ip6.aussiebb.net (2403:580a:7fff:1f3e:cc6f:52fc:f803:54ed) 156.018 ms !X 155.831 ms !X 155.505 ms !Xignore the !X, that's because of ::10s firewall, the same firewall that's worked for years.
Inbound traceroute to ::10 when IPv6 stopped again 2 hours later
1 2602:ffc5:60::232 (2602:ffc5:60::232) 0.185 ms 0.091 ms 0.074 ms 2 2604:6600::275 (2604:6600::275) 1.775 ms 1.753 ms 1.848 ms 3 2604:6600:0:5::1 (2604:6600:0:5::1) 20.723 ms 3.353 ms 20.555 ms 4 2604:6600:ffff::7 (2604:6600:ffff::7) 3.982 ms 2604:6600:ffff::2 (2604:6600:ffff::2) 0.598 ms 2604:6600:ffff::7 (2604:6600:ffff::7) 0.419 ms 5 ae5-244.cr8-lax2.ip6.gtt.net (2001:668:0:3:ffff:2:0:7a9) 1.482 ms 1.387 ms * 6 ae6.edge7.lax1.sp.lumen.tech (2001:1900:4:3::501) 0.796 ms 2001:550:2:18::18d:2 (2001:550:2:18::18d:2) 1.070 ms ae6.edge7.lax1.sp.lumen.tech (2001:1900:4:3::501) 0.611 ms 7 *** 8 * AUSSIE-BROA.ear6.LosAngeles1.Level3.net (2001:1900:2100:31::354e) 0.855 ms 1.003 ms 9 *** 10 ***
As you see, ABB network doesn't know where to send that /48s traffic, it's almost like it's pulled from iBGP.
Finally, February 21, I was right, it wasn't routed...
Last night I get a message that alludes to my IPOA not requesting the delegated range - WTF I said... I have run static IPv6 configuration for 3 years (along with static IPv4 which has only failed a few times) with these clowns using the /48 they issued me, and although they are clueless at rDNS delegating (remember how when you tried to enter a slave DNS server or update existing DNS's their form would on submit wipe out all your IPv6 ranges disabling IPv6 - and taking over a YEAR to fix it, yes, absolute n00bs) but since they fixed that IPv6 routing at least has worked - until 3 weeks ago, now after 3 years all of a sudden it seems I have to run dhcp delegation for them to issue and route the traffic to me, so despite their claims nothings changed, three weeks ago now, something did change in their network, and to top it off, they are now prefixing me a /64 on a range above what was assigned in my /48 to the servers - had this remained a /48 routing, or at least the first /64 in that /48, things would have resumed working hours before they did once changing my 3 year old static setting to delegated but it didn't because of the out of range narrower assignment, this was an annoyance, but an easy enough fix (since I disabled IPv6 on all but one device after this clusterfuck occurred, finally IPv6 has now been working for some 14 hours ... ohh darnit, now I've gone and jinxed it....
There is one positive thing about aussiebroadband, they make TPG and Telstra look absolutely amazing!
I'm glad their advertising has removed the No BS motto, because these fools are full of bullshit.
Related Articles
Trackbacks
No Trackbacks
Comments
Display comments as Linear | Threaded
Tony the Newtwork Engineer on :
time for you to do what you should have done last time and go to TIO, reem them, go to talk back media as well so people can get to know the real aussie broadband, rather than the choir kids they make themselves out to be in their publicity ads
Alyssa Thomissen on :
NoelB on :
Anyways an update it's now Feb 26 and ipv6 has been running fine for several days, I've not told them this because I'm giving it a week to see how stable it is, I'd demand to know why I had to make this change from static to dhcp delegated, but they'll tell me " nothings changed" when I know bloody well it has, hell, I don't even know if the /64 I've got now is permanent, my portal login still says I've a /48 subnet - if thats even still true, but lets play along and say it is, if the NBN goes down, and I have to resync fresh, will I still have this same /64 I have now or will that change to another /64 inside the 48, who the hell knows... They sure as fuck don't.