From spoofer-info at caida.org  Mon Sep  9 03:00:28 2024
From: spoofer-info at caida.org (CAIDA Spoofer Project)
Date: Sun, 8 Sep 2024 10:00:28 -0700
Subject: [AusNOG] Spoofer Report for AusNOG for Aug 2024
Message-ID: <1725814828.901692.31957.nullmailer@caida.org>

In response to feedback from operational security communities,
CAIDA's source address validation measurement project
(https://spoofer.caida.org) is automatically generating monthly
reports of ASes originating prefixes in BGP for systems from which
we received packets with a spoofed source address.
We are publishing these reports to network and security operations
lists in order to ensure this information reaches operational
contacts in these ASes.

This report summarises tests conducted within aus.

Inferred improvements during Aug 2024:
 none inferred

Source Address Validation issues inferred during Aug 2024:
ASN    Name                           First-Spoofed Last-Spoofed
4804   MPX                               2024-03-19   2024-08-14

Further information for these tests where we received spoofed
packets is available at:
https://spoofer.caida.org/recent_tests.php?country_include=aus&no_block=1

Please send any feedback or suggestions to spoofer-info at caida.org

From mitchkelly24 at gmail.com  Wed Sep 18 10:55:39 2024
From: mitchkelly24 at gmail.com (Mitch Kelly)
Date: Wed, 18 Sep 2024 08:55:39 +0800
Subject: [AusNOG] QSFP 100GE CU1M
Message-ID: <CAKZcER6HA29jx+6CSmMMj-jh_kahzKmvNnhxge5tNrsFTwQBcQ@mail.gmail.com>

Hi,

Would anyone have 2x QSFP 100GE CU1M Cables in Perth I could borrow for a
week or two?
Needed Urgently

Mitch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240918/7cccc129/attachment.htm>

From christian.heinrich at cmlh.id.au  Thu Sep 19 11:48:42 2024
From: christian.heinrich at cmlh.id.au (Christian Heinrich)
Date: Thu, 19 Sep 2024 11:18:42 +0930
Subject: [AusNOG] Security contact at Internode/iiNet/TPG
In-Reply-To: <CAOu9xNKjKTvhdtfzergY47_L9mqwDmOKuwwDg9it9B0umUCojg@mail.gmail.com>
References: <CAOu9xNKjKTvhdtfzergY47_L9mqwDmOKuwwDg9it9B0umUCojg@mail.gmail.com>
Message-ID: <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>

Robert,

On Mon, 5 Feb 2024 at 08:34, Robert Hudson <hudrob at gmail.com> wrote:
> I've emailed abuse at intenode but it bounces with a content warning.
> There's a phishing and MFA issue that I suspect someone there should
> know about.

Did you receive a contact at TPG that you can pass on?


-- 
Regards,
Christian Heinrich

http://cmlh.id.au/contact

From Phil.Hunt at one.nz  Thu Sep 19 15:14:51 2024
From: Phil.Hunt at one.nz (Phil Hunt)
Date: Thu, 19 Sep 2024 05:14:51 +0000
Subject: [AusNOG] Security contact at Internode/iiNet/TPG
In-Reply-To: <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
References: <CAOu9xNKjKTvhdtfzergY47_L9mqwDmOKuwwDg9it9B0umUCojg@mail.gmail.com>
 <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
Message-ID: <ME3PR01MB8196BBA27BAC6B84822FC83390632@ME3PR01MB8196.ausprd01.prod.outlook.com>

Hi Christian, you can try techsec at tpgtelecom.com.au<mailto:techsec at tpgtelecom.com.au>








C2 General

From: AusNOG <ausnog-bounces at lists.ausnog.net> On Behalf Of Christian Heinrich
Sent: Thursday, September 19, 2024 1:49 PM
To: Robert Hudson <hudrob at gmail.com>
Cc: AusNOG at lists.ausnog.net
Subject: Re: [AusNOG] Security contact at Internode/iiNet/TPG

Robert, On Mon, 5 Feb 2024 at 08:?34, Robert Hudson <hudrob@?gmail.?com> wrote: > I've emailed abuse@?intenode but it bounces with a content warning. > There's a phishing and MFA issue that I suspect someone there should > know about.?
ZjQcmQRYFpfptBannerStart
This Email Is From an Untrusted Sender
CYBER SECURITY WARNING: You have not previously corresponded with this sender. Please follow the Cyber Code and report suspicious emails.
ZjQcmQRYFpfptBannerEnd

Robert,



On Mon, 5 Feb 2024 at 08:34, Robert Hudson <hudrob at gmail.com<mailto:hudrob at gmail.com>> wrote:

> I've emailed abuse at intenode but it bounces with a content warning.

> There's a phishing and MFA issue that I suspect someone there should

> know about.



Did you receive a contact at TPG that you can pass on?





--

Regards,

Christian Heinrich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240919/7fad6b19/attachment-0001.htm>

From christian.heinrich at cmlh.id.au  Fri Sep 20 06:08:38 2024
From: christian.heinrich at cmlh.id.au (Christian Heinrich)
Date: Fri, 20 Sep 2024 05:38:38 +0930
Subject: [AusNOG] Security contact at Internode/iiNet/TPG
In-Reply-To: <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
References: <CAOu9xNKjKTvhdtfzergY47_L9mqwDmOKuwwDg9it9B0umUCojg@mail.gmail.com>
 <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
Message-ID: <CAGKxTUTOCGjrvNYCvW+1qYXMk+Q7oCgHanFRhi+5yYr3EJxeVA@mail.gmail.com>

On Thu, 19 Sept 2024 at 11:18, Christian Heinrich
<christian.heinrich at cmlh.id.au> wrote:
> Did you receive a contact at TPG that you can pass on?

Thanks Phil and Erik, I received an acknowledgement from their
techsec@ email address.


-- 
Regards,
Christian Heinrich

http://cmlh.id.au/contact

From hudrob at gmail.com  Fri Sep 20 07:22:35 2024
From: hudrob at gmail.com (Robert Hudson)
Date: Fri, 20 Sep 2024 07:22:35 +1000
Subject: [AusNOG] Security contact at Internode/iiNet/TPG
In-Reply-To: <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
References: <CAOu9xNKjKTvhdtfzergY47_L9mqwDmOKuwwDg9it9B0umUCojg@mail.gmail.com>
 <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
Message-ID: <CAOu9xNLWqWE4hxjjvot0ncMuMK0DUvBe1-6CtzfV0rEWMzn_zA@mail.gmail.com>

I didn't get any reply.

On Thu, 19 Sept 2024 at 11:48, Christian Heinrich <
christian.heinrich at cmlh.id.au> wrote:

> Robert,
>
> On Mon, 5 Feb 2024 at 08:34, Robert Hudson <hudrob at gmail.com> wrote:
> > I've emailed abuse at intenode but it bounces with a content warning.
> > There's a phishing and MFA issue that I suspect someone there should
> > know about.
>
> Did you receive a contact at TPG that you can pass on?
>
>
> --
> Regards,
> Christian Heinrich
>
> http://cmlh.id.au/contact
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240920/5dbd1b84/attachment.htm>

From adamwoodland at gmail.com  Sat Sep 21 13:28:03 2024
From: adamwoodland at gmail.com (Adam Woodland)
Date: Sat, 21 Sep 2024 13:28:03 +1000
Subject: [AusNOG] Security contact at Internode/iiNet/TPG
In-Reply-To: <CAOu9xNLWqWE4hxjjvot0ncMuMK0DUvBe1-6CtzfV0rEWMzn_zA@mail.gmail.com>
References: <CAOu9xNKjKTvhdtfzergY47_L9mqwDmOKuwwDg9it9B0umUCojg@mail.gmail.com>
 <CAGKxTUQzWhL9W3=YWQsOUuszw6aGyAbz14SkWBju=uYbT95JNQ@mail.gmail.com>
 <CAOu9xNLWqWE4hxjjvot0ncMuMK0DUvBe1-6CtzfV0rEWMzn_zA@mail.gmail.com>
Message-ID: <CAPYhV=iKa6K-aEi7cugD-drQ5TDQFBV+GX0uqdyM5bLQSwh02g@mail.gmail.com>

https://www.iinet.net.au/.well-known/security.txt (and the same info on the
TPG domain) lists vulnerability at tpgtelecom.com.au, if you haven't tried
that one yet.

Adam

On Fri, 20 Sept 2024 at 07:55, Robert Hudson <hudrob at gmail.com> wrote:

> I didn't get any reply.
>
> On Thu, 19 Sept 2024 at 11:48, Christian Heinrich <
> christian.heinrich at cmlh.id.au> wrote:
>
>> Robert,
>>
>> On Mon, 5 Feb 2024 at 08:34, Robert Hudson <hudrob at gmail.com> wrote:
>> > I've emailed abuse at intenode but it bounces with a content warning.
>> > There's a phishing and MFA issue that I suspect someone there should
>> > know about.
>>
>> Did you receive a contact at TPG that you can pass on?
>>
>>
>> --
>> Regards,
>> Christian Heinrich
>>
>> http://cmlh.id.au/contact
>>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240921/a32ea355/attachment.htm>

From sales at twig.com.au  Thu Sep 26 14:19:05 2024
From: sales at twig.com.au (TWIG Solutions)
Date: Thu, 26 Sep 2024 14:19:05 +1000
Subject: [AusNOG] Curly One
Message-ID: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>

