- NZNOG - lists.nznog.org

Fwd: Re: [mailop] Wildcarding of AHBL public DNSbl lists on Jan 1st
by Thom Hooker 04 Jan '15

04 Jan '15

(Apologies if you've seen this notification from the mailop list already. ) See the post below re: the AHBL RBL wildcarding certain zones today. There are NZ ASs in the latest CSV lists in the link below (Vodafone NZ, ICONZ, HD & NZ Wireless), this change may affect mail flows. Regards Thom -------- Original Message -------- Subject: Re: [mailop] Wildcarding of AHBL public DNSbl lists on Jan 1st Date: Fri, 26 Dec 2014 16:26:34 -0700 From: Brielle Bruns <bruns(a)2mbit.com> To: mailop(a)mailop.org On 12/26/14 4:00 PM, Frank Bulk (iname.com) wrote: > Thanks, that's helpful. > > I'm not sure how many IPs you have, but Cymru's service might be an option: >https://www.team-cymru.org/Services/ip-to-asn.html > > I found some other options: >http://quaxio.com/bgp/ >http://ipinfo.io/ >http://dev.maxmind.com/geoip/legacy/geolite/ (usage described here: >https://stackoverflow.com/questions/13110386/ip-to-asn-mapping-algorithm) > Thanks. I threw together a shell script that handles the conversion for me based on the geoiplookup tool and the output is going here: http://www.ahbl.org/queries/ I have to generate the lists manually for now, but it should help those looking to figure out who on their network is doing queries. -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org /http://www.ahbl.org _______________________________________________ mailop mailing list mailop(a)mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop _____________________________________________________________________________ This email has been filtered by SMX. For more info visit http://smxemail.com _____________________________________________________________________________

1 0

BCP / Guidance on IPv6 prefix size to provide to customers
by Alexander Neilson 02 Jan '15

02 Jan '15

I wondered if anyone on here had any guidance on any current BCP (or BCOP) or some general guidance on IPv6 allocations to customers (I am speaking here only for casual day to day allocations to customers) Looking through email archives and discussions that have seen around there was fairly vigorous discussions but no real resolutions. I have seen suggestions of /48, /50, /56. I am inclined to allocate /56’s to each customer (providing 256 /64’s). I don’t want to prevent customers from having the flexibility to do what they need / want to do nor stymie future use cases. If there is some good guidance on a need for /48’s then I will look at it and will use those if needed. Also, is current operating practice amongst others for all links to be /64’s even for p2p links? It seems a lot of documentation / reference texts are a few years old now and some providers have told me that this advice is no longer current but I haven’t yet seen this codified. My /32 allocation is provisionally as follows: 16 bits of /56 allocations - 65,535 customer allocations 8 bits for internal (leaves me 255 /64’s for p2p links between routers) Currently using PPPoE for IPv4 authentication for bulk customers and bespoke routed configurations for the rest. I intend to continue the PPPoE at this stage and just provide dual stack to every customer when connecting. I am still open to any input people have or feedback about what contributed to their deployments. I have looked into archives but was unable to find clear guidance that wasn’t discussed at length to be out of date / disputed so I am primarily looking for what the current best practice is so I can take advantage of the best advise for rolling out the deployment (I know we are late to this party but better late than never) Regards Alexander Alexander Neilson Neilson Productions Limited alexander(a)neilson.net.nz 021 329 681 022 456 2326

7 13

Re: [nznog] Whole of Domain Web Harvest 2015
by emma h 23 Dec '14

23 Dec '14

for those wishing to block, the apache rewrite rule is; RewriteEngine on RewriteRule ^(.*)$ http:/your.domain.co.nz [R=301,L] RewriteCond %{HTTP_USER_AGENT} ^(.*)NLNZ_IAHarvester2015(.*)$ RewriteRule ^(.*)$ http://tinyurl.com/NLNZ-IAHarvester2015 merry festivus. -- em

2 1

AUI 10BaseT transceiver
by Gareth Fletcher 23 Dec '14

23 Dec '14

Hi team Is anyone near Auckland CBD/Ponsonby and have one of these they'd be willing to part with this afternoon/next week? We seem to have trashed all ours years ago... Please reply off-list, with beer of choice of course :) Cheers! Gareth

1 0

Whole of Domain Web Harvest 2015
by Jay Gattuso 23 Dec '14

23 Dec '14

Hi NZNoggers, I write to let you know of our intent to commence the next NZ Whole of Domain web harvest on the 12th of Jan 2015. The crawl will take approximately 3 weeks to complete. We will be following the same model as previous years, with the Internet Archive acting on our behalf to undertake the crawl. We will be adhering to robots.txt in the main, however when content blocked by robots.txt is embedded in a page that’s not blocked by robots.txt we will attempt to capture that content. The metadata the crawler will be using is:- metadata.userAgentTemplate=Mozilla/5.0 (compatible; NLNZ_IAHarvester2015 +(a)OPERATOR_CONTACT_URL@) metadata.operatorContactUrl=https://natlib.govt.nz/publishers-and-authors/web-harvesting/domain-harvest The contact URL gives some information that describes why we are doing this, and what we’re doing. If you have any questions or concerns, please drop me a line – I’ll be monitoring this email address over the Xmas period. Many thanks, Jay Jay Gattuso | Digital Preservation Analyst | Preservation, Research and Consultancy National Library of New Zealand | Te Puna Mātauranga o Aotearoa PO Box 1467 Wellington 6140 New Zealand | +64 (0)4 474 3064 jay.gattuso(a)dia.govt.nz<mailto:jay.gattuso(a)natlib.govt.nz>

1 0

Fwd: Estonian IPv6 deployment report
by Brian E Carpenter 22 Dec '14

22 Dec '14

An example from far away... -------- Original Message -------- Subject: Estonian IPv6 deployment report Date: Mon, 22 Dec 2014 17:27:23 +0200 From: Tarko Tikan <tarko(a)lanparty.ee> To: IPv6 Ops list <ipv6-ops(a)lists.cluenet.de> hey, Some time ago, many people noticed rapid IPv6 deployment growth in Estonia (from 0% to 5% in 4 weeks). We at 3249/Elion/Estonian Telecom were behind this, other operators don't have any serious IPv6 deployments at the moment. We rolled out v6 to everyone (both business and residential customers) with last-gen CPE, there was no hop-in our hop-out program - aim was to do it perfectly and without customers even noticing. I'm happy to say that we achieved this goal :) To satisfy general interest, I promised small (somehow it turned out longer than I expected) technical writeup how we enabled v6 for our subscribers. If you have any other questions, feel free to ask and I do my best to answer them. You can also skip the technical content and there are some statistics below. Our access network is mix of DSL/GPON/wimax/p2p-ETH and broadband service is deployed in shared service vlans. IPv6 traffic shares vlan with IPv4. Service vlans are transported over MPLS metro network using pseudowires and terminated in geo-clustered Alcatel 7750 BNG routers. Each subscriber is allocated up to 4 mixed v4 and v6 IP hosts. For v4 we are using the usual DHCP, for IPv6 we are using DHCPv6 with IA_PD only, no IA_NA is provided. Unfortunately DHCPv6 provides no way to signal IPv6 default-route thus we have to fall back to RA for default-route. RA does not include any on-link prefixes or DNS information. RAs are L2 unicasted to CPE MAC so no other CPE in service vlan picks up those RAs. To ensure rapid switchover between BNG routers, we are signalling virtual link-local address as default-route. We are using ALU internal DHCP/DHCPv6 servers to allocate leases but we also signal IP information from radius (in such case BNG "fakes" DHCP server) for static IP customers. Provided IPv6 prefix is always /56 and we keep the old lease for 24h even if the CPE is turned off (actual lease time is 30min). Unfortunately, IPv6 LDRA is not available on most of our access platforms so we have to rely on IPv4 session information for authentication. This linking is done in the radius server during subscriber authentication (excellent radiator + quite awful SQL queries :) - if subscriber has IPv4 session (that has been authenticated using DHCP opt82), same MAC address is allowed to have IPv6 session on exactly the same virtual BNG port. IPv4 and v6 session are both tied to same subscriber and share shapers, QOS etc. We were able to enable IPv6 only on our last-gen Inteno CPEs. They run modified OpenWrt and because it's linux - everything is possible :) In CPE, /56 is divided up to /64s, first one is currently reserved but we will configure it on loopback interface and use it for CPE management. Second /64 is configured on LAN and third is configured on public wifi SSID (if you choose to enable this option). In the LAN, IPv6 config is provided by RAs, we also support RDNSS and stateless DHCPv6 for DNS. There is also ingress IPv6 firewall in the CPE and configuration is modifiable by user. To make deployment as smooth as possible, we rolled out IPv6 capable CPE software first. Then, during the BNG platform refresh, we deployed L2 ACLs that dropped all IPv6 traffic based on 0x86dd ethertype. We then deployed IPv6 config to all BNGs and could verify everything before single v6 lease was handed out to the subscribers. Then, interface by interface, we replaced L2 ACL with one that only allowed 0x86dd for certain, supported, OUIs. This is the current situation and we are investigating ways to support 3rd party CPEs - main problem is unreliable IPv6 config in CPEs. Many don't enable DHCPv6 (or enable NA but no PD) but still pick up default-route from RA and happily signal it to LAN. Some others hammer our BNGs with NA request every 0.1 seconds etc. As statistics go, there are 30000+ active IPv6 subscribers (almost 15% of our customer base, based on our public numbers), 81% of them have have at least one IPv6 enabled device in the LAN, 70% have more than one. Most IPv6 traffic is generated by Google+Youtube, Facebook and Akamai. Not bad for a country with 1.3M people. Next up: mobile network :) -- tarko

