- NZNOG - lists.nznog.org

Network atlas november 2018 update
by Mehmet Akcin 05 Nov '18

05 Nov '18

Hello everyone, We wanted to share several updates about our project Network Atlas with you. First of all we are very excited to announce now our page has many more features (and more to come) and hosted in a much more robust platform at www.networkatlas.org We've recently made a press release about our project , https://finance.yahoo.com/news/network-atlas-launches-map-global-221500875.… Now we are working on two major tracks 1) Raising funds via sponsorship and our kickstarter to be able to afford future of developments. 2) Talking to engineers , network professionals to understand what would make this tool better everyone. As you might be already aware we have a slack channel you can join and discuss/help the project. here is the slack channel link - https://join.slack.com/t/kapany/shared_invite/enQtNDUwOTIzMDEwODM4LWE5NjNmO… Overall we need network operators who have access to networks/fibre/route information and operational status as we are developing our self service portal which via GUI and API will enable you to be able to provide status of global fibre optic cables, and receive updates the same way. For more information about this project, and other ideas feel free to join our slack or email me directly at mehmet(a)networkatlas.org thank you and we will follow up with further updates in December 2018! We are very excited how far we came so far providing more visibility already ( even though we are just in demo state ) Mehmet Network Atlas https://angel.co/mhmtkcn

1 0

TICSA annual update required in November
by ticsa＠police.govt.nz 04 Nov '18

04 Nov '18

Hello NZNOG A reminder to all New Zealand Network Operators that it is November again, which means its time for your Designated Contacts to ensure the Chief Executive completes your annual TICSA update. Complete the update here -- TICSA Registration Portal: https://services.police.govt.nz/ticsa Information -- Police TICSA webpage: https://www.police.govt.nz/advice/businesses-and-organisations/ticsa Portal Issues -- Contact NZ Police TICSA Team: https://forms.police.govt.nz/forms/contact-ticsa-registrar/57 TICSA Legislation - Link to the act: http://www.legislation.govt.nz/act/public/2013/0091/latest/DLM5177923.html Excerpt from the act: ------------------------------------------------------------------------------------------------------ 69 Annual update (1) A network operator must give to the Registrar each year in November an annual update of information on the register relating to that operator. (2) The annual update must— (a) specify any changes to the information referred to in section 62 that have occurred since the network operator last gave information to the Registrar (whether in a notice under section 68, the previous annual update, or an application under section 61); and (b) confirm that, apart from the changes under paragraph (a), all other information referred to in section 62 that is currently held by the Registrar remains correct; and (c) be in the form (if any) required by the Registrar; and (d) be accompanied by a certificate signed by the chief executive of the network operator confirming that the information contained in the annual update is true and correct. (3) An annual update does not need to be provided in the year during which this section comes into force. ------------------------------------------------------------------------------------------------------ Thank you NZ Police TICSA Team. =============================================================== WARNING The information contained in this email message is intended for the addressee only and may contain privileged information. It may also be subject to the provisions of section 50 of the Policing Act 2008, which creates an offence to have unlawful possession of Police property. If you are not the intended recipient of this message or have received this message in error, you must not peruse, use, distribute or copy this message or any of its contents. Also note, the views expressed in this message may not necessarily reflect those of the New Zealand Police. If you have received this message in error, please email or telephone the sender immediately

1 0

Papamoa UFF fibre outage
by Jesse Archer 31 Oct '18

31 Oct '18

Hey All, Did anyone get more details (or photos!) on the massive Ultrafast Fibre outage in Papamoa? https://ultrafastfibre.statuspage.io The fibre strike happened on Monday afternoon, the outage looks set to be resolved tonight (more than 48 hours since the outage began) which must be a record on the UFF network to date. *Jesse Archer* *General Manager*Full Flavour *p. *07 577 0099 *ddi*. 07 281 1391 *s*. Skype "myfullflavour" *e*. jesse(a)fullflavour.nz <jesse(a)fullflavourmedia.co.nz> *w*. fullflavour.nz <http://www.fullflavourmedia.co.nz/> *a. *Basestation, 148 Durham Street, Tauranga *a*. PO Box 13403, Tauranga Central, Tauranga 3141, New Zealand

5 5

NZNOG2019 CFP
by Richard Nelson 24 Oct '18

24 Oct '18