Afternoon All,
 ? I have an issue with some of my clients, which I discovered while 
looking into the issue for 1 client.?? After testing from various other 
geographically and ISP diverse clients I discovered it's pretty wide 
spread issue.

The issue is that the website below will only display a blank white page 
for most clients, definitely ALL clients (I have tested) using 
Exetel/Superloop FTTN, FTTC and select FTTP.

https://fanaccount.axs.com.au/login

Yet some clients, when they view the site on the same laptop when at 
home (Telstra), it loads fine and shows a login page.? They come back to 
the office, and it wont.?? My own service when it was FTTC, didnt work, 
now I am FTTP it works.

I did some tracing and discovered that as soon as the data traverse a 
certain link,? it fails.?? I passed all my findings to Exetel/Superloop 
technical and it's been now been in hand since 25/6/24 and revived again 
on 26/8/24? (after the original ticket was closed with no resolution). ? 
Nor they are saying its a website issue, and they suggested installing a 
CORs extension on Chrome as it "fixed" it for them.? Not a secure 
solution, but I tested extension on 3 clients, still no good, and why 
only for some clients??.

So again I am waiting for responses, and? the initial client who 
reported to me is getting very p*ssed off with the delays.? They use the 
site a lot booking tickets for their clients etc...

Traces shown below, I wonder if anyone can test and advise, perhaps look 
at the traces you get if it does or doesn't work, as it seem 
Exetel/Superloop are stumped.


Cheers,

Mal

++++++++++++++++++++++++++++++++++++++++++++++++++++

*My Service ?? Working*
Service:? 1000/50 FTTP

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
over a maximum of 30 hops:

 ? 1??? <1 ms??? <1 ms??? <1 ms? [redacted]
 ? 2???? 4 ms???? 3 ms???? 4 ms?? [redacted]
 ? 3???? 2 ms???? 2 ms???? 2 ms? 202.90.206.198
 ? 4???? 3 ms???? 3 ms???? * 
*Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]*
 ? 5???? 3 ms???? 4 ms???? 8 ms? 27.122.122.15
 ? 6???? 4 ms???? 6 ms???? 3 ms? 108.162.247.77
 ? 7???? 3 ms???? 3 ms???? 3 ms? 172.64.151.20



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

*Client 1 ? Not Working*

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
[2606:4700:4400::6812:24ec]
over a maximum of 30 hops:

 ? 1???? *??????? *??????? *???? Request timed out.
 ? 2???? *??????? *??????? *???? Request timed out.
 ? 3??? 10 ms??? 10 ms??? 10 ms? [redacted]
 ? 4???? *??????? *?????? 11 ms? r0q86sqz1y5z2lmg941.ip6.superloop.au 
[2401:d000:3401::31]
 ? 5???? *?????? 10 ms???? * 
*bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
[2401:d000:10:100::2c1]*
 ? 6??? 32 ms??? 13 ms??? 24 ms? q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
[2401:d000:3202::12]
 ? 7??? 10 ms??? 10 ms??? 10 ms? 2400:cb00:26:3::
 ? 8??? 10 ms??? 10 ms??? 10 ms? 2606:4700:4400::6812:24ec

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

*
Initial Client - NOT WORKING *

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
[2606:4700:4400::6812:24ec]
over a maximum of 30 hops:

 ? 1???? *??????? *??????? *???? Request timed out.
 ? 2???? *??????? *??????? *???? Request timed out.
 ? 3???? 9 ms???? 9 ms???? 9 ms? 2406:3400:0:1::1
 ? 4???? *??????? *??????? *???? Request timed out.
 ? 5???? 9 ms???? 9 ms???? * 
*bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
[2401:d000:10:100::2c1]*
 ? 6??? 17 ms??? 24 ms??? 21 ms? q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
[2401:d000:3202::12]
 ? 7??? 10 ms???? 9 ms???? 9 ms? 2400:cb00:491:3::
 ? 8???? 9 ms???? 9 ms???? 9 ms? 2606:4700:4400::6812:24ec


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


*Client 2 ? Not Working*

Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32 
bytes of data:
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58

Ping statistics for 172.64.151.20:
 ??? Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
 ??? Minimum = 13ms, Maximum = 13ms, Average = 13ms


Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
over a maximum of 30 hops:

 ? 1??? <1 ms??? <1 ms??? <1 ms?? [redacted]
 ? 2??? 12 ms??? 12 ms??? 12 ms?? [redacted]
 ? 3??? 13 ms??? 13 ms??? 13 ms? 10.1.23.54 [10.1.23.54]
 ? 4??? 13 ms??? 13 ms??? 12 ms 
Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
 ? 5??? 13 ms???? *?????? 13 ms 
*Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]*
 ? 6??? 13 ms??? 13 ms??? 14 ms? 27.122.122.15
 ? 7??? 14 ms??? 13 ms??? 13 ms? 108.162.250.5
 ? 8??? 13 ms??? 13 ms??? 13 ms? 172.64.151.20


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


*Client 3 ? Not Working*

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
over a maximum of 30 hops:

 ? 1??? <1 ms??? <1 ms??? <1 ms?? [redacted]
 ? 2???? 1 ms???? 2 ms???? 1 ms?? [redacted]
 ? 3???? 2 ms???? 2 ms???? 2 ms? 10.1.21.186
 ? 4???? 2 ms???? 2 ms???? 1 ms 
Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
 ? 5???? 2 ms???? 1 ms???? 2 ms 
*Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]*
 ? 6???? 3 ms???? 2 ms???? 5 ms? 27.122.122.15
 ? 7???? 3 ms???? 3 ms???? 2 ms? 108.162.247.83
 ? 8???? 3 ms???? 2 ms???? 2 ms? 104.18.36.236



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/5dd4b815/attachment.htm>

From Nathan.Brookfield at iperium.com.au  Thu Sep 26 14:35:23 2024
From: Nathan.Brookfield at iperium.com.au (Nathan Brookfield)
Date: Thu, 26 Sep 2024 04:35:23 +0000
Subject: [AusNOG] Curly One
In-Reply-To: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
Message-ID: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>

What do the backend website owners AXS and Cloudflare have to say, I?d strongly suggest if your get a white page it?s nothing to do with the ISP?s you mentioned, also it loads fine here on all of the networks I manage.

From: AusNOG <ausnog-bounces at lists.ausnog.net> on behalf of TWIG Solutions <sales at twig.com.au>
Date: Thursday, 26 September 2024 at 14:19
To: AusNOG at lists.ausnog.net <AusNOG at lists.ausnog.net>
Subject: [AusNOG] Curly One
Afternoon All,
  I have an issue with some of my clients, which I discovered while looking into the issue for 1 client.   After testing from various other geographically and ISP diverse clients I discovered it's pretty wide spread issue.

The issue is that the website below will only display a blank white page for most clients, definitely ALL clients (I have tested) using Exetel/Superloop FTTN, FTTC and select FTTP.

https://fanaccount.axs.com.au/login<https://fanaccount.axs.com.au/>

Yet some clients, when they view the site on the same laptop when at home (Telstra), it loads fine and shows a login page.  They come back to the office, and it wont.   My own service when it was FTTC, didnt work, now I am FTTP it works.

I did some tracing and discovered that as soon as the data traverse a certain link,  it fails.   I passed all my findings to Exetel/Superloop technical and it's been now been in hand since 25/6/24 and revived again on 26/8/24  (after the original ticket was closed with no resolution).   Nor they are saying its a website issue, and they suggested installing a CORs extension on Chrome as it "fixed" it for them.  Not a secure solution, but I tested extension on 3 clients, still no good, and why only for some clients??.

So again I am waiting for responses, and  the initial client who reported to me is getting very p*ssed off with the delays.  They use the site a lot booking tickets for their clients etc...

Traces shown below, I wonder if anyone can test and advise, perhaps look at the traces you get if it does or doesn't work, as it seem Exetel/Superloop are stumped.


Cheers,

Mal

++++++++++++++++++++++++++++++++++++++++++++++++++++

My Service    Working
Service:  1000/50 FTTP

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2     4 ms     3 ms     4 ms   [redacted]
  3     2 ms     2 ms     2 ms  202.90.206.198
  4     3 ms     3 ms     *     Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]
  5     3 ms     4 ms     8 ms  27.122.122.15
  6     4 ms     6 ms     3 ms  108.162.247.77
  7     3 ms     3 ms     3 ms  172.64.151.20



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Client 1   Not Working

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [2606:4700:4400::6812:24ec]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3    10 ms    10 ms    10 ms  [redacted]
  4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au [2401:d000:3401::31]
  5     *       10 ms     *     bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co [2401:d000:10:100::2c1]
  6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au [2401:d000:3202::12]
  7    10 ms    10 ms    10 ms  2400:cb00:26:3::
  8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Initial Client - NOT WORKING

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [2606:4700:4400::6812:24ec]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  2406:3400:0:1::1
  4     *        *        *     Request timed out.
  5     9 ms     9 ms     *     bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co [2401:d000:10:100::2c1]
  6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au [2401:d000:3202::12]
  7    10 ms     9 ms     9 ms  2400:cb00:491:3::
  8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Client 2   Not Working

Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32 bytes of data:
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58