2 1

Primary access method
by Brian E Carpenter 21 Dec '14

21 Dec '14

Hi, In answer to a ticket entitled "Not getting an IPv6 prefix today", here is what the help desk told me: > Currently XXX have IPv6 services turned off due to some ongoing investigations > with this service. > > Once this is turned back on you will be able to get an IPv6 address again. and in response to my follow-up bleat > As IPv6 is not the Primary access method we offer on our connections this does > not need to be updated on the network status page. > > IPv6 is not a fully released product therefore it is still going through testing > and this is why we are currently unable to apply static IPv6 address (I didn't ask about a static address and don't want one.) This morning, I still have no IPv6 service and the XXX status page still says "OK - No Known Network Problems". Now, since I've had stable IPv6 service for a long time and it often gives me better response times than IPv4, I was a bit annoyed by this. Isn't it time that people consider IPv6 to be the primary access method, and IPv4 to be a legacy solution? Grumble. I need to fire up SixXs again, then. Brian

9 14

Akamai at APE
by Scott Pettit 19 Dec '14

19 Dec '14

Hoping someone knows/can share more info about the Akamai APE peer. It's been there a couple of months now but I can't find any announcement or info in regards to what those caches are serving. I'm seeing a small amount of largely corporate-ish content coming off it (e.g. Cisco.com content seems to come from there) but wondered whether it also provides media content like iTunes movies? Does anyone have detail on how large it is and what it's there for? -Scott

