- NZNOG - lists.nznog.org

NZ NTP servers giving incorrect times?
by John Rumsey 20 Mar '10

20 Mar '10

Hi have just noticed msltime.irl.cri.nz. and msltime2.irl.cri.nz. have developed a 180 second offset from GPS-based ntp sources. As far as we can tell, the GPS-based sources are more likely right than the msltime servers. Can anyone shed any further light on this? cheers, John Rumsey

3 2

Dunedin Peering Exchange
by Stu Fleming 19 Mar '10

19 Mar '10

WIC operates the Dunedin Peering Exchange on behalf of Citylink. The exchange is a neutral meeting point for operators within Dunedin city to gain access to route servers and peer data locally. The exchange has been housed with WIC since 2005 and a portion of the exchange was transferred to Snap Internet in 2007. The portion that remains with WIC is active and available for peering; the portion with Snap is currently inactive. Can someone from Snap Internet please contact me off-list to discuss? I am aware of misinformation that is being spread locally regarding the Dunedin Peering Exchange and wish to correct this. 1. The Dunedin Peering Exchange (http://dpe.nzix.net/) is active and open to any parties who wish to exchange data. 2. The requirements for peering at the exchange are: layer 2 connectivity to an exchange location, an ASN and public IPs. 3. Multilateral peering is default; bilateral is by arrangement, both coordinated through Citylink via the online form at http://citylink.co.nz/products/forms/exchangenet.php 4. The current exchange location is 26 Cresswell St, Dunedin, with the additional location hosted by Snap Internet TBC. 5. Exchange location at Cresswell St has rack space available for equipment should it be required. 6. Exchange location has connectivity options via Flute dark fibre, TelstraClear fibre, Telecom copper to the rack, with Telecom fibre available. We also have a variety of wireless options for connectivity. 7. Local beer includes Speights (in keg form), Emersons, Macduff and Green Man. We actively encourage operators within Dunedin city and beyond to connect to the exchange. To arrange connectivity to the exchange, please contact Citylink via the forms indicated above. For any other information, or if you wish to discuss becoming a connectivity provider to the exchange, please contact me directly. Regards, Stu Managing Director, WIC NZ Tel: 03 474 2100 Cell: 021 993 125

1 0

Posting Form
by James Jones 17 Mar '10

17 Mar '10

Ok the new posting form can be found on the main info page for the mailing list https://puck.nether.net/mailman/listinfo/network-jobs. This will make it a lot easier to use and clear up any confusion on the format. I also welcome people to bypass the form post directly to the cgi handling the form. http://outcast.ws/cgi-bin/networkjobs it will only accept post method. You can pull all the variables from the web form. All fields are required other wise they will not get pass the moderator (Me!!). -- James Jones +1-413-667-9199 james(a)freedomnet.co.nz

1 1

NZRS recommends to test if your resolver is able to receive larger DNS responses
by Sebastian Castro 17 Mar '10

17 Mar '10

[Apologies in advance if you have received similar message coming from a different mailing list] The purpose of this email is to raise awareness of the root zone signing that is currently taking place. During the first half of 2010 the DNS root servers will incrementally deploy DNSSEC by introducing a signed root zone. This change aims to provide more confidence in DNS responses by adding signatures that can be validated, with the side effect of responses becoming larger in size. Originally the DNS protocol considered a response to be sent using UDP if it fits in a 512-byte packet, if not a signal is sent back to the requestor to retry using TCP. In 1999, RFC 2671 extended this limit up to 64k but in practice is 4096 bytes, allowing a client to signal the ability to receive a larger response by UDP. Despite the support for larger responses, there are firewalls and network equipment that, by design or configuration, does not allow DNS responses larger than 512 bytes. Another issue observable is by equipment able to handle the responses but failing to handle IP fragments, limiting the effective limit to the size of the local MTU (for Ethernet networks, 1500 bytes). According to the plan published by the DNS root servers operators at http://www.root-dnssec.org/ the deployment will be completed in May 2010. By that time if a network is unable to receive larger responses, they will perceive an "Internet blackout". The deployment has already started and root servers A, L, M and I are currently serving a signed zone. The critical point for New Zealand could be when F and J root servers deploy given their local presence. NZRS recommends that users and operators should check the ability of their networks to receive such larger packets. o do so, you can use: 1. From a machine with the tool *dig* installed run dig +short rs.dns-oarc.net txt this will test the ability of your configured resolver to receive large packets. For details on what to expect from the response and more information about this tool, please check: https://www.dns-oarc.net/oarc/services/replysizetest 2. You can use the tool developed by RIPE NCC to run similar test (requires Java). http://labs.ripe.net/content/testing-your-resolver-dns-reply-size-issues NOTE: This is also valid with the signed .ARPA zone announced by Joe Abley recently on this mailing list. .nz Registry Services PO Box 24361 Wellington New Zealand e support(a)nzrs.net.nz p 64 4 931 6970 f 64 4 931 6979 w www.nzrs.net.nz

1 0

NZRR Route Registry Update
by NZRR Database Notifications 17 Mar '10

17 Mar '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES6:AS4739 descr: Route set advertised to AS9560 by Internode Pty Ltd - AS4739 mp-members: 2001:44B8:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mmc(a)internode.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100311 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES6:AS4739 descr: Route set advertised to AS9560 by Internode - AS4739 mp-members: 2001:0dcd:0:0:0:0:0:0/32^32-64, 2400:5000:0:0:0:0:0:0/32^32-64, 2400:c400:0:0:0:0:0:0/32^32-64, 2401:e400:0:0:0:0:0:0/32^32-64, 2001:0500:002f:0:0:0:0:0/48^48-64, 2405:5000:0:0:0:0:0:0/32^32-64, 2001:44b8:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mmc(a)internode.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100318 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 17 Mar '10

17 Mar '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Vodafone NZ - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 124.6.192.0/19^19-29, 203.96.192.0/19^19-29, 174.128.16.0/20^20-29, 202.73.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 210.4.208.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.50.188.0/22^22-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 203.84.134.0/23^23-29, 203.147.108.0/23^23-29, 97.64.46.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 203.119.56.0/24^24-29, 203.171.4.0/24^24-29, 205.233.128.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jack.lee(a)vodafone.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20081115 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Vodafone NZ - AS7657 members: 118.92.0.0/15^15-29, 27.252.0.0/16^16-29, 121.90.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 124.6.192.0/19^19-29, 203.96.192.0/19^19-29, 203.173.192.0/19^19-29, 202.73.192.0/20^20-29, 203.173.240.0/20^20-29, 202.36.16.0/21^21-29, 198.48.0.0/22^22-29, 202.36.24.0/22^22-29, 210.4.208.0/22^22-29, 202.8.44.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 203.147.108.0/23^23-29, 210.4.214.0/23^23-29, 192.190.108.0/24^24-29, 202.8.47.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.66.0/24^24-29, 202.49.69.0/24^24-29, 202.49.71.0/24^24-29, 202.49.178.0/24^24-29, 202.50.84.0/24^24-29, 202.50.188.0/24^24-29, 203.171.4.0/24^24-29, 205.191.208.0/24^24-29, 205.233.128.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: relihan.myburgh(a)vodafone.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100318 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Signing of the ARPA zone
by Joe Abley 17 Mar '10

17 Mar '10

Colleagues, This is a follow-up to the operational announcement regarding changes to the ARPA top-level domain that was sent on 2010-03-10. Apologies in advance for duplicates received through different mailing lists. As of 2010-03-17 1630 UTC all the authoritative servers for ARPA are serving a signed ARPA zone. We would like to solicit feedback from the technical community to allow us to identify any operational ill-effects that this change has caused. We will monitor this mailing list for feedback, and I will also distribute any feedback sent to me personally so that it can be considered. If no harmful effects have been identified by 2010-03-21 the trust anchor for the ARPA zone will be published through the IANA ITAR at <https://itar.iana.org/>. Regards, Joe Begin forwarded message: > From: Joe Abley <joe.abley(a)icann.org> > Date: 10 March 2010 16:13:46 EST > To: Joe Abley <joe.abley(a)icann.org> > Subject: Signing of the ARPA zone > > Colleagues, > > This is a technical, operational announcement regarding changes to the ARPA top-level domain. Apologies in advance for duplicates received through different mailing lists. > > No specific action is requested of operators. This message is for your information only. > > The ARPA zone is about to be signed using DNSSEC. The technical parameters by which ARPA will be signed are as follows: > > KSK Algorithm and Size: 2048 bit RSA > KSK Rollover: every 2-5 years, scheduled rollover to follow RFC 5011 > KSK Signature Algorithm: SHA-256 > Validity period for signatures made with KSK: 15 days; new signatures published every 10 days > ZSK Algorithm and Size: 1024 bit RSA > ZSK Rollover: every 3 months > ZSK Signature Algorithm: SHA-256 > Authenticated proof of non-existence: NSEC > Validity period for signatures made with ZSK: 7 days; zone generated and re-signed twice per day > > The twelve root server operators [1] will begin to serve a signed ARPA zone instead of the (current) unsigned ARPA zone during a maintenance window which will open at 2010-03-15 0001 UTC and close at 2010-03-17 2359 UTC. Individual root server operators will carry out their maintenance at times within that window according to their own operational preference. > > The trust anchor for the ARPA zone will be published in the ITAR [2], and in the root zone in the form of a DS record once the root zone is signed. > > If you have any concerns or require further information, please let me know. > > Regards, > > > Joe Abley > Director DNS Operations, ICANN > > [1] <http://www.root-servers.org/> > [2] <https://itar.iana.org/>

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Mar '10

16 Mar '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4739 descr: Route set advertised to AS9560 by Internode Pty Ltd - AS4739 members: 192.231.203.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mmc(a)internode.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100311 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4739 descr: advertised to AS9560 by Internode - AS4739 members: 118.208.0.0/15^15-29, 121.44.0.0/15^15-29, 59.167.0.0/16^16-29, 118.210.0.0/16^16-29, 131.242.0.0/16^16-29, 143.92.0.0/16^16-29, 143.216.0.0/16^16-29, 147.132.0.0/16^16-29, 150.101.0.0/16^16-29, 161.143.0.0/16^16-29, 164.112.0.0/16^16-29, 167.123.0.0/16^16-29, 113.192.0.0/18^18-29, 118.127.0.0/18^18-29, 121.101.0.0/18^18-29, 124.157.0.0/18^18-29, 173.222.0.0/18^18-29, 175.107.128.0/18^18-29, 203.122.192.0/18^18-29, 64.185.160.0/19^19-29, 69.192.96.0/19^19-29, 96.16.64.0/19^19-29, 96.16.128.0/19^19-29, 113.203.32.0/19^19-29, 118.215.0.0/19^19-29, 118.215.192.0/19^19-29, 182.50.0.0/19^19-29, 184.50.64.0/19^19-29, 184.50.128.0/19^19-29, 184.84.128.0/19^19-29, 202.9.64.0/19^19-29, 202.60.64.0/19^19-29, 203.161.128.0/19^19-29, 69.192.144.0/20^20-29, 69.192.176.0/20^20-29, 72.246.96.0/20^20-29, 72.246.128.0/20^20-29, 72.247.176.0/20^20-29, 88.221.160.0/20^20-29, 92.122.128.0/20^20-29, 92.123.80.0/20^20-29, 95.100.0.0/20^20-29, 96.7.64.0/20^20-29, 96.7.128.0/20^20-29, 96.7.176.0/20^20-29, 96.7.192.0/20^20-29, 96.16.224.0/20^20-29, 96.17.16.0/20^20-29, 96.17.128.0/20^20-29, 113.20.0.0/20^20-29, 117.53.160.0/20^20-29, 117.55.224.0/20^20-29, 118.214.64.0/20^20-29, 118.214.96.0/20^20-29, 118.214.208.0/20^20-29, 118.215.32.0/20^20-29, 118.215.128.0/20^20-29, 118.215.160.0/20^20-29, 119.15.96.0/20^20-29, 119.148.64.0/20^20-29, 123.136.32.0/20^20-29, 125.252.192.0/20^20-29, 172.247.176.0/20^20-29, 173.222.64.0/20^20-29, 173.222.96.0/20^20-29, 173.223.64.0/20^20-29, 173.223.96.0/20^20-29, 180.235.192.0/20^20-29, 182.50.32.0/20^20-29, 184.50.96.0/20^20-29, 184.50.160.0/20^20-29, 184.50.208.0/20^20-29, 184.51.176.0/20^20-29, 184.51.224.0/20^20-29, 184.84.16.0/20^20-29, 184.84.112.0/20^20-29, 202.77.80.0/20^20-29, 202.79.160.0/20^20-29, 202.146.160.0/20^20-29, 202.174.96.0/20^20-29, 203.11.192.0/20^20-29, 203.33.80.0/20^20-29, 203.33.112.0/20^20-29, 203.83.224.0/20^20-29, 203.88.112.0/20^20-29, 203.104.0.0/20^20-29, 203.145.32.0/20^20-29, 209.131.96.0/20^20-29, 210.56.80.0/20^20-29, 59.151.128.0/21^21-29, 59.151.152.0/21^21-29, 59.151.160.0/21^21-29, 64.86.232.0/21^21-29, 72.246.216.0/21^21-29, 72.247.0.0/21^21-29, 72.247.104.0/21^21-29, 72.247.112.0/21^21-29, 88.221.88.0/21^21-29, 88.221.176.0/21^21-29, 88.221.200.0/21^21-29, 92.122.96.0/21^21-29, 92.122.208.0/21^21-29, 92.123.64.0/21^21-29, 95.101.88.0/21^21-29, 96.16.0.0/21^21-29, 96.16.40.0/21^21-29, 96.16.104.0/21^21-29, 96.16.112.0/21^21-29, 96.16.200.0/21^21-29, 111.118.192.0/21^21-29, 112.140.176.0/21^21-29, 114.141.96.0/21^21-29, 115.178.16.0/21^21-29, 116.0.16.0/21^21-29, 118.214.176.0/21^21-29, 118.215.48.0/21^21-29, 119.31.224.0/21^21-29, 119.63.208.0/21^21-29, 119.148.80.0/21^21-29, 119.160.232.0/21^21-29, 122.252.40.0/21^21-29, 122.252.56.0/21^21-29, 125.56.168.0/21^21-29, 125.214.80.0/21^21-29, 173.222.200.0/21^21-29, 173.223.144.0/21^21-29, 180.235.208.0/21^21-29, 184.84.168.0/21^21-29, 202.72.224.0/21^21-29, 202.125.168.0/21^21-29, 202.134.48.0/21^21-29, 203.16.208.0/21^21-29, 203.100.48.0/21^21-29, 203.145.56.0/21^21-29, 203.195.112.0/21^21-29, 203.222.120.0/21^21-29, 208.67.232.0/21^21-29, 210.5.32.0/21^21-29, 59.151.148.0/22^22-29, 59.151.184.0/22^22-29, 60.254.132.0/22^22-29, 60.254.140.0/22^22-29, 60.254.152.0/22^22-29, 60.254.168.0/22^22-29, 60.254.180.0/22^22-29, 72.246.32.0/22^22-29, 72.246.52.0/22^22-29, 72.246.60.0/22^22-29, 72.246.68.0/22^22-29, 72.246.76.0/22^22-29, 72.246.212.0/22^22-29, 72.246.252.0/22^22-29, 72.247.28.0/22^22-29, 72.247.240.0/22^22-29, 80.67.84.0/22^22-29, 84.53.132.0/22^22-29, 84.53.148.0/22^22-29, 84.53.156.0/22^22-29, 84.53.164.0/22^22-29, 84.53.176.0/22^22-29, 88.221.4.0/22^22-29, 88.221.40.0/22^22-29, 88.221.48.0/22^22-29, 88.221.60.0/22^22-29, 88.221.64.0/22^22-29, 88.221.76.0/22^22-29, 92.122.40.0/22^22-29, 92.122.92.0/22^22-29, 92.122.104.0/22^22-29, 92.122.124.0/22^22-29, 92.122.216.0/22^22-29, 92.123.72.0/22^22-29, 92.123.128.0/22^22-29, 92.123.148.0/22^22-29, 92.123.176.0/22^22-29, 92.123.196.0/22^22-29, 95.101.0.0/22^22-29, 95.101.44.0/22^22-29, 95.101.64.0/22^22-29, 95.101.84.0/22^22-29, 96.7.248.0/22^22-29, 96.16.96.0/22^22-29, 96.16.120.0/22^22-29, 96.16.164.0/22^22-29, 96.17.4.0/22^22-29, 96.17.172.0/22^22-29, 110.44.24.0/22^22-29, 113.20.24.0/22^22-29, 113.20.128.0/22^22-29, 113.29.240.0/22^22-29, 113.212.96.0/22^22-29, 114.111.132.0/22^22-29, 114.111.136.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 115.178.28.0/22^22-29, 118.214.184.0/22^22-29, 119.252.176.0/22^22-29, 120.29.196.0/22^22-29, 122.100.0.0/22^22-29, 122.252.36.0/22^22-29, 125.56.212.0/22^22-29, 164.108.8.0/22^22-29, 173.222.128.0/22^22-29, 173.222.176.0/22^22-29, 173.222.196.0/22^22-29, 173.222.220.0/22^22-29, 173.223.16.0/22^22-29, 173.223.48.0/22^22-29, 173.223.132.0/22^22-29, 173.223.140.0/22^22-29, 173.223.152.0/22^22-29, 173.223.172.0/22^22-29, 180.94.236.0/22^22-29, 180.235.216.0/22^22-29, 184.51.20.0/22^22-29, 184.51.92.0/22^22-29, 184.51.96.0/22^22-29, 184.51.196.0/22^22-29, 184.51.244.0/22^22-29, 184.84.160.0/22^22-29, 184.84.176.0/22^22-29, 202.65.12.0/22^22-29, 202.92.248.0/22^22-29, 202.151.36.0/22^22-29, 203.3.88.0/22^22-29, 203.4.168.0/22^22-29, 203.9.184.0/22^22-29, 203.14.156.0/22^22-29, 203.15.124.0/22^22-29, 203.17.208.0/22^22-29, 203.26.120.0/22^22-29, 203.28.48.0/22^22-29, 203.34.168.0/22^22-29, 203.56.204.0/22^22-29, 203.62.180.0/22^22-29, 203.62.216.0/22^22-29, 203.135.184.0/22^22-29, 203.145.48.0/22^22-29, 203.166.104.0/22^22-29, 203.191.36.0/22^22-29, 204.8.48.0/22^22-29, 210.11.52.0/22^22-29, 210.11.236.0/22^22-29, 60.254.130.0/23^23-29, 60.254.184.0/23^23-29, 61.69.8.0/23^23-29, 63.110.26.0/23^23-29, 69.45.84.0/23^23-29, 72.246.46.0/23^23-29, 72.246.48.0/23^23-29, 72.246.64.0/23^23-29, 72.246.94.0/23^23-29, 72.247.40.0/23^23-29, 72.247.146.0/23^23-29, 72.247.218.0/23^23-29, 72.247.238.0/23^23-29, 80.231.16.0/23^23-29, 80.231.162.0/23^23-29, 84.53.136.0/23^23-29, 84.53.142.0/23^23-29, 84.53.144.0/23^23-29, 84.53.174.0/23^23-29, 84.53.182.0/23^23-29, 92.122.122.0/23^23-29, 96.6.118.0/23^23-29, 96.6.122.0/23^23-29, 96.6.126.0/23^23-29, 96.7.40.0/23^23-29, 96.17.8.0/23^23-29, 96.17.104.0/23^23-29, 111.125.160.0/23^23-29, 111.125.168.0/23^23-29, 114.111.130.0/23^23-29, 114.111.140.0/23^23-29, 114.111.148.0/23^23-29, 114.141.108.0/23^23-29, 118.214.188.0/23^23-29, 119.160.224.0/23^23-29, 119.160.228.0/23^23-29, 120.29.192.0/23^23-29, 121.244.74.0/23^23-29, 121.244.136.0/23^23-29, 121.244.172.0/23^23-29, 121.244.190.0/23^23-29, 121.244.204.0/23^23-29, 122.100.4.0/23^23-29, 122.100.10.0/23^23-29, 122.100.12.0/23^23-29, 122.201.64.0/23^23-29, 125.56.184.0/23^23-29, 125.56.192.0/23^23-29, 125.56.210.0/23^23-29, 125.56.222.0/23^23-29, 164.108.12.0/23^23-29, 165.86.70.0/23^23-29, 165.86.80.0/23^23-29, 184.50.26.0/23^23-29, 192.52.72.0/23^23-29, 193.108.88.0/23^23-29, 193.108.94.0/23^23-29, 193.108.152.0/23^23-29, 202.6.42.0/23^23-29, 202.41.194.0/23^23-29, 202.44.98.0/23^23-29, 202.150.60.0/23^23-29, 203.6.146.0/23^23-29, 203.8.128.0/23^23-29, 203.10.130.0/23^23-29, 203.12.244.0/23^23-29, 203.15.106.0/23^23-29, 203.16.230.0/23^23-29, 203.18.16.0/23^23-29, 203.18.108.0/23^23-29, 203.18.242.0/23^23-29, 203.20.68.0/23^23-29, 203.20.228.0/23^23-29, 203.23.138.0/23^23-29, 203.24.64.0/23^23-29, 203.26.94.0/23^23-29, 203.27.114.0/23^23-29, 203.27.214.0/23^23-29, 203.28.46.0/23^23-29, 203.28.176.0/23^23-29, 203.31.240.0/23^23-29, 203.33.18.0/23^23-29, 203.33.152.0/23^23-29, 203.33.220.0/23^23-29, 203.55.40.0/23^23-29, 203.55.46.0/23^23-29, 203.55.62.0/23^23-29, 203.55.140.0/23^23-29, 203.55.248.0/23^23-29, 203.63.24.0/23^23-29, 203.87.192.0/23^23-29, 203.119.14.0/23^23-29, 203.222.90.0/23^23-29, 204.10.30.0/23^23-29, 210.9.2.0/23^23-29, 210.9.42.0/23^23-29, 210.9.132.0/23^23-29, 210.9.186.0/23^23-29, 210.10.118.0/23^23-29, 210.11.220.0/23^23-29, 8.3.213.0/24^24-29, 60.254.129.0/24^24-29, 60.254.149.0/24^24-29, 60.254.151.0/24^24-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100317 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Mar '10

16 Mar '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.78.240.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100302 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.78.240.0/21^21-29, 202.46.190.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100317 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Vodafone NZ Broadband Issues
by Richard Naylor 15 Mar '10

15 Mar '10

At 08:38 p.m. 16/03/2010, Mauricio Freitas wrote: >Vodafone is trying to get people to use the other APNs, because >"internet" was a test APN with a limited number of IP addresses >available. They have changed the www.vodafone.net.nz to give a >public IP address instead of NAT. It's still restricted to outbound >connections only. A HUGE issue. >I updated the list last week on request of VFNZ: >http://www.geekzone.co.nz/forums.asp?forumid=40&topicid=9780 Thanks Mauricio - much appreciated. However the constant changes of APN names and VF's definition of "broadband" being somewhat different to mine finally got to me and we cancelled all but one of our VF accesses. On the other hand Telecom XT rocks along nicely and where it struggles we add a 27dBi aerial or go to satellite. We had to ask about XTs APNs but they don't seem to change and really really work well. Even the broadcasters are using XT now for live News feeds. We also use Telecom's CDMA as EVDO Rev A and it also rocks along with no IP filters. It also works with our 27dBi aerial. As an aside we (almost) regularly get fill-in work doing video conferences for folks who either want it at short notice, or in a place with limited resources. VC work is traditionally ISDN based (remember that stuff ?) and clients leave it too late to get circuits. So XT runs a 256k or 384k VC session very nicely and the 8GB data caps last a few more days than the old 1GB stuff. To make the VC work we don't want any filter stuff in the way. Just the bandwidth Man, just the bandwidth. R

1 0