- NZNOG - lists.nznog.org

SkyTV geoblock
by Brad Cook 20 Mar '18

20 Mar '18

reaching out, is anyone from SkyTV able to contact me off-list, we have some ranges that are geoblocked.

2 1

IPv6 static addressing
by Richard Hector 16 Mar '18

16 Mar '18

Hi all, Apologies if this is a bit off-topic, but I know there's lots of IPv6 knowledge here :-) If I have an IPv6 ULA block (or several) using SLAAC, and I want to additionally give out some static addresses in one or more of those blocks, am I right in thinking I can pick anything I like as long as it doesn't have the magic fffe in the middle? Is there a more formal approach? Is this (SLAAC plus statics where required) the normal way of doing things? Thanks, Richard

2 3

Update from DNCL regarding WHOIS
by Daniel Griggs 15 Mar '18

15 Mar '18

Hi Everybody, DNCL attended the NZNOG conference in January, and talked about the policy consultation on Port 43 WHOIS requirements. You can read more about that consultation and the submissions here https://dnc.org.nz/port-43. Thanks to those NZNOG members who provided a submission. The DNCL Board has considered all submissions, and decided that the information returned via Port 43 will be reduced. Port 43 queries will continue to show domain name availability, Registrar contact details and name server details (including DS records). It will no longer show contact details of Registrant, Admin or Technical contacts, or the date billed until information. Though this information will still be available on the DNCL website (http://www.dnc.org.nz/) DNCL and InternetNZ/NZRS are working on a plan to implement the changes in early April 2018. If you have any questions regarding the process or decision feel free to drop a line to info(a)dnc.org.nz -- Daniel Griggs e: daniel(a)internetnz.net.nz p: +64 27 448 8230

1 0

Range Announcements ExChristchurch - Please update your GeoCoding as required.
by Don Gould 14 Mar '18

14 Mar '18

For those GeoCoding... Please be advised that we're announcing the follow exChristchurch. as=45887 router-id=202.68.88.218 network=103.68.122.0/24 network=103.68.123.0/24 network=103.68.121.0/24 network=117.121.244.0/24 network=182.54.234.0/24 TVNZ, MediaWorks... my wife would like your service back... NetFlix my wife liked her 2 days with the 'extended catalogue'... guess we can't have pie and eat it to! ;) D -- Don Gould 5 Cargill Place Richmond Christchurch, New Zealand Ph: + 64 3 348 7235 Mobile: + 64 21 114 0699 Ph: +61 3 9111 1821 (Melb) www.bowenvale.co.nz skype: don.gould.nz -- Don Gould 31 Acheson Ave Mairehau Christchurch, New Zealand Ph: + 64 3 348 7235 Ph: 0800 00 15 92 Mobile: + 64 21 114 0699 Ph: +61 3 9111 1821 (Melb) www.yournet.co.nz skype: don.gould.nz

1 0

Looking for spare Xirrus XS-8 wireless devices
by Matt Stevens 13 Mar '18

13 Mar '18

Greetings, Victoria Uni, School of Engineering and Computer Science is heading to Samoa in April to do outreach to local Universities and High Schools. To help out we have been donated six Xirrus XS-8 wireless points to install. A big thank you to our donor :-) Having figured out how to install these, we are now thinking that it may be useful to have spare devices. Either spares for the local IT team for when the installed ones give up or to increase coverage. So... do you have any used/replaced Xirrus XS-8 wireless devices lying around, that you might be happy to donate? Brackets for these devices are also in short supply and it turns out, expensive to fabricate. Thank you for reading and please send me any responses off-list. Cheers! Matt Stevens Work Experience Coordinator Engineering and Computer Science Victoria University of Wellington

1 0

Asbestos in Remuera?
by Brian E Carpenter 01 Mar '18

01 Mar '18

Hi, Is anyone aware of access problems (asbestos issues) at the Remuera exchange? I'm being given the run-around by Chorus - just moved and no local loop for the last 10 days. (Yes, I know I should upgrade to fibre but that is stage 2.) This is a personal gripe but if the access problem is genuine it probably affects many subscribers. An off list reply would be fine. Regards Brian Carpenter

1 0

Removing the four stale TAL from the APNIC RPKI validation set.
by George Michaelson 26 Feb '18

26 Feb '18