Ping statistics for 172.64.151.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 13ms, Average = 13ms


Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [redacted]
  2    12 ms    12 ms    12 ms   [redacted]
  3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
  4    13 ms    13 ms    12 ms  Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
  5    13 ms     *       13 ms  Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
  6    13 ms    13 ms    14 ms  27.122.122.15
  7    14 ms    13 ms    13 ms  108.162.250.5
  8    13 ms    13 ms    13 ms  172.64.151.20


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Client 3   Not Working

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [redacted]
  2     1 ms     2 ms     1 ms   [redacted]
  3     2 ms     2 ms     2 ms  10.1.21.186
  4     2 ms     2 ms     1 ms  Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
  5     2 ms     1 ms     2 ms  Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
  6     3 ms     2 ms     5 ms  27.122.122.15
  7     3 ms     3 ms     2 ms  108.162.247.83
  8     3 ms     2 ms     2 ms  104.18.36.236







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/85a25e8a/attachment.htm>

From sr at cloudflare.com  Thu Sep 26 14:48:22 2024
From: sr at cloudflare.com (Shane Renshaw)
Date: Thu, 26 Sep 2024 04:48:22 +0000
Subject: [AusNOG] Curly One
In-Reply-To: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <CAKWLbw0bGyPvqeF2+26ScgaconzOncUaDkOREXHbJuzO=9UfQg@mail.gmail.com>

White pages like that are rarely on the eyeball network side if they are
network issues. Its often something on the client or the server side

Im not able to replicate it, I would be worth raising it with AXS who can
see the whole story of the issue.

*Shane Renshaw* | Manager - Edge Network Engineering APAC
sr at cloudflare.com | as13335.peeringdb.com
Location: Melbourne, Australia

[image: Cloudflare] <https://www.cloudflare.com/>

1 888 99 FLARE | www.cloudflare.com


On Thu, Sep 26, 2024 at 4:35?AM Nathan Brookfield <
Nathan.Brookfield at iperium.com.au> wrote:

> What do the backend website owners AXS and Cloudflare have to say, I?d
> strongly suggest if your get a white page it?s nothing to do with the ISP?s
> you mentioned, also it loads fine here on all of the networks I manage.
>
>
>
> *From: *AusNOG <ausnog-bounces at lists.ausnog.net> on behalf of TWIG
> Solutions <sales at twig.com.au>
> *Date: *Thursday, 26 September 2024 at 14:19
> *To: *AusNOG at lists.ausnog.net <AusNOG at lists.ausnog.net>
> *Subject: *[AusNOG] Curly One
>
> Afternoon All,
>   I have an issue with some of my clients, which I discovered while
> looking into the issue for 1 client.   After testing from various other
> geographically and ISP diverse clients I discovered it's pretty wide spread
> issue.
>
> The issue is that the website below will only display a blank white page
> for most clients, definitely ALL clients (I have tested) using
> Exetel/Superloop FTTN, FTTC and select FTTP.
>
> https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>
> Yet some clients, when they view the site on the same laptop when at home
> (Telstra), it loads fine and shows a login page.  They come back to the
> office, and it wont.   My own service when it was FTTC, didnt work, now I
> am FTTP it works.
>
> I did some tracing and discovered that as soon as the data traverse a
> certain link,  it fails.   I passed all my findings to Exetel/Superloop
> technical and it's been now been in hand since 25/6/24 and revived again on
> 26/8/24  (after the original ticket was closed with no resolution).   Nor
> they are saying its a website issue, and they suggested installing a CORs
> extension on Chrome as it "fixed" it for them.  Not a secure solution, but
> I tested extension on 3 clients, still no good, and why only for some
> clients??.
>
> So again I am waiting for responses, and  the initial client who reported
> to me is getting very p*ssed off with the delays.  They use the site a lot
> booking tickets for their clients etc...
>
> Traces shown below, I wonder if anyone can test and advise, perhaps look
> at the traces you get if it does or doesn't work, as it seem
> Exetel/Superloop are stumped.
>
>
> Cheers,
>
> Mal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *My Service    Working*
> Service:  1000/50 FTTP
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms  [redacted]
>   2     4 ms     3 ms     4 ms   [redacted]
>   3     2 ms     2 ms     2 ms  202.90.206.198
>   4     3 ms     3 ms     *     *Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.65]*
>   5     3 ms     4 ms     8 ms  27.122.122.15
>   6     4 ms     6 ms     3 ms  108.162.247.77
>   7     3 ms     3 ms     3 ms  172.64.151.20
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *Client 1   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3    10 ms    10 ms    10 ms  [redacted]
>   4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au
> [2401:d000:3401::31]
>   5     *       10 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms    10 ms    10 ms  2400:cb00:26:3::
>   8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> * Initial Client - NOT WORKING *
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3     9 ms     9 ms     9 ms  2406:3400:0:1::1
>   4     *        *        *     Request timed out.
>   5     9 ms     9 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms     9 ms     9 ms  2400:cb00:491:3::
>   8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 2   Not Working*
>
> Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32
> bytes of data:
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>
> Ping statistics for 172.64.151.20:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 13ms, Maximum = 13ms, Average = 13ms
>
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2    12 ms    12 ms    12 ms   [redacted]
>   3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
>   4    13 ms    13 ms    12 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5    13 ms     *       13 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6    13 ms    13 ms    14 ms  27.122.122.15
>   7    14 ms    13 ms    13 ms  108.162.250.5
>   8    13 ms    13 ms    13 ms  172.64.151.20
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 3   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2     1 ms     2 ms     1 ms   [redacted]
>   3     2 ms     2 ms     2 ms  10.1.21.186
>   4     2 ms     2 ms     1 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5     2 ms     1 ms     2 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6     3 ms     2 ms     5 ms  27.122.122.15
>   7     3 ms     3 ms     2 ms  108.162.247.83
>   8     3 ms     2 ms     2 ms  104.18.36.236
>
>
>
>
>
>
>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/f6c51fce/attachment.htm>

From jhellenthal at dataix.net  Thu Sep 26 14:49:54 2024
From: jhellenthal at dataix.net (J. Hellenthal)
Date: Wed, 25 Sep 2024 23:49:54 -0500
Subject: [AusNOG] Curly One
In-Reply-To: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
References: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <6D223212-1E43-4175-BFD3-14F4FB3EEDDD@dataix.net>

An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240925/128136f7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image0.png
Type: image/png
Size: 196875 bytes
Desc: not available
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240925/128136f7/attachment-0001.png>

From shaun at kadeo.com.au  Thu Sep 26 14:57:12 2024
From: shaun at kadeo.com.au (Shaun D)
Date: Thu, 26 Sep 2024 04:57:12 +0000
Subject: [AusNOG] Curly One
In-Reply-To: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <SY5P282MB46459E485D1923138E8D37A28A6A2@SY5P282MB4645.AUSP282.PROD.OUTLOOK.COM>

The ?blank page? returns HTML with a JS App which won?t start due to what looks like a 403 from an API.

[cid:image001.png at 01DB1023.B2EABE70]

As someone with experience in both camps (software dev, built ISPs), I?d agree with Nathan that Exetel is a red herring and that the above 403 is causing the blank page.

The specific API endpoint above https://api.axs.com/v1/fanskin/myaxs/17?access_token=XnFpNJG7cLxg1Tqz9PMg8H1CYKc could have something that does IP lookups or whatever.

The fact that the above domain is axs.com and the URL above is axs.com.au does mean that it would be ?cross-origin?, which is why installing a CORS plugin was a workaround. If the server responds with the correct CORS headers, it may work.


From: AusNOG <ausnog-bounces at lists.ausnog.net> on behalf of Nathan Brookfield <Nathan.Brookfield at iperium.com.au>
Date: Thursday, 26 September 2024 at 2:36?pm
To: sales at twig.com.au <sales at twig.com.au>, AusNOG at lists.ausnog.net <AusNOG at lists.ausnog.net>
Subject: Re: [AusNOG] Curly One
What do the backend website owners AXS and Cloudflare have to say, I?d strongly suggest if your get a white page it?s nothing to do with the ISP?s you mentioned, also it loads fine here on all of the networks I manage.

From: AusNOG <ausnog-bounces at lists.ausnog.net> on behalf of TWIG Solutions <sales at twig.com.au>
Date: Thursday, 26 September 2024 at 14:19
To: AusNOG at lists.ausnog.net <AusNOG at lists.ausnog.net>
Subject: [AusNOG] Curly One
Afternoon All,
  I have an issue with some of my clients, which I discovered while looking into the issue for 1 client.   After testing from various other geographically and ISP diverse clients I discovered it's pretty wide spread issue.

The issue is that the website below will only display a blank white page for most clients, definitely ALL clients (I have tested) using Exetel/Superloop FTTN, FTTC and select FTTP.

https://fanaccount.axs.com.au/login<https://fanaccount.axs.com.au/>

Yet some clients, when they view the site on the same laptop when at home (Telstra), it loads fine and shows a login page.  They come back to the office, and it wont.   My own service when it was FTTC, didnt work, now I am FTTP it works.

I did some tracing and discovered that as soon as the data traverse a certain link,  it fails.   I passed all my findings to Exetel/Superloop technical and it's been now been in hand since 25/6/24 and revived again on 26/8/24  (after the original ticket was closed with no resolution).   Nor they are saying its a website issue, and they suggested installing a CORs extension on Chrome as it "fixed" it for them.  Not a secure solution, but I tested extension on 3 clients, still no good, and why only for some clients??.

So again I am waiting for responses, and  the initial client who reported to me is getting very p*ssed off with the delays.  They use the site a lot booking tickets for their clients etc...