Yep, it is that time again... The NZNOG trustees invite papers for the 16th annual NZNOG conference, to be hosted at the Napier Conference Centre on 31 Jan and 1 Feb 2019. With the conference there will be a three day Workshop 28-30 Jan and a day of tutorials on 30 Jan. Conference objective: The NZNOG conference, workshops and tutorials are a once-a-year opportunity for individuals and organisations involved in Internet operations to meet and share the latest in Internet operations, technologies, practices and receive high quality training. The event is unique in New Zealand and attracts technical, skilled individuals with a genuine interest in Internet operations and Internetworking technologies. Submissions on any aspect of networking are welcome however we are particularly interested in talks that involve real world deployment experience, particularly in New Zealand. Submit a paper: Presenters are invited to submit talk proposals for consideration by Monday 29 Oct. Please provide your talk title, a short presenter bio and an abstract of the talk. Abstracts should be no more than one page long and provide a summary of your networking related subject matter. Normally presentations 30 min long, are video streamed live and slide decks are posted to the NZNOG website. If you want a different duration or other arrangements you need to let us know at submission time To submit your paper please e-mail: talks(a)nznog.org Proposals will be evaluated on fit with the conference’s objective and its ability to stimulate lively discussions around the current state of New Zealand networking. This call for submissions can also be found at: http://www.nznog.org/nznog-2019/call-for-papers-2019 For more information about the conference visit www.nznog.org or contact: talks(a)nznog.org

2 1

Re: [nznog] Hurricane Electric joining APE
by Sid Jones 23 Oct '18

23 Oct '18

