Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 
Talkiet
4819 posts

Uber Geek
+1 received by user: 3934

Trusted

  #2813797 16-Nov-2021 11:27
Send private message

It's not out of the realm of possibility that the LFC PON port is congesting (or exhibiting behaviours resulting from very high usage) but confirming that requires parsing hundreds of GB of data from Chorus. (I'm not sure if the other LFCs even make the data available)

 

Cheers- N

 

 





Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.




majiktripp

47 posts

Geek
+1 received by user: 1


  #2813892 16-Nov-2021 14:29
Send private message

Response from Orcon, aligns with comments above:

 

We have provided the data to our Tier 2 team to review. There does appear to be a large spike in ping when your issues occur but they have not been able to find an explanation as to why this is the case. There is uncertainty as to why IPv6 appears to be prioritised too. To elaborate, they are not seeing any breaks in session or other noticeable issues in our records which align with the timing of the ping spikes in the data you have provided.

 

Our Tier 2 team has advised that they will need more data. They have indicated that you should use a minimalistic setup (i.e. connect the PC directly to the modem which in turn is connected directly to the ONT). No other devices should be connected at the time of testing as they wish to rule out all other variables related to your equipment/setup.

 

With the setup above, the team has requested that you perform and provide the following:

 

1. A trace route run on your PC.

 

2. A trace route run on your PC with IPv6 disabled.

 

3. A trace route run on an alternate PC.


nztim
4013 posts

Uber Geek
+1 received by user: 2711

ID Verified
Trusted
TEAMnetwork
Subscriber

  #2813920 16-Nov-2021 15:45
Send private message

Where are you based?




Any views expressed on these forums are my own and don't necessarily reflect those of my employer. 




majiktripp

47 posts

Geek
+1 received by user: 1


  #2813924 16-Nov-2021 15:52
Send private message

West Auckland, Glen Eden

nztim
4013 posts

Uber Geek
+1 received by user: 2711

ID Verified
Trusted
TEAMnetwork
Subscriber

  #2813925 16-Nov-2021 16:01
Send private message

Ok If you were in Wellington id offer to look

Have you tried disabling IPV6 on your device forcing ipv4?




Any views expressed on these forums are my own and don't necessarily reflect those of my employer. 


majiktripp

47 posts

Geek
+1 received by user: 1


  #2813962 16-Nov-2021 16:56
Send private message

Have just updated LAN DHCP settings on the Orcon modem and disabled IPV6 so will monitor over next while and see if any impact/change.

 
 
 

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).
nztim
4013 posts

Uber Geek
+1 received by user: 2711

ID Verified
Trusted
TEAMnetwork
Subscriber

  #2813976 16-Nov-2021 17:33
Send private message

majiktripp: Have just updated LAN DHCP settings on the Orcon modem and disabled IPV6 so will monitor over next while and see if any impact/change.


You didn’t need to go to that extent just untick ipv6 on your pcs network settings




Any views expressed on these forums are my own and don't necessarily reflect those of my employer. 


majiktripp

47 posts

Geek
+1 received by user: 1


  #2817207 22-Nov-2021 16:34
Send private message

Just had another outage, and hooked up the laptop to the ONT box via the LAN 1 Port being used by the Orcon router.

Pings from the laptop via the ONT box worked without issue, detailed below:

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [2400:4800:1::6] with 32 bytes of data:
Reply from 2400:4800:1::6: time=2ms
Reply from 2400:4800:1::6: time=1ms
Reply from 2400:4800:1::6: time=1ms
Reply from 2400:4800:1::6: time=1ms

 

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

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252

 

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

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252

 

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

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=3ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252

 

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

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252

 

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

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=3ms TTL=252
Reply from 60.234.0.19: bytes=32 time=3ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252

 

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

 


At this point, I reconnected to the Orcon Router and was carrying out pings on the laptop - the times below blow out again:

C:\Users\Caroline>ping www.orcon.net.nz
Ping request could not find host www.orcon.net.nz. Please check the name and try again.

 

C:\Users\Caroline>ping www.orcon.net.nz
Ping request could not find host www.orcon.net.nz. Please check the name and try again.

 

C:\Users\Caroline>ping www.orcon.net.nz

 

Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=18ms TTL=251
Request timed out.
Reply from 60.234.0.19: bytes=32 time=1457ms TTL=251
Reply from 60.234.0.19: bytes=32 time=2796ms TTL=251

 

Ping statistics for 60.234.0.19:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 2796ms, Average = 1423ms



Seems it would indicate an issue with the Orcon router? I'll be sending this all through to their ICT on the existing thread but at this point I'm thinking of swapping out the router for one of my own (leaning towards Ubiquiti Edgerouter at moment).


majiktripp

47 posts

Geek
+1 received by user: 1


  #2833020 15-Dec-2021 20:03
Send private message

Last update for completeness. I have removed the Orcon router from the equation and been running a TP-Link ER605 router in its place. It has been up and running for the last 9 days without any drop outs or outages and seems to have resolved the problem. I will continue to monitor using the TP-Link Omada SDN software but so far so good. Seems to indicate the router itself was the core of the problem all along.


1 | 2 
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.