Traces shown below, I wonder if anyone can test and advise, perhaps look at the traces you get if it does or doesn't work, as it seem Exetel/Superloop are stumped.


Cheers,

Mal

++++++++++++++++++++++++++++++++++++++++++++++++++++

My Service    Working
Service:  1000/50 FTTP

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  [redacted]
  2     4 ms     3 ms     4 ms   [redacted]
  3     2 ms     2 ms     2 ms  202.90.206.198
  4     3 ms     3 ms     *     Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]
  5     3 ms     4 ms     8 ms  27.122.122.15
  6     4 ms     6 ms     3 ms  108.162.247.77
  7     3 ms     3 ms     3 ms  172.64.151.20



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Client 1   Not Working

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [2606:4700:4400::6812:24ec]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3    10 ms    10 ms    10 ms  [redacted]
  4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au [2401:d000:3401::31]
  5     *       10 ms     *     bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co [2401:d000:10:100::2c1]
  6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au [2401:d000:3202::12]
  7    10 ms    10 ms    10 ms  2400:cb00:26:3::
  8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Initial Client - NOT WORKING

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [2606:4700:4400::6812:24ec]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  2406:3400:0:1::1
  4     *        *        *     Request timed out.
  5     9 ms     9 ms     *     bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co [2401:d000:10:100::2c1]
  6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au [2401:d000:3202::12]
  7    10 ms     9 ms     9 ms  2400:cb00:491:3::
  8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Client 2   Not Working

Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32 bytes of data:
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
Reply from 172.64.151.20: bytes=32 time=13ms TTL=58

Ping statistics for 172.64.151.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 13ms, Average = 13ms


Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [redacted]
  2    12 ms    12 ms    12 ms   [redacted]
  3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
  4    13 ms    13 ms    12 ms  Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
  5    13 ms     *       13 ms  Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
  6    13 ms    13 ms    14 ms  27.122.122.15
  7    14 ms    13 ms    13 ms  108.162.250.5
  8    13 ms    13 ms    13 ms  172.64.151.20


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Client 3   Not Working

Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms   [redacted]
  2     1 ms     2 ms     1 ms   [redacted]
  3     2 ms     2 ms     2 ms  10.1.21.186
  4     2 ms     2 ms     1 ms  Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
  5     2 ms     1 ms     2 ms  Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
  6     3 ms     2 ms     5 ms  27.122.122.15
  7     3 ms     3 ms     2 ms  108.162.247.83
  8     3 ms     2 ms     2 ms  104.18.36.236







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/2bd5ec19/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001[39].png
Type: image/png
Size: 130304 bytes
Desc: image001[39].png
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/2bd5ec19/attachment-0001.png>

From pat at ge3k.net  Thu Sep 26 14:58:28 2024
From: pat at ge3k.net (Patrick Ohearn)
Date: Thu, 26 Sep 2024 14:58:28 +1000
Subject: [AusNOG] Curly One
In-Reply-To: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
Message-ID: <CAGyKTFsrpYYZZABa763q+UkULdOr2X_jTvH_z=Nz2ywfewo1Kg@mail.gmail.com>

You indicated a CORS disabling extension works around the issue, this
suggests that the issue is with the website operators CORS policy & how it
handles the failure of loading that response from a specific IP block
(likely geoip replated).

 Have you spoken to the end website operator about that failure of the CORS
policy, and how their CDN's (Cloudflare & Cloudfront) are handling geoip?

Regards,
Patrick.



On Thu, 26 Sept 2024 at 14:19, TWIG Solutions <sales at twig.com.au> wrote:

> Afternoon All,
>   I have an issue with some of my clients, which I discovered while
> looking into the issue for 1 client.   After testing from various other
> geographically and ISP diverse clients I discovered it's pretty wide spread
> issue.
>
> The issue is that the website below will only display a blank white page
> for most clients, definitely ALL clients (I have tested) using
> Exetel/Superloop FTTN, FTTC and select FTTP.
>
> https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>
> Yet some clients, when they view the site on the same laptop when at home
> (Telstra), it loads fine and shows a login page.  They come back to the
> office, and it wont.   My own service when it was FTTC, didnt work, now I
> am FTTP it works.
>
> I did some tracing and discovered that as soon as the data traverse a
> certain link,  it fails.   I passed all my findings to Exetel/Superloop
> technical and it's been now been in hand since 25/6/24 and revived again on
> 26/8/24  (after the original ticket was closed with no resolution).   Nor
> they are saying its a website issue, and they suggested installing a CORs
> extension on Chrome as it "fixed" it for them.  Not a secure solution, but
> I tested extension on 3 clients, still no good, and why only for some
> clients??.
>
> So again I am waiting for responses, and  the initial client who reported
> to me is getting very p*ssed off with the delays.  They use the site a lot
> booking tickets for their clients etc...
>
> Traces shown below, I wonder if anyone can test and advise, perhaps look
> at the traces you get if it does or doesn't work, as it seem
> Exetel/Superloop are stumped.
>
>
> Cheers,
>
> Mal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *My Service    Working*
> Service:  1000/50 FTTP
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms  [redacted]
>   2     4 ms     3 ms     4 ms   [redacted]
>   3     2 ms     2 ms     2 ms  202.90.206.198
>   4     3 ms     3 ms     *     *Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.65]*
>   5     3 ms     4 ms     8 ms  27.122.122.15
>   6     4 ms     6 ms     3 ms  108.162.247.77
>   7     3 ms     3 ms     3 ms  172.64.151.20
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *Client 1   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3    10 ms    10 ms    10 ms  [redacted]
>   4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au
> [2401:d000:3401::31]
>   5     *       10 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms    10 ms    10 ms  2400:cb00:26:3::
>   8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> * Initial Client - NOT WORKING *
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3     9 ms     9 ms     9 ms  2406:3400:0:1::1
>   4     *        *        *     Request timed out.
>   5     9 ms     9 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms     9 ms     9 ms  2400:cb00:491:3::
>   8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 2   Not Working*
>
> Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32
> bytes of data:
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>
> Ping statistics for 172.64.151.20:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 13ms, Maximum = 13ms, Average = 13ms
>
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2    12 ms    12 ms    12 ms   [redacted]
>   3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
>   4    13 ms    13 ms    12 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5    13 ms     *       13 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6    13 ms    13 ms    14 ms  27.122.122.15
>   7    14 ms    13 ms    13 ms  108.162.250.5
>   8    13 ms    13 ms    13 ms  172.64.151.20
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 3   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2     1 ms     2 ms     1 ms   [redacted]
>   3     2 ms     2 ms     2 ms  10.1.21.186
>   4     2 ms     2 ms     1 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5     2 ms     1 ms     2 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6     3 ms     2 ms     5 ms  27.122.122.15
>   7     3 ms     3 ms     2 ms  108.162.247.83
>   8     3 ms     2 ms     2 ms  104.18.36.236
>
>
>
>
>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog
>


-- 
0406884900
pat at ge3k.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/f2e416b2/attachment.htm>

From g2x at juliet.emu.st  Thu Sep 26 15:00:34 2024
From: g2x at juliet.emu.st (Mark Delany)
Date: Thu, 26 Sep 2024 05:00:34 +0000
Subject: [AusNOG] Curly One
In-Reply-To: <6D223212-1E43-4175-BFD3-14F4FB3EEDDD@dataix.net>
References: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
 <6D223212-1E43-4175-BFD3-14F4FB3EEDDD@dataix.net>
Message-ID: <0.2.0-final-1727326834.913-0x56f28b@qmda.emu.st>

First WAG is MTU issues. Second WAG is ipv4 vs ipv6.


Mark.

From sales at twig.com.au  Thu Sep 26 15:29:59 2024
From: sales at twig.com.au (TWIG Solutions)
Date: Thu, 26 Sep 2024 15:29:59 +1000
Subject: [AusNOG] Curly One
In-Reply-To: <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <4a06521a-2518-4170-af7b-73ec9b20ac93@twig.com.au>


 ?They have said there is no issue on the website end..