FYI: We will be standing up the first session tomorrow from 10am rs2.ape.nzix.net 192.203.154.2 2001:7fa:4:c0cb::9a02 From: <nznog-bounces(a)list.waikato.ac.nz> on behalf of Todd Dickason <todd.dickason(a)citylink.co.nz> Date: Thursday, 18 October 2018 at 17:31 To: "nznog(a)list.waikato.ac.nz" <nznog(a)list.waikato.ac.nz> Subject: [nznog] Hurricane Electric joining APE Hello APE peers (and NZNOG), A heads up from CityLink Peering (http://nzix.net) Hurricane Electric (AS6939) are in the process of connecting to the Auckland Peering Exchange (APE) and you can expect to see an increase in the number of prefixes once they're connected. We'll send another post to NZNOG when we've a confirmed turn-up date. We're going to follow the sensible lead of ix.nz here (credit where it's due Joe) and only open the filters for Hurricane Electric up on one of our route servers (rs2.ape.nzix.net) initially. We'll open up rs1.ape.nzix.net when we see all peers functioning normally on rs2.ape.nzix.net. Hurricane Electric have advised us that they will advertise approximately 28,000 IPv6 routes and up to 57,000 IPv4 routes initially. Additionally they've suggested prefix limit adjustments to cater for increases from them of 65k IPv6 and 175k IPv4 routes. FYI: our details AS9560 rs1.ape.nzix.net, 192.203.154.1, 2001:7fa:4:c0cb::9a01 rs2.ape.nzix.net, 192.203.154.2, 2001:7fa:4:c0cb::9a02 Any queries for our customers who are on-list please email us at peering(a)citylink.co.nz<mailto:peering(a)citylink.co.nz>. Cheers Todd CityLink/TeamTalk Ops

4 5

Re: [nznog] Hurricane Electric joining APE
by Walt 19 Oct '18

19 Oct '18

We are very close When we do go live we value bilateral sessions more than over the route servers Please email peering(a)he.net to get a bilateral session Thanks Walt From: <nznog-bounces(a)list.waikato.ac.nz<mailto:nznog-bounces(a)list.waikato.ac.nz>> on behalf of Todd Dickason <todd.dickason(a)citylink.co.nz<mailto:todd.dickason(a)citylink.co.nz>> Date: Wednesday, October 17, 2018 at 9:31 PM To: "nznog(a)list.waikato.ac.nz<mailto:nznog(a)list.waikato.ac.nz>" <nznog(a)list.waikato.ac.nz<mailto:nznog(a)list.waikato.ac.nz>> Subject: [nznog] Hurricane Electric joining APE Hello APE peers (and NZNOG), A heads up from CityLink Peering (http://nzix.net) Hurricane Electric (AS6939) are in the process of connecting to the Auckland Peering Exchange (APE) and you can expect to see an increase in the number of prefixes once they're connected. We'll send another post to NZNOG when we've a confirmed turn-up date. We're going to follow the sensible lead of ix.nz here (credit where it's due Joe) and only open the filters for Hurricane Electric up on one of our route servers (rs2.ape.nzix.net) initially. We'll open up rs1.ape.nzix.net when we see all peers functioning normally on rs2.ape.nzix.net. Hurricane Electric have advised us that they will advertise approximately 28,000 IPv6 routes and up to 57,000 IPv4 routes initially. Additionally they've suggested prefix limit adjustments to cater for increases from them of 65k IPv6 and 175k IPv4 routes. FYI: our details AS9560 rs1.ape.nzix.net, 192.203.154.1, 2001:7fa:4:c0cb::9a01 rs2.ape.nzix.net, 192.203.154.2, 2001:7fa:4:c0cb::9a02 Any queries for our customers who are on-list please email us at peering(a)citylink.co.nz<mailto:peering(a)citylink.co.nz>. Cheers Todd CityLink/TeamTalk Ops

1 0

Hurricane Electric joining APE
by Todd Dickason 17 Oct '18

17 Oct '18

Hello APE peers (and NZNOG), A heads up from CityLink Peering (http://nzix.net) Hurricane Electric (AS6939) are in the process of connecting to the Auckland Peering Exchange (APE) and you can expect to see an increase in the number of prefixes once they're connected. We'll send another post to NZNOG when we've a confirmed turn-up date. We're going to follow the sensible lead of ix.nz here (credit where it's due Joe) and only open the filters for Hurricane Electric up on one of our route servers (rs2.ape.nzix.net) initially. We'll open up rs1.ape.nzix.net when we see all peers functioning normally on rs2.ape.nzix.net. Hurricane Electric have advised us that they will advertise approximately 28,000 IPv6 routes and up to 57,000 IPv4 routes initially. Additionally they've suggested prefix limit adjustments to cater for increases from them of 65k IPv6 and 175k IPv4 routes. FYI: our details AS9560 rs1.ape.nzix.net, 192.203.154.1, 2001:7fa:4:c0cb::9a01 rs2.ape.nzix.net, 192.203.154.2, 2001:7fa:4:c0cb::9a02 Any queries for our customers who are on-list please email us at peering(a)citylink.co.nz<mailto:peering(a)citylink.co.nz>. Cheers Todd CityLink/TeamTalk Ops

1 0

Internet for Kiwicon
by Mike Forbes 15 Oct '18

15 Oct '18

Could I have some contacts off list that would be willing to help out Kiwicon with a dedicated / reliable / fast internet link? Requirements are a fast (at least 100Mbit) connection and mostly international traffic (video streaming, CTF hosted in AWS Sydney) We're operating out of the Michael Fowler Centre in Wellington on the 15/16/17 November. The building is lit with Citylink fibre but Citylink are unable to help. Kiwicon is non profiting but we do have cash to make this happen, and i'd like to get it sorted! Thanks, Mike

1 0

LCA2019 Sysadmin Miniconf -- Call for Presentations
by Ewen McNeill 10 Oct '18

10 Oct '18

Linux.Conf.Au 2019 is being held in Christchurch, New Zealand near the end of January 2019 (21-25 January), the week before NZNOG 2019 (http://www.nznog.org/nznog-2019) -- thanks to NZNOG for moving from their regular slot to make it possible for those of us who like to attend both conferences. LCA2019 early bird tickets are on sale this month (https://linux.conf.au/attend/tickets/) As usual at LCA, we (Simon Lyall and I) are running a System Administration Miniconf as part of LCA2019, and I'd be quite keen to see some networking-related presentations. Perhaps someone would like to talk about GNS3 for network lab simulation? Or using Ansible / Salt for network configuration automation? Or anything around network monitoring/management. Or high performance networking on commodity hardware controlled by Linux? The LCA2019 Sysadmin Miniconf Call for Presentations is at: http://sysadmin.miniconf.org/cfp19.html and the text is included below for your convenience. Ewen PS: The Sysadmin Miniconf is part of LCA2019, so you'll need a ticket to LCA2019 to attend/speak the Sysadmin Miniconf or any other LCA2019 Miniconf. -=- cut here -=- Call for Presentations Linux.conf.au 2019 Systems Administration Miniconf There will be a one day mini conference on Linux Systems Administration held as part of linux.conf.au 2019. LCA2019 will be held in Christchurch, New Zealand on 21 - 25 January 2019. The organisers of the Systems Administration Miniconf would like to invite proposals for presentations to be delivered at the Miniconf. Please forward this CFP to your colleagues, peers, social networks, and other relevant mailing lists. Please help by encouraging submissions from people you would like to hear present at this Miniconf. This is our 13th Sysadmin Miniconf at Linux.conf.au. Previous presentations can be found at the website: https://sysadmin.miniconf.org/. Presentation Topics =================== We welcome talks on best current practice, new developments in Systems Administration, cutting edge techniques and technologies, and ways to better manage Linux environments large and small. Topics for presentations could include (but are not limited to): Virtualisation and Cloud Computing Kubernetes / Docker / Containers / Orchestration Infrastructure/Platform/Software as a Service (IAAS, PAAS, SAAS) Sysadmin Administration in a "serverless" environment (FAAS) DevOps and SysAdmin Culture Systems Administration Best Practice Monitoring and metrics. Collection, storage and presentation Networkng: IPv6, SDN (Software Defined Networking), performance DevOps, Configuration Management and provisioning Bootstrapping systems, Lifecycle Management Dealing with BYOD Backups in a virtual/distributed world Troubleshooting techniques Keeping legacy systems functioning War stories from the "Real World" Presentations should be of a technical nature and speakers should assume that members of the audience have at least a couple of years experience in professional Unix/Linux administration (many in the audience will have decades of experience). Format of Presentations ======================= We are now seeking proposals for presentations at the mini-conference. We have openings for: 15-25 minute short presentations 5-10 minute "lightning talks" Please note, due to the single day available (and whole-LCA opening before morning tea), we expect the majority of available timeslots to be 20 minutes or less, with possibly 1-2 slightly longer talks if there is space in the schedule. We have a general policy of accepting a high proportion of proposals but handing out relatively short timeslots. Please see previous years Miniconf schedules for examples of how the programme is organised. Submitting talks ================ Please note that in order to give a presentation or attend the Miniconf you must be registered (and paid up by the time the conference happens) for the main linux.conf.au conference. Presenting at the Miniconf does not entitle you to discounted or free registration at the main conference nor to priority with registration. Unfortunately the Miniconf has no budget for sponsorship of speakers. To submit a talk to the LCA2019 Sysadmin Miniconf, create an account on the LCA2019 website: https://linux.conf.au/dashboard create a speaker profile, and then select "SysAdmin Miniconf Talk" (in the "New Proposal" section of the Dashboard), or while logged into the LCA2019 site, go directly to: https://linux.conf.au/proposals/submit/sysadmin-miniconf/ Please pick a preferred length for your presentation from Short Presentation (15/20/25 minutes) or Lightning Talk (5/10 minutes) in the submission form; if you could do either (with more or less detail) use the Private Abstract field to describe the options and what you would prefer. In some cases we maybe able to add a few extra minutes to a few Short Presentations if there is any spare time left in the programme. Use the Private Abstract field to let us know a few more minutes would be useful for your presentation. Questions should be sent to: lca2019 at sysadmin.miniconf.org Dates and Deadlines =================== To encourage early submissions, priority (both of inclusion and scheduling) will be given to presentations submitted by 23:59 (any time zone) on 31st of October 2018. If you have a good presentation idea, please let us know early, even if you need time to finalise the presentation abstract. Please let us know directly if you need an early confirmation to assist you in arranging time off work or travel; we will do our best to help. 2018-10-31 - Deadline for early submissions 2018-11-18 - Deadline for submissions 2018-12-04 - LCA2019 Sysadmin Miniconf programme published 2019-01-21 - LCA2019 Sysadmin Miniconf held (Christchurch, NZ) Contact and Questions ===================== Please see our website at https://sysadmin.miniconf.org for more information on the miniconf, past presentations and presenting at it. If you have any questions please feel free to email the organisers at: lca2019 at sysadmin.miniconf.org -=- cut here -=-

1 0

new subnet not accepted by smx
by Paul Willard 09 Oct '18

09 Oct '18

Anybody here from smx? I'm advertising a new subnet. Upstream (vocus) suggests that smx may have incorrect routes? Contact me off list paul(a)paulwillard.nz

1 0