2 1

Multicast traffic replication issue
by Ben Cornish 18 Dec '14

18 Dec '14

Hi All, Curious if anyone has seen this issue previously or could offer any advice on the issue: We have a VLL/EOMPLS with Pipe from Sydney to NZ which then utilises a City Link QinQ service across town in Auckland. We've had an issue ongoing for some time and it only relates to multicast traffic traversing the path. Essentially this issue started when we couldn't establish a OSPF session over the link - yet all other traffic flows as expected. When we broke this link down to basics (laptop either end) we send one multicast packet in the Sydney end - we then receive that same packet 97 times out the Auckland end. (Over the Pipe and City link path) We see this issue when we ping 224.0.0.5 over the link and get that same exact packet 97 times on the other end. We've seen this when doing WireShark captures on the port. The captures show the exact same packet 97 times (ie same payload/sequence number). Pipe seem to be running out of ideas to track the issue. Being a EoMPLS circuit I doubt the issue is on the Pipe side but more on the City Link side. When CityLink were engaged in the issue they did what they referred to as an RFC test - as I understand it, unicast testing only and never engaged further. This issue only seems to effect link local multicast traffic - ie 224.0.0.x/24 All other traffic appears to flow normally/as expected. Obviously we are chasing pipe to test each side individually to work out who is doing the packet replication - however I am curious if anyone has had issues forming OSPF sessions over a City link service ?? Or if anyone can offer advice or seen a similar issue ? My brain boggles thinking how this is even possible or what would cause it. Ben Cornish General Manager [Description: Description: cid:image001.png(a)01CCB4C2.B40A97F0] Over the Wire Pty Ltd - An Impirical Company Level 3, 24 Little Edward St, Spring Hill QLD 4000 t +61 7 3847 9292 m +61 417 617 204 e ben.cornish(a)overthewire.com.au<mailto:ben.cornish(a)overthewire.com.au> www.overthewire.com.au<http://www.overthewire.com.au/>

3 4

Call for Presentations - DNS-OARC Spring Workshop, May 2015
by Sebastian Castro 18 Dec '14

18 Dec '14

NOTE: Previous message contained the right information, but with the subject referring to the wrong year. Apologies for the noise. The next OARC Spring Workshop will take place in Amsterdam on May 9th and 10th, the weekend before RIPE70. OARC is requesting proposals for presentations, with a preference for DDoS attack reports and mitigation techniques. Reports and field stories can cover DNS-based DDoS attacks, attacks to DNS infrastructure or side effects suffered by cache resolver operators. This workshop intends to build from previous strong OARC workshops, where operational content and research is welcome. Presentations from DNS operators are particularly welcome, as well as from DNS researchers. All DNS-related subjects are accepted, introduction to new tools, visualizations, DNSSEC and novel uses of the DNS. If you are an OARC member, and have a sensitive topic you would like to present for members-only, we will accommodate those talks too. Adopting practice from other conferences, a timeslot for lighting talks will be available for short presentations (5 to 10 minutes). Workshop Milestones * 18 December 2014, Call for Presentations posted * 8 January 2015, Open for submissions * 5 March 2015, Deadline for submission * 26 March 2015, Final Program published * 7 May 2015, Final deadline for slideset submission Details for abstract submission will be published here: https://indico.dns-oarc.net//conferenceCFA.py?confId=21 The workshop will be organized on different tracks, depending on the topics and the timing of each presentation. If you are interested in a lightning talk, let us know at the time of submission. You can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> if you have questions or concerns. Sebastian Castro, for the OARC Programme Committee OARC is also seeking sponsorship for this workshop, please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.) -- Sebastian Castro Technical Research Manager .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

1 0