On 26/09/2024 14:35, Nathan Brookfield wrote:
>
> What do the backend website owners AXS and Cloudflare have to say, I?d 
> strongly suggest if your get a white page it?s nothing to do with the 
> ISP?s you mentioned, also it loads fine here on all of the networks I 
> manage.
>
> *From: *AusNOG <ausnog-bounces at lists.ausnog.net> on behalf of TWIG 
> Solutions <sales at twig.com.au>
> *Date: *Thursday, 26 September 2024 at 14:19
> *To: *AusNOG at lists.ausnog.net <AusNOG at lists.ausnog.net>
> *Subject: *[AusNOG] Curly One
>
> Afternoon All,
> ? I have an issue with some of my clients, which I discovered while 
> looking into the issue for 1 client. After testing from various other 
> geographically and ISP diverse clients I discovered it's pretty wide 
> spread issue.
>
> The issue is that the website below will only display a blank white 
> page for most clients, definitely ALL clients (I have tested) using 
> Exetel/Superloop FTTN, FTTC and select FTTP.
>
> https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>
> Yet some clients, when they view the site on the same laptop when at 
> home (Telstra), it loads fine and shows a login page.? They come back 
> to the office, and it wont.?? My own service when it was FTTC, didnt 
> work, now I am FTTP it works.
>
> I did some tracing and discovered that as soon as the data traverse a 
> certain link,? it fails.?? I passed all my findings to 
> Exetel/Superloop technical and it's been now been in hand since 
> 25/6/24 and revived again on 26/8/24? (after the original ticket was 
> closed with no resolution). ? Nor they are saying its a website issue, 
> and they suggested installing a CORs extension on Chrome as it "fixed" 
> it for them.? Not a secure solution, but I tested extension on 3 
> clients, still no good, and why only for some clients??.
>
> So again I am waiting for responses, and? the initial client who 
> reported to me is getting very p*ssed off with the delays.? They use 
> the site a lot booking tickets for their clients etc...
>
> Traces shown below, I wonder if anyone can test and advise, perhaps 
> look at the traces you get if it does or doesn't work, as it seem 
> Exetel/Superloop are stumped.
>
>
> Cheers,
>
> Mal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *My Service ?? Working*
> Service:? 1000/50 FTTP
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
> ? 1??? <1 ms??? <1 ms??? <1 ms? [redacted]
> ? 2???? 4 ms???? 3 ms???? 4 ms?? [redacted]
> ? 3???? 2 ms???? 2 ms???? 2 ms? 202.90.206.198
> ? 4???? 3 ms???? 3 ms???? * 
> *Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]*
> ? 5???? 3 ms???? 4 ms???? 8 ms? 27.122.122.15
> ? 6???? 4 ms???? 6 ms???? 3 ms? 108.162.247.77
> ? 7???? 3 ms???? 3 ms???? 3 ms? 172.64.151.20
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *Client 1 ? Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
> ? 1???? *??????? *??????? *???? Request timed out.
> ? 2???? *??????? *??????? *???? Request timed out.
> ? 3??? 10 ms??? 10 ms??? 10 ms? [redacted]
> ? 4???? *??????? *?????? 11 ms r0q86sqz1y5z2lmg941.ip6.superloop.au 
> [2401:d000:3401::31]
> ? 5???? *?????? 10 ms???? * 
> *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
> [2401:d000:10:100::2c1]*
> ? 6??? 32 ms??? 13 ms??? 24 ms q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
> [2401:d000:3202::12]
> ? 7??? 10 ms??? 10 ms??? 10 ms? 2400:cb00:26:3::
> ? 8??? 10 ms??? 10 ms??? 10 ms 2606:4700:4400::6812:24ec
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *
> Initial Client - NOT WORKING *
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
> ? 1???? *??????? *??????? *???? Request timed out.
> ? 2???? *??????? *??????? *???? Request timed out.
> ? 3???? 9 ms???? 9 ms???? 9 ms? 2406:3400:0:1::1
> ? 4???? *??????? *??????? *???? Request timed out.
> ? 5???? 9 ms???? 9 ms???? * 
> *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
> [2401:d000:10:100::2c1]*
> ? 6??? 17 ms??? 24 ms??? 21 ms q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
> [2401:d000:3202::12]
> ? 7??? 10 ms???? 9 ms???? 9 ms? 2400:cb00:491:3::
> ? 8???? 9 ms???? 9 ms???? 9 ms 2606:4700:4400::6812:24ec
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 2 ? Not Working*
>
> Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 
> 32 bytes of data:
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>
> Ping statistics for 172.64.151.20:
> ??? Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> ??? Minimum = 13ms, Maximum = 13ms, Average = 13ms
>
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
> ? 1??? <1 ms??? <1 ms??? <1 ms?? [redacted]
> ? 2??? 12 ms??? 12 ms??? 12 ms?? [redacted]
> ? 3??? 13 ms??? 13 ms??? 13 ms? 10.1.23.54 [10.1.23.54]
> ? 4??? 13 ms??? 13 ms??? 12 ms 
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
> ? 5??? 13 ms???? *?????? 13 ms 
> *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]*
> ? 6??? 13 ms??? 13 ms??? 14 ms? 27.122.122.15
> ? 7??? 14 ms??? 13 ms??? 13 ms? 108.162.250.5
> ? 8??? 13 ms??? 13 ms??? 13 ms? 172.64.151.20
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 3 ? Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
> over a maximum of 30 hops:
>
> ? 1??? <1 ms??? <1 ms??? <1 ms?? [redacted]
> ? 2???? 1 ms???? 2 ms???? 1 ms?? [redacted]
> ? 3???? 2 ms???? 2 ms???? 2 ms? 10.1.21.186
> ? 4???? 2 ms???? 2 ms???? 1 ms 
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
> ? 5???? 2 ms???? 1 ms???? 2 ms 
> *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]*
> ? 6???? 3 ms???? 2 ms???? 5 ms? 27.122.122.15
> ? 7???? 3 ms???? 3 ms???? 2 ms? 108.162.247.83
> ? 8???? 3 ms???? 2 ms???? 2 ms? 104.18.36.236
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/5e88f462/attachment.htm>

From lidder86 at gmail.com  Thu Sep 26 15:33:12 2024
From: lidder86 at gmail.com (Michael Baker)
Date: Thu, 26 Sep 2024 13:33:12 +0800
Subject: [AusNOG] Curly One
In-Reply-To: <4a06521a-2518-4170-af7b-73ec9b20ac93@twig.com.au>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <MEYP282MB2520242C70CE706032B7A50EDB6A2@MEYP282MB2520.AUSP282.PROD.OUTLOOK.COM>
 <4a06521a-2518-4170-af7b-73ec9b20ac93@twig.com.au>
Message-ID: <CAF3m+prDKvExd3CYROU6MRC81OR54im5EOb+W-HehGt+VTTkKA@mail.gmail.com>

If you getting a blank page open up  dev tools and look at console see what
errors come up? Maybe a third party cdn blocking assets

On Thu, 26 Sept 2024, 1:30?pm TWIG Solutions, <sales at twig.com.au> wrote:

>
>  They have said there is no issue on the website end..
>
>
>
> On 26/09/2024 14:35, Nathan Brookfield wrote:
>
> What do the backend website owners AXS and Cloudflare have to say, I?d
> strongly suggest if your get a white page it?s nothing to do with the ISP?s
> you mentioned, also it loads fine here on all of the networks I manage.
>
>
>
> *From: *AusNOG <ausnog-bounces at lists.ausnog.net>
> <ausnog-bounces at lists.ausnog.net> on behalf of TWIG Solutions
> <sales at twig.com.au> <sales at twig.com.au>
> *Date: *Thursday, 26 September 2024 at 14:19
> *To: *AusNOG at lists.ausnog.net <AusNOG at lists.ausnog.net>
> <AusNOG at lists.ausnog.net>
> *Subject: *[AusNOG] Curly One
>
> Afternoon All,
>   I have an issue with some of my clients, which I discovered while
> looking into the issue for 1 client.   After testing from various other
> geographically and ISP diverse clients I discovered it's pretty wide spread
> issue.
>
> The issue is that the website below will only display a blank white page
> for most clients, definitely ALL clients (I have tested) using
> Exetel/Superloop FTTN, FTTC and select FTTP.
>
> https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>
> Yet some clients, when they view the site on the same laptop when at home
> (Telstra), it loads fine and shows a login page.  They come back to the
> office, and it wont.   My own service when it was FTTC, didnt work, now I
> am FTTP it works.
>
> I did some tracing and discovered that as soon as the data traverse a
> certain link,  it fails.   I passed all my findings to Exetel/Superloop
> technical and it's been now been in hand since 25/6/24 and revived again on
> 26/8/24  (after the original ticket was closed with no resolution).   Nor
> they are saying its a website issue, and they suggested installing a CORs
> extension on Chrome as it "fixed" it for them.  Not a secure solution, but
> I tested extension on 3 clients, still no good, and why only for some
> clients??.
>
> So again I am waiting for responses, and  the initial client who reported
> to me is getting very p*ssed off with the delays.  They use the site a lot
> booking tickets for their clients etc...
>
> Traces shown below, I wonder if anyone can test and advise, perhaps look
> at the traces you get if it does or doesn't work, as it seem
> Exetel/Superloop are stumped.
>
>
> Cheers,
>
> Mal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *My Service    Working*
> Service:  1000/50 FTTP
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms  [redacted]
>   2     4 ms     3 ms     4 ms   [redacted]
>   3     2 ms     2 ms     2 ms  202.90.206.198
>   4     3 ms     3 ms     *     *Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.65]*
>   5     3 ms     4 ms     8 ms  27.122.122.15
>   6     4 ms     6 ms     3 ms  108.162.247.77
>   7     3 ms     3 ms     3 ms  172.64.151.20
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *Client 1   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3    10 ms    10 ms    10 ms  [redacted]
>   4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au
> [2401:d000:3401::31]
>   5     *       10 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms    10 ms    10 ms  2400:cb00:26:3::
>   8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> * Initial Client - NOT WORKING *
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3     9 ms     9 ms     9 ms  2406:3400:0:1::1
>   4     *        *        *     Request timed out.
>   5     9 ms     9 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms     9 ms     9 ms  2400:cb00:491:3::
>   8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 2   Not Working*
>
> Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32
> bytes of data:
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>
> Ping statistics for 172.64.151.20:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 13ms, Maximum = 13ms, Average = 13ms
>
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2    12 ms    12 ms    12 ms   [redacted]
>   3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
>   4    13 ms    13 ms    12 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5    13 ms     *       13 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6    13 ms    13 ms    14 ms  27.122.122.15
>   7    14 ms    13 ms    13 ms  108.162.250.5
>   8    13 ms    13 ms    13 ms  172.64.151.20
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 3   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2     1 ms     2 ms     1 ms   [redacted]
>   3     2 ms     2 ms     2 ms  10.1.21.186
>   4     2 ms     2 ms     1 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5     2 ms     1 ms     2 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6     3 ms     2 ms     5 ms  27.122.122.15
>   7     3 ms     3 ms     2 ms  108.162.247.83
>   8     3 ms     2 ms     2 ms  104.18.36.236
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/63f3bac3/attachment.htm>

