Completed -
The scheduled maintenance has been completed.
Dec 2, 10:04 NZDT
Update -
Maintenance completed successfully.
Dec 2, 10:03 NZDT
In progress -
Maintenance in progress.
Symptoms: IPoE has been available on our broadband services for two years, with around 10% of customers now using it. While performance has been strong, we’ve identified an issue affecting a small number of customers using static IP addresses across multiple sites.
Occasionally, these customers may experience routing issues between their own Voyager connections due to automatically generated subnet masks under IPoE, which can sometimes overlap between sites.
What are we changing ?
We are introducing a standardised /24 subnet mask (255.255.255.0) for all static-IP IPoE services.
Applies only to static IPs on IPoE
Dynamic IP services are not affected
The /24 subnet will apply after the change and a session re-authentication
.0 and .255 addresses will be phased out as network/broadcast addresses
This update will remove inter-site routing issues for customers with multiple Voyager static-IP connections.
Recommended user actions: No action is required for most customers.
Those wishing to apply the new settings immediately can restart their router and leave it powered off for at least 15 minutes to trigger an IPoE re-authentication.
Dec 2, 09:02 NZDT
Update -
Maintenance has been scheduled.
Symptoms: IPoE has been available on our broadband services for two years, with around 10% of customers now using it. While performance has been strong, we’ve identified an issue affecting a small number of customers using static IP addresses across multiple sites.
Occasionally, these customers may experience routing issues between their own Voyager connections due to automatically generated subnet masks under IPoE, which can sometimes overlap between sites.
What are we changing ?
We are introducing a standardised /24 subnet mask (255.255.255.0) for all static-IP IPoE services.
Applies only to static IPs on IPoE
Dynamic IP services are not affected
The /24 subnet will apply after the change and a session re-authentication
.0 and .255 addresses will be phased out as network/broadcast addresses
This update will remove inter-site routing issues for customers with multiple Voyager static-IP connections.
Recommended user actions: No action is required for most customers.
Those wishing to apply the new settings immediately can restart their router and leave it powered off for at least 15 minutes to trigger an IPoE re-authentication.
Nov 28, 15:34 NZDT
Update -
Maintenance has been scheduled.
Symptoms: IPoE has been available on our broadband services for two years, with around 10% of customers now using it. While performance has been strong, we’ve identified an issue affecting a small number of customers using static IP addresses across multiple sites.
Occasionally, these customers may experience routing issues between their own Voyager connections due to automatically generated subnet masks under IPoE, which can sometimes overlap between sites.
________________________________________
What We Are Changing
We are introducing a standardised /24 subnet mask (255.255.255.0) for all static-IP IPoE services.
Applies only to static IPs on IPoE
Dynamic IP services are not affected
The /24 subnet will apply after the change and a session re-authentication
.0 and .255 addresses will be phased out as network/broadcast addresses
This update will remove inter-site routing issues for customers with multiple Voyager static-IP connections.
Recommended user actions: No action is required for most customers.
Those wishing to apply the new settings immediately can restart their router and leave it powered off for at least 15 minutes to trigger an IPoE re-authentication.
Nov 28, 15:31 NZDT
Scheduled -
Maintenance has been scheduled.
Symptoms: Two years ago we enabled IPoE and largely things have been working smoothly. Currently almost 10% of our user base has switched to using IPoE from PPP. We have been monitoring an issue with our static IP customers who have multiple sites where sometimes they may not be able to route to the other connection. This issue is due to the nature of how static IP DHCP is currently assigned in that a subnet mask is synthesized to ensure ethernet rules. For every IP provided to a customer there must be a network address, broadcast address and a gateway. We don't actually configure any of these and there is a bunch of networking smoke and mirrors at play. Sometimes the generated network details create issues when a customer needs to route to another Voyager connection with a similar IP address.
In order to rectify this situation we are opting to impose a hard configured subnet mask for all static IP IPoE connections. (Dynamic works through a different mechanism so isn't affected by this). After this change has been implemented and after an IPoE re-authentication has occurred customers will see a /24 subnet mask (255.255.255.0). Over time we will also be removing .0 and .255 out of service as those are the expected network and broadcast addresses for a /24 subnet.
This change will remove any intersite routing issues for our customers with multiple connections who are wanting to use IPoE.
Recommended user actions: Customers may choose to re-authenticate their IPoE session to take advantage of these change by turning off their router for at least 15mins - This is not a requirement for all customers.
Nov 27, 13:44 NZDT