Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
OBJECT BELOW CREATED:
aut-num: AS18202
as-name: NZRR-AS18202
descr: Net24
descr: CHIX peering at '218.100.24.12'
descr: see Citylink RT job #9729
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24388
accept ANY AND NOT fltr-bogons
export: to AS24388
announce AS18202
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: nikolai(a)net24.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070612
source: NZRR
---
OBJECT BELOW CREATED:
route-set: AS24388:RS-ROUTES:AS18202
descr: Route set advertised to AS24388 by Net24 - AS18202
members: 210.5.48.0/21^21-29,
210.55.30.0/23^23-29,
210.55.4.0/24^24-29,
210.55.7.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: nikolai(a)net24.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070612
source: NZRR
Hi,
A quick announcement to let everyone know that the site at
http://www.nznog.org has been updated. It now has info on NZNOG, with
links to conference sites and the NOC list.
There is a NOC list as part of the site - please check your entries and
if they are incorrect or incomplete please *follow the instructions on
the page* to get them updated / adjusted. The NOC list is a fairly
informal affair, but I have made a spur of the moment decision that
we'll (there's three of us in the NZNOG08 conference web team who will
be updating these) only update requests originating from a URL that
matches the URL in the table or is so obviously related that we're
willing to take the risk. In other words please don't ask for updates
from some disposable email address as we will most likely ignore them.
Most things on the historical conference sites work, but some things are
broken. We're still working on getting them sorted out, but thought it
better to get the NZNOG and the 2008.nznog.org sites out.
Comments and feedback of a useful and constructive nature would be
appreciated.
Cheers,
Gerard
NZNOG08 Public Relations Team
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS17412
descr: advertised to AS9439 by Woosh Wireless Limited - AS17412
members: 203.211.64.0/18^18-29,
202.74.192.0/19^19-29,
202.89.128.0/19^19-29,
202.21.16.0/20^20-29,
202.37.90.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: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17412
descr: advertised to AS9439 by Woosh Wireless Limited - AS17412
members: 203.211.64.0/18^18-29,
202.74.192.0/19^19-29,
202.89.128.0/19^19-29,
116.93.128.0/20^20-29,
202.21.16.0/20^20-29,
202.37.90.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: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070611
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS17412
descr: advertised to AS9560 by Woosh Wireless Limited - AS17412
members: 203.211.64.0/18^18-29,
202.74.192.0/19^19-29,
202.89.128.0/19^19-29,
202.21.16.0/20^20-29,
202.37.90.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: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17412
descr: advertised to AS9560 by Woosh Wireless Limited - AS17412
members: 203.211.64.0/18^18-29,
202.74.192.0/19^19-29,
202.89.128.0/19^19-29,
116.93.128.0/20^20-29,
202.21.16.0/20^20-29,
202.37.90.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: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070611
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS23655
descr: advertised to AS9439 by Snap Internet Limited - AS23655
members: 132.181.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
203.86.192.0/20^20-29,
210.5.48.0/21^21-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.218.0/23^23-29,
202.36.220.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.156.225.0/24^24-29,
202.36.170.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
203.96.112.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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: mark.petrie(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20061218
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS23655
descr: advertised to AS9439 by Snap Internet Limited - AS23655
members: 132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.218.0/23^23-29,
202.36.220.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.156.225.0/24^24-29,
202.36.170.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
203.96.112.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070608
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
aut-num: AS23655
as-name: NZRR-AS23655
descr: Snap Internet
descr: WIX peering at '202.7.1.240'
descr: see Citylink RT job #2857
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS9439
accept ANY AND NOT fltr-bogons
export: to AS9439
announce AS23655
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050721
source: NZRR
REPLACED BY:
aut-num: AS23655
as-name: NZRR-AS23655
descr: Snap Internet Limited
descr: CHIX peering at '218.100.24.10'
descr: see Citylink RT job #9020
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24388
accept ANY
export: to AS24388
announce AS23655
notify: rpsl-admin(a)nzix.net
notify: noc(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070606
source: NZRR
Stuff all.
WIX + a 1 route from an upstream is using a total of ~7% of 64Mb on a
Soekris here = ~4.5Mb (zebra and bgpd)
A full route table an a different router is only using about 25Mb.
Gerard
On 6/06/2007 9:45 a.m., Michael Fincham wrote:
> Hey All,
>
> Does anyone have some rough figures for how much RAM Quagga uses to keep
> the routing tables for WIX or APE in memory?
>
>
--
Netspace Services Limited
http://www.netspace.net.nz
Phone +64 4 917 8098
Mobile +64 21 246 2266
Level One, 220 Thorndon Quay, Thorndon
PO Box 12-082, Thorndon, Wellington 6004, New Zealand
Hey All,
Does anyone have some rough figures for how much RAM Quagga uses to keep
the routing tables for WIX or APE in memory?
--
-Michael Fincham
Unleash Technology Solutions
During a discussion on the NANOG list this week, I came up with an
idea that would allow content providers to test their IPv6-ability
ie. what would happen if they turned on AAAA records for their
websites, which is currently a big reason that content providers
aren't "6-ing up".
The general idea is to do GETs to several different URLs on different
hostnames, and have the different hostnames have IPv4-only, IPv6-only
and IPv4+IPv6, and then report the stats.
After some playing+testing, I've come up with some code, and it's
available here:
http://www.braintrust.co.nz/ipv6wwwtest/
I'm not really a JavaScript hacker so it probably isn't terribly
amazing quality, but it seems to work OK for me - I've been running
it on several of my websites with a large range of user clue+access+OS
+browser+ISP as visitors and I've had no complaints. The code is
running on the page above, too.
Also, the default timeout in the tarball is too high, 10000-20000 is
probably adequate.
Please let me know if you use it, or if you do something similar or
use it for inspiration or whatever.
In addition, I'm sure we'd all love to see any statistics you can
share when using this.
Enjoy!
--
Nathan Ward