From sales at twig.com.au  Thu Sep 26 15:38:50 2024
From: sales at twig.com.au (TWIG Solutions)
Date: Thu, 26 Sep 2024 15:38:50 +1000
Subject: [AusNOG] Curly One
In-Reply-To: <119601db0fd1$3b727560$b2576020$@duxtel.com>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <119601db0fd1$3b727560$b2576020$@duxtel.com>
Message-ID: <aa883b95-b900-46ae-82a0-72c02569f0b7@twig.com.au>


But that doesn't explain why a staff member at home works (or when 
hot-spotted), he goes to the office with same laptop, it fails..? So as 
someone suggested maybe a GEO issue not loading the .js due to block.?? 
But then the service provider (AXS) would have been aware by now, I 
assume they have 000's of customers here.

We'll persevere!? Thanks for all the ideas..

Oh and as I said, loading the CORs Chrome extension didn't solve it for 
the 3 individual clients? tested.


Cheers,

Mal



On 26/09/2024 15:02, Mike Everest wrote:
>
> It?s a white page for everyone until the js loads and runs.? My guess 
> is that either some js bombs in the client browser, or the js is 
> attempting to load resources from some other location that is not 
> accessible to those locations.
>
> Eiter way, developer tools will give you some answers.
>
> Good luck with that! :-}
>
> Cheers!
>
> *From:*AusNOG <ausnog-bounces at lists.ausnog.net> *On Behalf Of *TWIG 
> Solutions
> *Sent:* Thursday, 26 September 2024 2:19 PM
> *To:* AusNOG at lists.ausnog.net
> *Subject:* [AusNOG] Curly One
>
> Afternoon All,
> ? I have an issue with some of my clients, which I discovered while 
> looking into the issue for 1 client.?? After testing from various 
> other geographically and ISP diverse clients I discovered it's pretty 
> wide spread issue.
>
> The issue is that the website below will only display a blank white 
> page for most clients, definitely ALL clients (I have tested) using 
> Exetel/Superloop FTTN, FTTC and select FTTP.
>
> https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>
> Yet some clients, when they view the site on the same laptop when at 
> home (Telstra), it loads fine and shows a login page. They come back 
> to the office, and it wont.?? My own service when it was FTTC, didnt 
> work, now I am FTTP it works.
>
> I did some tracing and discovered that as soon as the data traverse a 
> certain link,? it fails.?? I passed all my findings to 
> Exetel/Superloop technical and it's been now been in hand since 
> 25/6/24 and revived again on 26/8/24? (after the original ticket was 
> closed with no resolution). ? Nor they are saying its a website issue, 
> and they suggested installing a CORs extension on Chrome as it "fixed" 
> it for them.? Not a secure solution, but I tested extension on 3 
> clients, still no good, and why only for some clients??.
>
> So again I am waiting for responses, and? the initial client who 
> reported to me is getting very p*ssed off with the delays.? They use 
> the site a lot booking tickets for their clients etc...
>
> Traces shown below, I wonder if anyone can test and advise, perhaps 
> look at the traces you get if it does or doesn't work, as it seem 
> Exetel/Superloop are stumped.
>
>
> Cheers,
>
> Mal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *My Service ?? Working*
> Service:? 1000/50 FTTP
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
> ? 1??? <1 ms??? <1 ms??? <1 ms? [redacted]
> ? 2???? 4 ms???? 3 ms???? 4 ms?? [redacted]
> ? 3???? 2 ms???? 2 ms???? 2 ms? 202.90.206.198
> ? 4???? 3 ms???? 3 ms???? * 
> *Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]*
> ? 5???? 3 ms???? 4 ms???? 8 ms? 27.122.122.15
> ? 6???? 4 ms???? 6 ms???? 3 ms? 108.162.247.77
> ? 7???? 3 ms???? 3 ms???? 3 ms? 172.64.151.20
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *Client 1 ? Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
> ? 1???? *??????? *??????? *???? Request timed out.
> ? 2???? *??????? *??????? *???? Request timed out.
> ? 3??? 10 ms??? 10 ms??? 10 ms? [redacted]
> ? 4???? *??????? *?????? 11 ms r0q86sqz1y5z2lmg941.ip6.superloop.au 
> [2401:d000:3401::31]
> ? 5???? *?????? 10 ms???? * 
> *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
> [2401:d000:10:100::2c1]*
> ? 6??? 32 ms??? 13 ms??? 24 ms q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
> [2401:d000:3202::12]
> ? 7??? 10 ms??? 10 ms??? 10 ms? 2400:cb00:26:3::
> ? 8??? 10 ms??? 10 ms??? 10 ms? 2606:4700:4400::6812:24ec
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *
> Initial Client - NOT WORKING *
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
> ? 1???? *??????? *??????? *???? Request timed out.
> ? 2???? *??????? *??????? *???? Request timed out.
> ? 3???? 9 ms???? 9 ms???? 9 ms? 2406:3400:0:1::1
> ? 4???? *??????? *??????? *???? Request timed out.
> ? 5???? 9 ms???? 9 ms???? * 
> *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
> [2401:d000:10:100::2c1]*
> ? 6??? 17 ms??? 24 ms??? 21 ms q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
> [2401:d000:3202::12]
> ? 7??? 10 ms???? 9 ms???? 9 ms? 2400:cb00:491:3::
> ? 8???? 9 ms???? 9 ms???? 9 ms? 2606:4700:4400::6812:24ec
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 2 ? Not Working*
>
> Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 
> 32 bytes of data:
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>
> Ping statistics for 172.64.151.20:
> ??? Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> ??? Minimum = 13ms, Maximum = 13ms, Average = 13ms
>
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
> ? 1??? <1 ms??? <1 ms??? <1 ms?? [redacted]
> ? 2??? 12 ms??? 12 ms??? 12 ms?? [redacted]
> ? 3??? 13 ms??? 13 ms??? 13 ms? 10.1.23.54 [10.1.23.54]
> ? 4??? 13 ms??? 13 ms??? 12 ms 
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
> ? 5??? 13 ms???? *?????? 13 ms 
> *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]*
> ? 6??? 13 ms??? 13 ms??? 14 ms? 27.122.122.15
> ? 7??? 14 ms??? 13 ms??? 13 ms? 108.162.250.5
> ? 8??? 13 ms??? 13 ms??? 13 ms? 172.64.151.20
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 3 ? Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
> over a maximum of 30 hops:
>
> ? 1??? <1 ms??? <1 ms??? <1 ms?? [redacted]
> ? 2???? 1 ms???? 2 ms???? 1 ms?? [redacted]
> ? 3???? 2 ms???? 2 ms???? 2 ms? 10.1.21.186
> ? 4???? 2 ms???? 2 ms???? 1 ms 
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
> ? 5???? 2 ms???? 1 ms???? 2 ms 
> *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]*
> ? 6???? 3 ms???? 2 ms???? 5 ms? 27.122.122.15
> ? 7???? 3 ms???? 3 ms???? 2 ms? 108.162.247.83
> ? 8???? 3 ms???? 2 ms???? 2 ms? 104.18.36.236
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/c7cefc8d/attachment.htm>

From joseph at goldman.id.au  Thu Sep 26 15:43:40 2024
From: joseph at goldman.id.au (Joseph Goldman)
Date: Thu, 26 Sep 2024 05:43:40 +0000
Subject: [AusNOG] Curly One
In-Reply-To: <4a06521a-2518-4170-af7b-73ec9b20ac93@twig.com.au>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <MEYP282MB2520242C70CE706032B7A50EDB6A2@meyp282mb2520.ausp282.prod.outlook.com>
 <4a06521a-2518-4170-af7b-73ec9b20ac93@twig.com.au>
Message-ID: <em884e03ad-45ad-4fd6-8deb-bc941eb501da@joe-pc>

They would say that, as if 99.999% of people are working but a few 
outliers are having issues then they'd not want to spend the time 
deep-diving logs.

Shaun's findings are spot on - and i'd be confirming you are seeing the 
same, that you get a valid response to the original request and that you 
are getting similar error (403) for that resource which would indicate 
it definitely IS a website issue, but it'll be up to them to tell you 
why they are denying it. Perhaps superloop got a new block of IPs that 
are flagged in the GeoIP DB they use? Have you seen a correlation with 
the users assigned public IP such as are they all in the same 
subnet/supernet block? Would definitely explain why same laptop works on 
some  internet connections but not on others, still without it being a 
direct network issue.

Perhaps reach out to the site again with a src IP, datetime and the 
resource thats getting 403'd (with a snapshot of request/response 
headers) so they might be able to actually go log hunting for you.

------ Original Message ------
From: "TWIG Solutions" <sales at twig.com.au>
To: "AusNOG at lists.ausnog.net" <AusNOG at lists.ausnog.net>
Sent: 26/09/2024 3:29:59 PM
Subject: Re: [AusNOG] Curly One