Updating RPKI trust anchor configuration ------------------------------------------------------- APNIC has completed the process of transitioning from its previous Resource Public Key Infrastructure (RPKI) trust anchor arrangement to a new single trust anchor configuration. Each RIR will publish an 'all resources' global trust anchor, under which its own regional resources (IP addresses and ASNs) will be certified. APNICs trust anchor is one of the previous five, which has been retained as the sole trust anchor over all APNIC resource certificate products. If you are using relying-party software, such as the Dragon Research Labs RPKI Toolkit, RPSTIR or the RIPE NCC’s RPKI Validator, you are advised to update your software’s configuration to use only the current APNIC trust anchor, rather than the set of five APNIC trust anchors that were previously in use. The update is to remove four of the five: One has been retained as the current live Trust Anchor. Note: this update is not critical. However, if it is not done, the software will log or report warnings about being unable to retrieve the trust anchors that are no longer being used. All resources now validate under the single active trust anchor and no orphan products are valid under the other prior trust anchors. The current APNIC TAL is as follows: ------ rsync://rpki.apnic.net/repository/apnic-rpki-root-iana-origin.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx9RWSL61YAAYumEiU8z8 qH2ETVIL01ilxZlzIL9JYSORMN5Cmtf8V2JblIealSqgOTGjvSjEsiV73s67zYQI 7C/iSOb96uf3/s86NqbxDiFQGN8qG7RNcdgVuUlAidl8WxvLNI8VhqbAB5uSg/Mr LeSOvXRja041VptAxIhcGzDMvlAJRwkrYK/Mo8P4E2rSQgwqCgae0ebY1CsJ3Cjf i67C1nw7oXqJJovvXJ4apGmEv8az23OLC6Ki54Ul/E6xk227BFttqFV3YMtKx42H cCcDVZZy01n7JjzvO8ccaXmHIgR7utnqhBRNNq5Xc5ZhbkrUsNtiJmrZzVlgU6Ou 0wIDAQAB ------ Configuring Relying Party Software ----------------------------------------------- RIPE NCC RPKI Validator: If you upgrade to RIPE validator rpki-validator-app-2.24 the correct Trust Anchor is configured. No further work is required. Dragon Research Labs Rcynic Validator: If you run rcynic, you need to remove all the TAL, TA or CER entries in rcynic.conf except ones which point to apnic-rpki-root-iana-origin.cer or the related TAL. If you use the trusted-certs/ directory, simply remove the four files which are named for the non-APNIC RIR as follows: cd /etc/trust-anchors # or wherever you place the TAL files rm apnic-rpki-root-ripe-origin.tal rm apnic-rpki-root-arin-origin.tal rm apnic-rpki-root-lacnic-origin.tal rm apnic-rpki-root-afrinic-origin.tal RPSTIR To modify an installed RPSTIR system, locate the /usr/local/etc/rpstir directory and remove all but the current live APNIC TAL. More information is in the attached PDF describing how to update the trust anchor configuration in these three popular relying-partner software systems. -George

1 0

Survey
by Richard Nelson 15 Feb '18

15 Feb '18

Thankyou to everybody who responded to the NZNOG survey, the results are in and are very useful to us. Geoff Huston was considered a top three speaker most often followed by Francesco Alberti of Eolo. Hamid Maani of Hawaiki and Kraig Winters representing the Red Cross were third equal with a large group just behind them. More importantly almost all the speakers were considered interesting by someone attending the conference so we are pleased with the programme reception. Respondents liked Queenstown but didn't like the venue. They wanted desks in the conference and aircon in the rooms. The most popular destination choices for next years conference were Napier, Wellington and New Plymouth. This fairly closely corresponds with the trustees' thinking so we will check them out for venues and accommodation with air conditioned rooms. It will, however, be difficult to top jet boating as a social activity. Just over 90% of people are open to us changing the conference dates. We will investigate this. There were almost no other conferences identified to avoid clashes with but public holidays are clearly sancrosanct. There was also a suggestion that we avoid school holdiays which we currently don't do. People are happy for us to make the conference a bit bigger to make sure people don't miss out. There were also a lot of individual comments and suggestions that we will try to take on board. Richard Nelson

4 4

Re: [nznog] Survey
by Ewen McNeill 11 Feb '18

11 Feb '18

On 9/02/18 13:11, Barry Murphy wrote: > May be quite beneficial to have NZNog the week after, so those that have travelled > from AU the week before can stick around for another week and attend NZNog Could definitely work out. I can think of at least a half dozen Australia-nbased Linux.Conf.au regulars, who would probably come to LCA2019 in Christchurch too, working in networks/network operations as their day job. There's probably more who would find it relevant if it was easy to get to after Linux.Conf.au (Christchurch/Wellington is an easy regular flight; not sure about Christchurch/New Plymouth or Christchurch/Napier -- those might be two flights). (The week before might work too, but some of the people I'm thinking of usually help with LCA conference setup, which obviously is the end of the week before the conference...) Ewen

4 3

Looking for DNS resolver addresses in NZ for research project
by Sebastian Castro 01 Feb '18

01 Feb '18

Hi everyone: In case you haven't seen a message from me before, I'm Sebastian Castro, Technical Research Manager for NZRS, part of the InternetNZ team. Our Research Team has been conducting some research work on passive DNS analysis in order to identify real DNS resolvers in the wild, as authoritative DNS servers like the .nz nameservers get a lot of rubbish traffic. In order to advance the work, we are looking for some ground truth about real DNS resolvers in NZ. We have a list of known resolvers from organizatons like Spark, Vodafone, some ISPs, but we are looking to extend and refresh that list. If you operate a network that has a resolver, would you be so kind to share with us the IP addresses (both v4 and v6 if available) the resolver uses to send traffic? Depending on your architecture, it could be the address your users setup in their configuration, or a different address based on location where there is a load balancing architecture. There is no restriction: we want big and small resolvers, ISPs, Wireless ISPS, educational organizations, big and small companies, everything helps. The list won't be made public, it will be used for our research purposes. Thanks in advance and enjoy your Waitangi weekend. -- Sebastian Castro Technical Research Manager NZRS Ltd. desk: +64 4 495 2337 mobile: +64 21 400535

1 0