On 09/03/2009, at 1:44 PM, Jasper Bryant-Greene wrote:
>
> How is that different from normal IP routing? The other end always
> decides which way to send packets back to you, and in the event that
> your customer is multihomed, the return path might not even transit
> your AS.
I control my outbound and inbound routing. People only send packets
via routes I advertise and I can show a contractual relationship
between me and my upstream or peer, my upstream and theirs or their
peer and then to the far end etc.
With using 6to4 the downside is that whilst I may have my own gateway,
the FAR end could be using a 3rd party 6to4 gateway. This means that
the return packets traverse links for which I have no contractual
relationship.
I guess in some way I'm agreeing with Joe that everyone SHOULD run
their own, especially if they offer up content over IPv6. (I wonder
if Google do with ipv6.google.com?).
MMC
--
Matthew Moyle-Croft Internode/Agile Peering and Core Networks
Level 5, 162 Grenfell Street, Adelaide, SA 5000 Australia
Email: mmc(a)internode.com.au Web: http://www.on.net
Direct: +61-8-8228-2909 Mobile: +61-419-900-366
Reception: +61-8-8228-2999 Fax: +61-8-8235-6909
via Ausnog:
"Wholesale internet transit provider Vocus will create an internet peering
exchange to greatly cut latency between Sydney and Auckland.
The PacificIX exchange would go live "by the end of the year", Vocus (ASX:
VOC) chief executive officer James Spenceley (pictured) told iTnews today.
It would run out of the Equinix and Global Switch data centres in Sydney
and from the Auckland Sky Tower and a "second [undisclosed] node"
elsewhere in the NZ city."
http://www.itnews.com.au/News/232330,vocus-to-cut-sydney-auckland-latency.a…
--
Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/
"To stay awake all night adds a day to your life" - Stilgar | eMT.
> In fact - what checks and balances are there to stop any ISP saying
> "chorus, churn phone 01 234 5678 to DodgyISP immediately"
This is the bit that is of most concern. From Joel's comment
> Wholesale get a job that says for instance "connect house X to DSLAM
> patch Y - for job ID XXXXX". all wholesale know is that there is a job
> and what they need to do.
It would appear that there may not be any or if they are that they may
be inadequate.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Glen Eustace
GodZone Internet Services, a division of AGRE Enterprises Ltd.
P.O. Box 8020, Palmerston North, New Zealand 4446.
Ph: +64 6 357 8168, Fax +64 6 357 8165, Mob: +64 27 542 4015
http://www.godzone.net.nz
"A Ministry specialising in providing low-cost Internet Services
to NZ Christian Churches, Ministries and Organisations."
This is partly a personal request but my frustration level is
approaching the red zone ..
I received an email from Telstraclear on 19 Feb advising that the
paradise.net.nz email and dial up service was to be retired on 30th
March. The message offered to forward existing paradise email addresses
to TC mailboxes and an email address was provided to request this, which
I did.
I've had no response to the email and three follow up calls to the TC
helpdesk have resulted in a "callback" request being logged but no
response so far.
So, I'm looking at all of my paradise email addresses being retired
(supposedly as of yesterday). The latest call to the TC helpdesk
suggested I email the postmaster at paradise to try and resolve the
issue, which I will do, but I though I would try here to see if there
any real people I can talk with to try and make sure my paradise
addresses remain active.
I can't be the only paradise user left, surely.
Thanks,
Dave
Hi all
Am after some advice please.
We've recently taken possession of a shiny new IP block from APNIC -
118.67.192.0/21 so that we can give our current IP's back to our
upstream.
As part of the renumbering processes we're taking the opportunity of
building a new mail server as the old one is getting a little tired.
However we've run into a minor snag: The IP of our new mail server
mta1.waspnet.co.nz 118.67.193.2 and this being explicitly refused
connection on port 25 to many of the major providers such as Gmail,
Excite and Hotmail - (In fact the entire range is but am only concerned
with one at this stage)
Apr 1 13:25:01 mta1 postfix/smtp[8807]: connect to
gmail-smtp-in.l.google.com[72.14.213.27]: Connection refused (port 25)
Apr 1 13:25:01 mta1 postfix/smtp[8807]: connect to
alt1.gmail-smtp-in.l.google.com[74.125.67.27]: Connection refused (port
25)
Apr 1 13:25:01 mta1 postfix/smtp[8807]: connect to
alt2.gmail-smtp-in.l.google.com[74.125.47.27]: Connection refused (port
25)
Apr 1 13:25:01 mta1 postfix/smtp[8807]: connect to
alt3.gmail-smtp-in.l.google.com[74.125.113.27]: Connection refused (port
25)
Apr 1 13:25:01 mta1 postfix/smtp[8807]: connect to
alt4.gmail-smtp-in.l.google.com[209.85.229.27]: Connection refused (port
25)
Apr 1 13:25:01 mta1 postfix/smtp[8808]: connect to
mx2.hotmail.com[65.55.92.184]: Connection refused (port 25)
Apr 1 13:25:01 mta1 postfix/smtp[8808]: connect to
mx1.hotmail.com[65.54.188.110]: Connection refused (port 25)
Apr 1 13:25:01 mta1 postfix/smtp[8808]: connect to
mx2.hotmail.com[65.54.188.126]: Connection refused (port 25)
Apr 1 13:25:01 mta1 postfix/smtp[8808]: connect to
mx4.hotmail.com[65.54.188.110]: Connection refused (port 25)
Apr 1 13:25:01 mta1 postfix/smtp[8808]: connect to
mx3.hotmail.com[65.54.188.126]: Connection refused (port 25)
Other providers such as TCL are just timing out on the connection
attempt
/var/log/maillog:Mar 29 08:27:29 mta1 postfix/smtp[28902]: connect to
mx.clear.net.nz[203.97.33.212]: Connection timed out (port 25)
Telnet to port 25 produces the same results
Yahoo interestingly isn't blocking it and other a few other providers
are letting us through
The frustrating thing for me is that once I got SPF & rDNS sorted we
had full connectivity to all of these on the 17th & 18th March. Then on
the 19th we started to be blocked again.
I've filled in online forms with the big three to no avail. I've checked
SORBS, Senderbase, etc and I can see no reason why we should not get
through. Any suggestions/assistance as to what I can try next would be
greatly appreciated.
We're currently using it for sending team.waspnet.co.nz mail
Cheers
Jodi
PS - We also have an IPv6 block which I am waiting upstream
advertisement
PPS - There will be beer J
Jodi Thomson
Network & Systems Engineer
Ph +64-6-8355800
Fax +64-6-8355811
Mob +64-21-903712
E-Mail jodi(a)team.waspnet.co.nz
www.waspnet.co.nz <http://www.waspnet.co.nz/>
________________________________________________________________________
IPv4 Exhaustion Information
________________________________________________________________________
Hi NZNOG community,
We are writing to remind you that IPv4 exhaustion is an issue that
should now be a priority for your organization.
Most of you will be aware that the central pool of IPv4 addresses held
by IANA was depleted in February. APNIC is currently delegating IPv4
addresses from its remaining pool.
For more information on how APNIC currently delegates addresses, please
refer to:
http://www.apnic.net/ipv4-exhaustion/stages
APNIC IPv4 Exhaustion Timeline?
-------------------------------
Due to a large number of variables, the timeline for APNIC IPv4
exhaustion is not predictable with any assured accuracy. However, it is
the APNIC Secretariat's role to make as much information as possible
available to all stakeholders, so they may make their own assessments.
You can view the current APNIC IPv4 address pool, which is updated
daily:
http://www.apnic.net/ipv4-exhaustion/graphs
Deploy IPv6 Now
---------------
If you are an APNIC Member, you can start your IPv6 deployment process
today with the APNIC Kickstart IPv6 program.
http://www.apnic.net/kickstartipv6
APNIC actively supports IPv6 deployment in the following ways:
- APNIC services and website are accessible over IPv6
- IPv6 addresses are readily available to Members
- APNIC provides IPv6 training courses
- IPv6 liaison services
- Regional IPv6 awareness initiatives
For more information on how APNIC can assist you to deploy IPv6 visit:
http://www.apnic.net/ipv6
_______________________________________________________________________
APNIC Secretariat secretariat(a)apnic.net
Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100
PO Box 3646 South Brisbane, QLD 4101 Australia Fax: +61 7 3858 3199
6 Cordelia Street, South Brisbane, QLD http://www.apnic.net
________________________________________________________________________
* Sent by email to save paper. Print only if necessary.
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:AS17746
descr: advertised to AS9560 by Orcon - AS17746
members: 121.98.0.0/15^15-29,
60.234.0.0/16^16-29,
143.96.0.0/16^16-29,
156.62.0.0/16^16-29,
14.1.32.0/19^19-29,
49.50.192.0/19^19-29,
180.189.192.0/19^19-29,
202.150.96.0/19^19-29,
49.50.240.0/20^20-29,
202.126.192.0/20^20-29,
202.191.32.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
49.50.224.0/21^21-29,
116.199.208.0/21^21-29,
120.136.0.0/21^21-29,
120.138.16.0/21^21-29,
202.36.16.0/21^21-29,
202.49.64.0/21^21-29,
210.54.56.0/21^21-29,
110.34.48.0/22^22-29,
113.21.224.0/22^22-29,
113.197.96.0/22^22-29,
202.36.24.0/22^22-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
202.36.230.0/23^23-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
192.88.190.0/24^24-29,
192.203.216.0/24^24-29,
202.0.151.0/24^24-29,
202.12.104.0/24^24-29,
202.14.217.0/24^24-29,
202.27.8.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29,
202.36.174.0/24^24-29,
202.36.198.0/24^24-29,
202.37.19.0/24^24-29,
202.37.78.0/24^24-29,
202.37.173.0/24^24-29,
202.37.179.0/24^24-29,
202.37.194.0/24^24-29,
202.46.189.0/24^24-29,
202.49.59.0/24^24-29,
202.49.140.0/24^24-29,
202.49.216.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.164.0/24^24-29,
202.50.176.0/24^24-29,
202.50.246.0/24^24-29,
202.62.245.0/24^24-29,
202.95.250.0/24^24-29,
202.129.253.0/24^24-29,
203.30.174.0/24^24-29,
203.208.21.0/24^24-29,
210.54.12.0/24^24-29,
210.55.8.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: benny.treefoot(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20101112
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17746
descr: advertised to AS9560 by Orcon - AS17746
members: 121.98.0.0/15^15-29,
60.234.0.0/16^16-29,
143.96.0.0/16^16-29,
156.62.0.0/16^16-29,
14.1.32.0/19^19-29,
49.50.192.0/19^19-29,
180.189.192.0/19^19-29,
202.150.96.0/19^19-29,
49.50.240.0/20^20-29,
202.126.192.0/20^20-29,
202.191.32.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
49.50.224.0/21^21-29,
116.199.208.0/21^21-29,
120.136.0.0/21^21-29,
120.138.16.0/21^21-29,
202.36.16.0/21^21-29,
202.49.64.0/21^21-29,
210.54.56.0/21^21-29,
110.34.48.0/22^22-29,
113.21.224.0/22^22-29,
113.197.96.0/22^22-29,
202.36.24.0/22^22-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
202.36.230.0/23^23-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
114.23.64.0/24^24-29,
192.88.190.0/24^24-29,
192.203.216.0/24^24-29,
202.0.151.0/24^24-29,
202.12.104.0/24^24-29,
202.14.217.0/24^24-29,
202.27.8.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29,
202.36.174.0/24^24-29,
202.36.198.0/24^24-29,
202.37.19.0/24^24-29,
202.37.78.0/24^24-29,
202.37.173.0/24^24-29,
202.37.179.0/24^24-29,
202.37.194.0/24^24-29,
202.46.189.0/24^24-29,
202.49.59.0/24^24-29,
202.49.140.0/24^24-29,
202.49.216.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.164.0/24^24-29,
202.50.176.0/24^24-29,
202.50.246.0/24^24-29,
202.62.245.0/24^24-29,
202.95.250.0/24^24-29,
202.129.253.0/24^24-29,
203.30.174.0/24^24-29,
203.208.21.0/24^24-29,
210.54.12.0/24^24-29,
210.55.8.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: benny.treefoot(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20110331
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: 121.79.192.0/18^18-29,
203.114.128.0/18^18-29,
202.174.160.0/20^20-29,
202.36.96.0/21^21-29,
140.200.248.0/22^22-29,
202.36.214.0/23^23-29,
192.138.251.0/24^24-29,
192.245.185.0/24^24-29,
202.74.38.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 20110309
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17705
descr: advertised to AS9439 by Inspire Net Ltd - AS17705
members: 121.79.192.0/18^18-29,
203.114.128.0/18^18-29,
202.174.160.0/20^20-29,
202.36.96.0/21^21-29,
140.200.248.0/22^22-29,
202.36.214.0/23^23-29,
192.138.251.0/24^24-29,
192.245.185.0/24^24-29,
202.36.110.0/24^24-29,
202.74.38.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 20110331
source: NZRR
------------------------------------------------------------