>
>  They have said there is no issue on the website end..
>
>
>
>
>On 26/09/2024 14:35, Nathan Brookfield wrote:
>>What do the backend website owners AXS and Cloudflare have to say, I?d 
>>strongly suggest if your get a white page it?s nothing to do with the 
>>ISP?s you mentioned, also it loads fine here on all of the networks I 
>>manage.
>>
>>
>>
>>From: AusNOG <ausnog-bounces at lists.ausnog.net> 
>><mailto:ausnog-bounces at lists.ausnog.net> on behalf of TWIG Solutions 
>><sales at twig.com.au> <mailto:sales at twig.com.au>
>>Date: Thursday, 26 September 2024 at 14:19
>>To: AusNOG at lists.ausnog.net<AusNOG at lists.ausnog.net> 
>><mailto:AusNOG at lists.ausnog.net>
>>Subject: [AusNOG] Curly One
>>
>>Afternoon All,
>>   I have an issue with some of my clients, which I discovered while 
>>looking into the issue for 1 client.   After testing from various 
>>other geographically and ISP diverse clients I discovered it's pretty 
>>wide spread issue.
>>
>>The issue is that the website below will only display a blank white 
>>page for most clients, definitely ALL clients (I have tested) using 
>>Exetel/Superloop FTTN, FTTC and select FTTP.
>>
>>https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>>
>>Yet some clients, when they view the site on the same laptop when at 
>>home (Telstra), it loads fine and shows a login page.  They come back 
>>to the office, and it wont.   My own service when it was FTTC, didnt 
>>work, now I am FTTP it works.
>>
>>I did some tracing and discovered that as soon as the data traverse a 
>>certain link,  it fails.   I passed all my findings to 
>>Exetel/Superloop technical and it's been now been in hand since 
>>25/6/24 and revived again on 26/8/24  (after the original ticket was 
>>closed with no resolution).   Nor they are saying its a website issue, 
>>and they suggested installing a CORs extension on Chrome as it "fixed" 
>>it for them.  Not a secure solution, but I tested extension on 3 
>>clients, still no good, and why only for some clients??.
>>
>>So again I am waiting for responses, and  the initial client who 
>>reported to me is getting very p*ssed off with the delays.  They use 
>>the site a lot booking tickets for their clients etc...
>>
>>Traces shown below, I wonder if anyone can test and advise, perhaps 
>>look at the traces you get if it does or doesn't work, as it seem 
>>Exetel/Superloop are stumped.
>>
>>
>>Cheers,
>>
>>Mal
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>My Service    Working
>>Service:  1000/50 FTTP
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
>>[172.64.151.20]
>>over a maximum of 30 hops:
>>
>>   1    <1 ms    <1 ms    <1 ms  [redacted]
>>   2     4 ms     3 ms     4 ms   [redacted]
>>   3     2 ms     2 ms     2 ms  202.90.206.198
>>   4     3 ms     3 ms     *     
>>Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.65]
>>   5     3 ms     4 ms     8 ms  27.122.122.15
>>   6     4 ms     6 ms     3 ms  108.162.247.77
>>   7     3 ms     3 ms     3 ms  172.64.151.20
>>
>>
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>Client 1   Not Working
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
>>[2606:4700:4400::6812:24ec]
>>over a maximum of 30 hops:
>>
>>   1     *        *        *     Request timed out.
>>   2     *        *        *     Request timed out.
>>   3    10 ms    10 ms    10 ms  [redacted]
>>   4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au 
>>[2401:d000:3401::31]
>>   5     *       10 ms     *     
>>bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
>>[2401:d000:10:100::2c1]
>>   6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
>>[2401:d000:3202::12]
>>   7    10 ms    10 ms    10 ms  2400:cb00:26:3::
>>   8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>Initial Client - NOT WORKING
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
>>[2606:4700:4400::6812:24ec]
>>over a maximum of 30 hops:
>>
>>   1     *        *        *     Request timed out.
>>   2     *        *        *     Request timed out.
>>   3     9 ms     9 ms     9 ms  2406:3400:0:1::1
>>   4     *        *        *     Request timed out.
>>   5     9 ms     9 ms     *     
>>bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co 
>>[2401:d000:10:100::2c1]
>>   6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au 
>>[2401:d000:3202::12]
>>   7    10 ms     9 ms     9 ms  2400:cb00:491:3::
>>   8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec
>>
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>Client 2   Not Working
>>
>>Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 
>>32 bytes of data:
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>>
>>Ping statistics for 172.64.151.20:
>>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>>Approximate round trip times in milli-seconds:
>>     Minimum = 13ms, Maximum = 13ms, Average = 13ms
>>
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
>>[172.64.151.20]
>>over a maximum of 30 hops:
>>
>>   1    <1 ms    <1 ms    <1 ms   [redacted]
>>   2    12 ms    12 ms    12 ms   [redacted]
>>   3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
>>   4    13 ms    13 ms    12 ms  
>>Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com 
>>[116.255.21.108]
>>   5    13 ms     *       13 ms  
>>Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
>>   6    13 ms    13 ms    14 ms  27.122.122.15
>>   7    14 ms    13 ms    13 ms  108.162.250.5
>>   8    13 ms    13 ms    13 ms  172.64.151.20
>>
>>
>>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>Client 3   Not Working
>>
>>Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net 
>>[104.18.36.236]
>>over a maximum of 30 hops:
>>
>>   1    <1 ms    <1 ms    <1 ms   [redacted]
>>   2     1 ms     2 ms     1 ms   [redacted]
>>   3     2 ms     2 ms     2 ms  10.1.21.186
>>   4     2 ms     2 ms     1 ms  
>>Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com 
>>[116.255.21.108]
>>   5     2 ms     1 ms     2 ms  
>>Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com [103.200.13.70]
>>   6     3 ms     2 ms     5 ms  27.122.122.15
>>   7     3 ms     3 ms     2 ms  108.162.247.83
>>   8     3 ms     2 ms     2 ms  104.18.36.236
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/de3f29b5/attachment-0001.htm>

From scott at doc.net.au  Thu Sep 26 15:46:51 2024
From: scott at doc.net.au (Scott Howard)
Date: Thu, 26 Sep 2024 15:46:51 +1000
Subject: [AusNOG] Curly One
In-Reply-To: <aa883b95-b900-46ae-82a0-72c02569f0b7@twig.com.au>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <119601db0fd1$3b727560$b2576020$@duxtel.com>
 <aa883b95-b900-46ae-82a0-72c02569f0b7@twig.com.au>
Message-ID: <CACnPsNUkdwVmFfHWwJyToKPOZ5Vmj8FHayuRg2ft5bRz6nvuqw@mail.gmail.com>

AXS (or probably more correctly, CloudFlare) are blocking requests.  You
should be able to repro this by going to https://api.axs.com from a
'broken' connection.

[image: image.png]

  Scott



On Thu, Sep 26, 2024 at 3:39?PM TWIG Solutions <sales at twig.com.au> wrote:

