AS13414 is now peering in Australia. We invite AU/NZ eyeball networks to
peer with us on the Equinix, IX Australia, and Megaport IXs in Sydney.
Please find our details at http://as13414.peeringdb.com, and contact
peering(a)twitter.com if this is of interest to you.
Tim Hoffman | Twitter, Inc.
1355 Market St. | San Francisco, CA | 94103
We said in Rotorua we'd be keen to subsidise Apricot attendance in 2016.
And if memory serves correctly it was for any of the diehard Noggers that
always turn up to our conference. We must have had a rush of blood to the
head at the time because it turns out we could do that and probably burn
out the NZNOG Trust fund at the same time. That's not wise.
Now that we've thought about it, what we can do is make 5K NZD available to
those who $deserve a subsidy. What we have not worked out is how to define
$deserve. But I'm sure we'll work that out. We can update you on that
later. There will be some kind of metric related to how much of diehard
Nogger you are I guess. Maybe in the meantime you could entertain the list
about just how diehard you are. Perhaps the subsidies go to the ones who
create the most mirth (whilst staying within the list AUP of course).
On a more serious note - just thought we should keep you updated, and we'll
advise more a little later as things firm up.
Jamie of behalf of the NZNOG Trustees
--- scott(a)scottpettit.nz wrote:
From: Scott Pettit <scott(a)scottpettit.nz>
puff piece designed to spread FUD for Digital Island's own
Funny, I worked for another Digital Island that existed in
Hawaii from the mid-1990s to ~2002. We had PoPs all over
the world including NZ. It was bought by C&W and these
guys took up the name 2 years later according to their
"about us" page. Until now I never heard of them...
NZNOG mailing list
A quick heads up about our experience on Akl-IX (community IX based in
Auckland, presence in 220 Queen and Vocus Albany).
This past week we've seen our traffic coming in via the IX double, in part
thanks to Microsoft peering and the Windows 10 updates that are hammering
everyone's networks right now :)
Also recent growth in peers - I see Compass are on-boarding and a couple of
other operators I've spoken with are peering shortly.
There are some large content providers on the IX, either directly connected
or via "host member ISPs" - so if you've been considering peering and
access to content might be a driver for on-boarding and you would like some
more info, please speak to Joe Wooller of WAIA on peering(a)akl-ix.nz or you
can drop me an email.
If you're from:
...I'd love to see you on the IX as we do a bit of traffic each day and the
current inbound and outbound paths are not as optimal as they could be.
*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 16306, Bethlehem 3176, New Zealand
I wanted to notify the list that anyone operating recursive resolvers would
be wise to flush the following zones from the cache:
Lastnight the name servers for these where switched to ns1, ns2 and
The TTL on the NS record was 24hrs at the time of change so these could
still be in cache as the old record.
The Chorus Co-Innovation Lab (CCIL) is being upgraded to a new software release in preparation for a UFB production upgrade later this year.
The Wellington and Auckland nodes will bounce several times today and tomorrow, as we exercise the upgrade and rollback procedures.
Network Specialist Layer 2
+64 4 896 4190
+64 27 514 8048
Level 8, State Insurance Tower, 1 Willis Street
Aon Hewitt Best Employer in Australasia 2012 & 2013
P Please consider the environment before printing this e-mail
This communication, including any attachments, is confidential and may be legally privileged. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. No confidentiality or privilege is waived or lost by any mis-transmission or error. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
Since it seems to be ipv6 month here at NZNog I thought I would bring this up.
Some of you have commented that Orcon is in trial mode for IPv6 and are probably wondering why we haven’t progressed.
We have had IPV6 enabled for a while and have a good number of ipv6 customers online now. However we found an issue on the Chorus network which stopped us rolling it out further. (UFB ipv6 was another battle which requires beer!)
What we found was some Chrous DSLAMS with certain card types would drop IPV6CP packets in one direction when doing the PPPoE->PPPoA conversation. It would seem that these cards don’t support Ipv6. Weirdly enough it would seem it is the newer card types used for Broadband IP. (citation needed). This in itself isn’t a major but we also found our NFV4 modem would reset its entire PPPoE stack if the IPV6CP conversation started but didn’t complete as expected, so customers would constantly be disconnected and cycle around. (The Genius modem works well with ipv6)
The NFV4 issue aside (we are resolving with the Vendor). We approached the Chorus tech team and they helped identify the issue but that’s is where its hit a brick wall. The Chorus op team are not keen on fixing the issue nationwide as it involves new code versions, a massive amount of testing and a long rollout program. (I can understand where they are coming from).
IPV6 doesn’t work on Chorus EUBA on some line card types
Only affect PPPoE->PPPoA translation
PPPoE end to end is fine.
Chorus say IPV6 not supported on EUBA
Customer numbers effected are smallish.
We will fix the NFV4 issue, but keen to rollout more IPV6 to all customers, not just the lucky ones on card types which work.
Has any other ISP’s (the bigger ones especially) noticed this? As it will require some pressure to get some progress.
Simon Allard // Senior Network Architect
D: 09 550 2790 M: 020 100 0790 F:
www.callplus.co.nz<http://www.callplus.co.nz> | www.slingshot.co.nz<http://www.slingshot.co.nz> | www.flip.co.nz<http://www.flip.co.nz> | www.orcon.net.nz<http://www.orcon.net.nz>
This message and any attachments contain privileged and confidential information. If you
are not the intended recipient of this message, you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify the sender immediately via email
and then destroy this message and any attachments.
On the off chance that someone else has seen this before and knows what
causes it, does anyone know of any software that generates ARP
_Requests_ with the Target Protocol Address (TPA) of 255.255.255.255
(all ones). Such that results in this sort of log message from picky
<188> Jul 29 10:47:13 [SWITCH] ARP[ipMapForwarding]:
ipmap_arp_api.c(1147) 1021154 %% Received ARP Request on interface Vl1
with bad target IP address 255.255.255.255. Sender IP is [REALIP],
sender MAC is [REALMAC].
As far as I can tell they happen _approximately_ every 5 minutes, but
definitely not to the second. I'm told the Sender IP is a relatively
old Windows host, but the Windows admins don't know of anything
installed which would do that.
Searching the Internet doesn't turn up much. I did find UNARP
(https://tools.ietf.org/html/rfc1868), but that's supposed to be an
unsolicited ARP _Reply_, and this is a Request; and besides this isn't
the scenario UNARP was invented for anyway. The only other speculation
I can find is maybe it's a gratuitous ARP that doesn't follow RFC5227
(https://tools.ietf.org/html/rfc5227; which says that Target Protocol
Address should be set to the address you want to claim), but that also
seems implausible (especially since the DHCP leases at this site are
longer than 5/10 minutes).
Any thoughts as to what might be generating it welcomed.
PS: This is not the ARP being _broadcast_ to the all address
255.255.255.255; that happens all the time on requests. This is asking