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:
------------------------------------------------------------
---
NEW OBJECT CREATION:
route-set: AS9281:RS-ROUTES:AS38477
descr: advertised to AS9281 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
202.6.116.0/23^23-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)unleash.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091113
source: NZRR
------------------------------------------------------------
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:AS17705
descr: advertised to AS9439 by Inspire Net Ltd - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: ops(a)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091022
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17705
descr: advertised to AS9439 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
202.174.160.0/20^20-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091113
source: NZRR
------------------------------------------------------------
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:AS17705
descr: advertised to AS9560 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: brenden(a)staff.inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080724
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17705
descr: advertised to AS9560 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
202.174.160.0/20^20-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091113
source: NZRR
------------------------------------------------------------
FYI to NZNOGers
...Skeeve
--
Skeeve Stevens, CEO/Technical Director
eintellego Pty Ltd - The Networking Specialists
skeeve(a)eintellego.net / www.eintellego.net
Phone: 1300 753 383, Fax: (+612) 8572 9954
Cell +61 (0)414 753 383 / skype://skeeve
www.linkedin.com/in/skeeve ; facebook.com/eintellego
--
NOC, NOC, who's there?
-----Original Message-----
From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens
Sent: Wednesday, 11 November 2009 5:44 PM
To: ausnog(a)ausnog.net
Subject: Re: [AusNOG] Soul/TPG buying Pipe ...
All,
I'm quite disappointed in this move.... yes, it is just my little opinion, but it is mine to give.
TPG's takeover of Soul, the way they run their network operations - from experience and the feedback of quite a few Soul staff, does not inspire me with any confidence with what will happen to Pipe. TPG basically gutted Soul in several areas and I can't see how, unless they've changed the way they do things, that this will be any good at all for Pipe.
Pipe, driven by Bevan and Steve have been amazing for this industry, building it, supporting it and making what it is today... I have never ever experienced TPG caring at all for the industry as a whole... sponsoring anything industry related or supporting it in other ways... if they have, I would like to be corrected.
Now Wholesale. I've been a big advocate of Pipe as a wholesale provider over anyone else - simply because of how much they've given the industry and my love for the guys.... but as a wholesale provider they never competed with ISP's in any real way. TPG is a retail based ISP primary.. Soul does other things, but again they shut down their wholesale business of DSL and other things very quickly after the takeover by TPG. What will happen to Pipe? Wholesale shutdown - prices up.. peering killed off?
One question I would really like to ask is 'Why Bevan why?'... I realise you guys together only had 27% - but did you have no choice? I am sure I am not the only one asking 'How could you do this to us?' Is it just about the money?
In the end.. whatever happens, we will adapt.... you never really do know how things will turn out. This might be a good thing... not that I can see how at the moment. If they leave Pipe alone and let it do what it does best... great... if they gut it and integrate... sad panda for all.
I see things like Pipe drinks disappearing, AUSNOG sponsorship disappearing, and amazing industry innovation - like PPC1 - things like that not happening anymore.
I remember Bevans' speech at the Pipe Xmas part in 2008... about being here for the small guy... What happened.
...Skeeve
--
Skeeve Stevens, CEO/Technical Director
eintellego Pty Ltd - The Networking Specialists
skeeve(a)eintellego.net / www.eintellego.net
Phone: 1300 753 383, Fax: (+612) 8572 9954
Cell +61 (0)414 753 383 / skype://skeeve
www.linkedin.com/in/skeeve ; facebook.com/eintellego
--
NOC, NOC, who's there?
> -----Original Message-----
> From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-
> bounces(a)lists.ausnog.net] On Behalf Of Matthew Moyle-Croft
> Sent: Wednesday, 11 November 2009 4:58 PM
> To: ausnog(a)ausnog.net
> Subject: [AusNOG] Soul/TPG buying Pipe ...
>
> http://www.asx.com.au/asx/statistics/displayAnnouncement.do?display=pdf&ids…
>
> I'd cut and paste, but it's been disabled.
>
> Have a read. How does the world change?
>
> MMC
> --
> Matthew Moyle-Croft
> Peering Manager and Team Lead - Commercial and DSLAMs
> Internode /Agile
>
> _______________________________________________
> AusNOG mailing list
> AusNOG(a)lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
_______________________________________________
AusNOG mailing list
AusNOG(a)lists.ausnog.nethttp://lists.ausnog.net/mailman/listinfo/ausnog
Thank you to everyone who emailed with suggestions for a switch for
my LAN upgrade to GigE. The issue is a little more complicated.
We have 3 main switches on the "base" network. They are all 24 ports,
not small 8 ports. The van and both encoder roadcases all have 24
port switches in them and we use the 24 ports. Plus there are
switches for "client use" (48 ports each). So I'm probably looking
for 6 to 8, 24 port switches with SFPs - and VLANs would be nice.
We use multiple internet links (sometimes as many as 4+) We build
the different networks via VLANS or sometimes separate physical networks.
And of course we use a VoIP pabx with lines in AKL, WLG and CHC. The
van has its own lines (2), and we have a portable VoIP pabx for event use.
When we need "more power", we connect the van to the office network,
both for uplink lines and encoders and for clearing the van-resident
disks. The neighbours are sort of used to seeing the van all lit up
at night. Satellite dishes sprout and disappear as
required. http://www.r2.co.nz/20080404/photos/
I hope this explains why things are a little more complicated. We
drink beer to stay sane (and on topic)
The New Zealand Network Operators' Group
The NZNOG mailing list exists to facilitate discussion among operators
of networks in New Zealand on matters relevant to network operators as
described in the list's Acceptable Use Policy. That policy appears later
in this posting.
The NZNOG Trust is registered as a charitable entity under the Charities
Act. The trust exists to provide the legal framework needed to do jobs
like operating the bank account which holds the money which allows our
annual conferences to happen.
Other than the trustees, the NZNOG does not have a formal membership.
Conference
NZNOG holds New Zealand's only annual technical networking conference.
The next conference is scheduled to be held on 27-29 January 2010 in
Hamilton, hosted by The University of Waikato's WAND research group.
Other Meetings
See http://thursdaynightcurry.com/ if you live in or near Auckland or
Wellington.
Operators' Contact List
See http://www.nznog.org/?page_id=6 for operational contact details for
most New Zealand ISP's. These are intended for use by other network
operators, not by most customers.
Internet Exchanges
See http://www.nzix.net/ for details of exchanges in operation.
About This Mailing List
This list has around 1000 addresses subscribed. You may only post to the
list from a subscribed address. A number of people subscribe
addresses which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of APN Online, Citylink, and
The University of Waikato. None of these organisations, nor any
administrator, is responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ .
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
with site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
--
Donald Neal | "I'm useless at chemistry. The only
| thing I know is not to lick the spoon."
High Performance Computing | - Sandi Toksvig
The University of Waikato |
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:AS17492
descr: advertised to AS9560 by Vector Communications LTD. (Tangent LTD) - AS17492
members: 202.126.192.0/20^20-29,
123.108.144.0/21^21-29,
202.0.151.0/24^24-29,
202.62.245.0/24^24-29,
203.30.174.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: matt.oram(a)vector.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090804
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17492
descr: advertised to AS9560 by Vector Communications - AS17492
members: 202.126.192.0/20^20-29,
123.108.144.0/21^21-29,
202.0.151.0/24^24-29,
202.62.245.0/24^24-29,
203.30.174.0/24^24-29,
203.99.68.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: tony.wicks(a)vector.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091106
source: NZRR
------------------------------------------------------------
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:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.46.160.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.126.80.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
202.36.218.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.221.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.49.144.0/24^24-29,
202.49.168.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29,
123.100.117.192/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091030
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.46.160.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.126.80.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.221.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.49.106.0/24^24-29,
202.49.144.0/24^24-29,
202.49.168.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29,
123.100.117.192/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091106
source: NZRR
------------------------------------------------------------