>
> But that doesn't explain why a staff member at home works (or when
> hot-spotted), he goes to the office with same laptop, it fails..  So as
> someone suggested maybe a GEO issue not loading the .js due to block.   But
> then the service provider (AXS) would have been aware by now, I assume they
> have 000's of customers here.
>
> We'll persevere!  Thanks for all the ideas..
>
> Oh and as I said, loading the CORs Chrome extension didn't solve it for
> the 3 individual clients  tested.
>
>
> Cheers,
>
> Mal
>
>
>
> On 26/09/2024 15:02, Mike Everest wrote:
>
> It?s a white page for everyone until the js loads and runs.  My guess is
> that either some js bombs in the client browser, or the js is attempting to
> load resources from some other location that is not accessible to those
> locations.
>
> Eiter way, developer tools will give you some answers.
>
>
>
> Good luck with that! :-}
>
> Cheers!
>
>
>
> *From:* AusNOG <ausnog-bounces at lists.ausnog.net>
> <ausnog-bounces at lists.ausnog.net> *On Behalf Of *TWIG Solutions
> *Sent:* Thursday, 26 September 2024 2:19 PM
> *To:* AusNOG at lists.ausnog.net
> *Subject:* [AusNOG] Curly One
>
>
>
> Afternoon All,
>   I have an issue with some of my clients, which I discovered while
> looking into the issue for 1 client.   After testing from various other
> geographically and ISP diverse clients I discovered it's pretty wide spread
> issue.
>
> The issue is that the website below will only display a blank white page
> for most clients, definitely ALL clients (I have tested) using
> Exetel/Superloop FTTN, FTTC and select FTTP.
>
> https://fanaccount.axs.com.au/login <https://fanaccount.axs.com.au/>
>
> Yet some clients, when they view the site on the same laptop when at home
> (Telstra), it loads fine and shows a login page.  They come back to the
> office, and it wont.   My own service when it was FTTC, didnt work, now I
> am FTTP it works.
>
> I did some tracing and discovered that as soon as the data traverse a
> certain link,  it fails.   I passed all my findings to Exetel/Superloop
> technical and it's been now been in hand since 25/6/24 and revived again on
> 26/8/24  (after the original ticket was closed with no resolution).   Nor
> they are saying its a website issue, and they suggested installing a CORs
> extension on Chrome as it "fixed" it for them.  Not a secure solution, but
> I tested extension on 3 clients, still no good, and why only for some
> clients??.
>
> So again I am waiting for responses, and  the initial client who reported
> to me is getting very p*ssed off with the delays.  They use the site a lot
> booking tickets for their clients etc...
>
> Traces shown below, I wonder if anyone can test and advise, perhaps look
> at the traces you get if it does or doesn't work, as it seem
> Exetel/Superloop are stumped.
>
>
> Cheers,
>
> Mal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *My Service    Working*
> Service:  1000/50 FTTP
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms  [redacted]
>   2     4 ms     3 ms     4 ms   [redacted]
>   3     2 ms     2 ms     2 ms  202.90.206.198
>   4     3 ms     3 ms     *     *Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether30.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.65]*
>   5     3 ms     4 ms     8 ms  27.122.122.15
>   6     4 ms     6 ms     3 ms  108.162.247.77
>   7     3 ms     3 ms     3 ms  172.64.151.20
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> *Client 1   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3    10 ms    10 ms    10 ms  [redacted]
>   4     *        *       11 ms  r0q86sqz1y5z2lmg941.ip6.superloop.au
> [2401:d000:3401::31]
>   5     *       10 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    32 ms    13 ms    24 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms    10 ms    10 ms  2400:cb00:26:3::
>   8    10 ms    10 ms    10 ms  2606:4700:4400::6812:24ec
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> * Initial Client - NOT WORKING *
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net
> [2606:4700:4400::6812:24ec]
> over a maximum of 30 hops:
>
>   1     *        *        *     Request timed out.
>   2     *        *        *     Request timed out.
>   3     9 ms     9 ms     9 ms  2406:3400:0:1::1
>   4     *        *        *     Request timed out.
>   5     9 ms     9 ms     *     *bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co
> <http://bundle-ether32.bdr02-ipt-639garde-syd.au.superloop.net.co>
> [2401:d000:10:100::2c1]*
>   6    17 ms    24 ms    21 ms  q4b0lhjpx7wd2m4dptk.ip6.superloop.au
> [2401:d000:3202::12]
>   7    10 ms     9 ms     9 ms  2400:cb00:491:3::
>   8     9 ms     9 ms     9 ms  2606:4700:4400::6812:24ec
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 2   Not Working*
>
> Pinging fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20] with 32
> bytes of data:
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
> Reply from 172.64.151.20: bytes=32 time=13ms TTL=58
>
> Ping statistics for 172.64.151.20:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 13ms, Maximum = 13ms, Average = 13ms
>
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [172.64.151.20]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2    12 ms    12 ms    12 ms   [redacted]
>   3    13 ms    13 ms    13 ms  10.1.23.54 [10.1.23.54]
>   4    13 ms    13 ms    12 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5    13 ms     *       13 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6    13 ms    13 ms    14 ms  27.122.122.15
>   7    14 ms    13 ms    13 ms  108.162.250.5
>   8    13 ms    13 ms    13 ms  172.64.151.20
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> *Client 3   Not Working*
>
> Tracing route to fanaccount.axs.com.au.cdn.cloudflare.net [104.18.36.236]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms   [redacted]
>   2     1 ms     2 ms     1 ms   [redacted]
>   3     2 ms     2 ms     2 ms  10.1.21.186
>   4     2 ms     2 ms     1 ms
> Bundle-Ether200.bdr02-ipt-47bourke-syd.au.superloop.com [116.255.21.108]
>   5     2 ms     1 ms     2 ms  *Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com
> <http://Bundle-Ether32.bdr02-ipt-639garde-syd.au.superloop.com>
> [103.200.13.70]*
>   6     3 ms     2 ms     5 ms  27.122.122.15
>   7     3 ms     3 ms     2 ms  108.162.247.83
>   8     3 ms     2 ms     2 ms  104.18.36.236
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/98465b99/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 199669 bytes
Desc: not available
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/98465b99/attachment-0001.png>

From gogroup.au at gmail.com  Thu Sep 26 17:02:16 2024
From: gogroup.au at gmail.com (Go Grp - LGov Systems)
Date: Thu, 26 Sep 2024 16:32:16 +0930
Subject: [AusNOG] Fwd:  Curly One
In-Reply-To: <CACnPsNUkdwVmFfHWwJyToKPOZ5Vmj8FHayuRg2ft5bRz6nvuqw@mail.gmail.com>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <119601db0fd1$3b727560$b2576020$@duxtel.com>
 <aa883b95-b900-46ae-82a0-72c02569f0b7@twig.com.au>
 <CACnPsNUkdwVmFfHWwJyToKPOZ5Vmj8FHayuRg2ft5bRz6nvuqw@mail.gmail.com>
Message-ID: <CAByB+vAPOG+0nk0WiwkCMoa+EBr127AiiZeW=i4=_t=UTEyiXQ@mail.gmail.com>

G'Day Mal

The 1st issue I 'see' is cloudflare, we havn't used them for a while due to
them blocking AusE IPV4 they believed were OS

2nd when the laptop was in the office & stopped working did you try
tethering to Telstra network (mobile) & retry

I have seen TOR exits on the telstra mobile network, but its very rare

BTW - In my humble opinion having run the nets longest continious
scientific experiement stating with a IBM OS2 BBS SMTP server ( I wrote in
Ass. & procedural C ) in early '90s this won't be a HTML/JS issue

Ken G.
Go G.



>
> But that doesn't explain why a staff member at home works (or when
> hot-spotted), he goes to the office with same laptop, it fails..  So as
> someone suggested maybe a GEO issue not loading the .js due to block.   But
> then the service provider (AXS) would have been aware by now, I assume they
> have 000's of customers here.
>
> We'll persevere!  Thanks for all the ideas..
>
> Oh and as I said, loading the CORs Chrome extension didn't solve it for
> the 3 individual clients  tested.
>
>
> Cheers,
>
> Mal
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/643042a4/attachment.htm>

From Clovis at netcore.com.au  Thu Sep 26 17:14:30 2024
From: Clovis at netcore.com.au (Steve Dimitrio)
Date: Thu, 26 Sep 2024 07:14:30 +0000
Subject: [AusNOG]  Reverse Name Lookup
Message-ID: <ME4P282MB072759A6ED24283E8B0D36FDE76A2@ME4P282MB0727.AUSP282.PROD.OUTLOOK.COM>

Hi guys
Anyone from aapt desk online?
The usual channels are getting us no where
Details below





Commencing early morning last Friday Sep 20, most of our nbn IPs are experiencing delays connecting to services which use IP Reverse Name Lookup.



ie ssh has a 15 second delay, mail/smtp has a 35 second delay.



If we disable Reverse Name Lookup in ssh, the delay dissappears.

Not possible to disable Reverse Name Lookup in sendmail.



For the good IPs, host or dig the IP returns a hostname, and host or dig or nslookup the hostname returns the IP.

For the bad IPs, host or dig the IP returns a hostname, and host or dig or nslookup the hostname fails.





27.32.181.22 is OK.



rain:~# host 27.32.181.22

22.181.32.27.in-addr.arpa domain name pointer 27-32-181-22.tpgi.com.au.

rain:~# host 27-32-181-22.tpgi.com.au

27-32-181-22.tpgi.com.au has address 27.32.181.22 rain:~#



59.100.247.50, 210.10.223.90, 59.100.243.186, 203.174.142.86,

203.174.178.46 are not OK.



rain:~# host 59.100.247.50

50.247.100.59.in-addr.arpa domain name pointer 59-100-247-50.mel.static-ipl.aapt.com.au.

rain:~# host 59-100-247-50.mel.static-ipl.aapt.com.au

;; connection timed out; no servers could be reached rain:~#



Similar results with nslookup or dig.



Can you please investigate and restore the hostname lookups.






Steve Dimitrio
Netcore PTY LTD
Office: 03 9725 1469

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240926/18993a64/attachment.htm>

From scott at doc.net.au  Fri Sep 27 19:48:45 2024
From: scott at doc.net.au (Scott Howard)
Date: Fri, 27 Sep 2024 19:48:45 +1000
Subject: [AusNOG] Curly One
In-Reply-To: <CACnPsNUkdwVmFfHWwJyToKPOZ5Vmj8FHayuRg2ft5bRz6nvuqw@mail.gmail.com>
References: <510f8e95-33d1-4818-80ea-5e8648ff6d67@twig.com.au>
 <119601db0fd1$3b727560$b2576020$@duxtel.com>
 <aa883b95-b900-46ae-82a0-72c02569f0b7@twig.com.au>
 <CACnPsNUkdwVmFfHWwJyToKPOZ5Vmj8FHayuRg2ft5bRz6nvuqw@mail.gmail.com>
Message-ID: <CACnPsNVUw_TKDOMD6gEVp2W++zb4o8TNm-fNQWm8=qg_VmMM6Q@mail.gmail.com>

There's something very ironic in this...

Delivery incomplete
There was a temporary problem delivering your message to sales at twig.com.au.

The response from the remote server was:
550 A URL in this email (cloudflare . net) is listed on https://spamrl.com/.
Please resolve and retry


  Scott

On Thu, Sep 26, 2024 at 3:46?PM Scott Howard <scott at doc.net.au> wrote:

> AXS (or probably more correctly, CloudFlare) are blocking requests.  You
> should be able to repro this by going to https://api.axs.com from a
> 'broken' connection.
>
> [image: image.png]
>
>   Scott
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240927/8722029c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 199669 bytes
Desc: not available
URL: <https://lists.ausnog.net/pipermail/ausnog/attachments/20240927/8722029c/attachment-0001.png>