Hi Guys We have moved a customers server over to our new ip range and now we are having reports that some customers in NZ can no longer reach the hosted site. If any one has some spare time can they please ping 103.4.122.20 and if the ping fails send me a trace route. That would be very much appreciated. Thank you Andrew Paternoster [cid:image001.png(a)01CC8F48.302414B0] Andrew Paternoster Screwloose Tel: (03) 9095-7290 Email: Andrew(a)screwloose.com.aumailto:Andrew(a)screwloose.com.au Site: http://www.screwloose.com.au You can now log faults by logging in to http://support.screwloose.com.au or just by simply emailing support(a)screwloose.com.aumailto:support(a)screwloose.com.au
On 20/10/11 Thu, Oct 20, 18:49, Andrew Paternoster wrote:
Hi Guys
We have moved a customers server over to our new ip range and now we are having reports that some customers in NZ can no longer reach the hosted site.
If any one has some spare time can they please ping 103.4.122.20 and if the ping fails send me a trace route. That would be very much appreciated.
I've tried it from a couple of different locations and it works fine. What's more interesting is that a traceroute from one location goes via the US and the other goes transTasman directly with a 140 msec rtt difference. Anyone peering with Vocus in Auckland is getting a better connection. $ traceroute 103.4.122.20 traceroute to 103.4.122.20 (103.4.122.20), 64 hops max, 52 byte packets 1 ngauranga (130.195.5.1) 109.370 ms 0.281 ms 0.259 ms 2 ntp.vuw.ac.nz (130.195.196.196) 0.179 ms 0.185 ms 0.197 ms 3 41.36.69.111.dynamic.snap.net.nz (111.69.36.41) 0.756 ms 0.748 ms 0.717 ms 4 111-69-27-66.core.snap.net.nz (111.69.27.66) 13.805 ms 13.740 ms 13.800 ms 5 111-69-27-65.core.snap.net.nz (111.69.27.65) 14.179 ms 14.216 ms 14.159 ms 6 203.167.233.10 (203.167.233.10) 14.073 ms 14.066 ms 14.283 ms 7 i-0-6-4-0.tlot-core01.bx.reach.com (202.84.142.110) 143.711 ms 143.701 ms 144.336 ms 8 i-2-5.tlot03.bi.reach.com (202.84.251.242) 139.397 ms 139.431 ms 139.367 ms 9 xe-11-2-0.edge1.losangeles6.level3.net (4.68.62.9) 142.229 ms * * 10 vlan70.csw2.losangeles1.level3.net (4.69.144.126) 142.767 ms vlan80.csw3.losangeles1.level3.net (4.69.144.190) 159.116 ms vlan60.csw1.losangeles1.level3.net (4.69.144.62) 140.911 ms 11 ae-63-63.ebr3.losangeles1.level3.net (4.69.137.33) 140.831 ms ae-83-83.ebr3.losangeles1.level3.net (4.69.137.41) 159.172 ms ae-73-73.ebr3.losangeles1.level3.net (4.69.137.37) 140.703 ms 12 ae-3-3.ebr1.sanjose1.level3.net (4.69.132.9) 173.270 ms 172.304 ms 172.189 ms 13 ae-61-61.csw1.sanjose1.level3.net (4.69.153.2) 168.866 ms ae-71-71.csw2.sanjose1.level3.net (4.69.153.6) 148.581 ms ae-61-61.csw1.sanjose1.level3.net (4.69.153.2) 159.099 ms 14 ae-34-80.car4.sanjose1.level3.net (4.69.152.134) 149.209 ms ae-14-60.car4.sanjose1.level3.net (4.69.152.6) 149.063 ms ae-44-90.car4.sanjose1.level3.net (4.69.152.198) 149.264 ms 15 4.71.114.242 (4.71.114.242) 196.022 ms 201.467 ms 195.922 ms 16 bdr01.syd01.nsw.plat.net.au (14.137.192.254) 196.005 ms 206.051 ms 199.592 ms 17 202.62.144.46 (202.62.144.46) 197.040 ms 197.494 ms 197.100 ms 18 202.62.156.78 (202.62.156.78) 209.120 ms 209.604 ms 209.025 ms 19 as131316.bdr01.mel01.vic.plat.net.au (202.62.157.78) 209.199 ms 209.445 ms 209.413 ms 20 * * * 21 * * * $ traceroute 103.4.122.20 traceroute to 103.4.122.20 (103.4.122.20), 30 hops max, 60 byte packets 1 202-8-44-33.citylink.co.nz (202.8.44.33) 0.285 ms 0.192 ms 0.250 ms 2 g0-2-4028.wn014-rt1.corp.clnz.net (202.8.44.76) 0.599 ms 0.513 ms 0.439 ms 3 eth0-4055.wn014-rt2.citylink.co.nz (202.8.44.103) 0.537 ms 0.475 ms 0.529 ms 4 eth0-4055.wn016-rt6.citylink.co.nz (202.8.44.101) 0.703 ms 0.831 ms 0.652 ms 5 gi0-2-51.wlg-bcl-core1.ihug.net (203.109.146.254) 1.110 ms 1.081 ms 1.363 ms 6 gi1-0-7-130.wlg-wtc-core1.wlg.vf.net.nz (203.109.180.26) 2.421 ms 8.913 ms 8.767 ms 7 gi0-0-0-15-130.ppnzwtc01.wlg.vf.net.nz (203.109.180.25) 2.342 ms 2.336 ms 2.256 ms 8 ip-221.200.31.114.VOCUS.net.au (114.31.200.221) 37.907 ms 37.703 ms 37.716 ms 9 ten-1-3-0.cor01.syd03.nsw.VOCUS.net.au (114.31.192.86) 49.597 ms 49.552 ms 49.420 ms 10 ten-0-2-0.bdr01.syd01.nsw.VOCUS.net.au (114.31.192.57) 50.625 ms 50.198 ms 50.054 ms 11 * * * 12 as9482.brisbane.pipenetworks.com (218.100.0.79) 51.090 ms 51.043 ms 50.972 ms 13 202.62.152.1 (202.62.152.1) 55.221 ms 54.511 ms 54.344 ms 14 202.62.144.46 (202.62.144.46) 54.136 ms 53.526 ms 53.497 ms 15 202.62.156.78 (202.62.156.78) 65.505 ms 65.478 ms 65.869 ms 16 as131316.bdr01.mel01.vic.plat.net.au (202.62.157.78) 65.781 ms 65.540 ms 65.412 ms 17 * * * 18 * * *
This subject line prompts a question: Is anyone still using bogan lists given that all IPv4 addresses have been allocated to the RIRs? Discuss.
On Thu, Oct 20, 2011 at 9:22 PM, Andy Linton
This subject line prompts a question:
Is anyone still using bogan lists given that all IPv4 addresses have been allocated to the RIRs?
From the other side of the world - last month I had an issue with my ISP here in Dublin filtering 106/8 (allocated in Jan 2011). Linode's new Tokyo datacenter lives in this range.
Their excuse was that they were simply using the Cisco supplied templates (ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-Templates) and didn't know any better, after haranguing them for several days it got fixed, but I note the templates on Cisco's FTP site still haven't been updated. -- Matt Brown matt(a)mattb.net.nz Mob +353 86 608 7117 www.mattb.net.nz
Is anyone still using bogan lists given that all IPv4 addresses have been allocated to the RIRs?
From the other side of the world - last month I had an issue with my ISP here in Dublin filtering 106/8 (allocated in Jan 2011). Linode's new Tokyo datacenter lives in this range.
Their excuse was that they were simply using the Cisco supplied templates (ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-Templates) and didn't know any better, after haranguing them for several days it got fixed, but I note the templates on Cisco's FTP site still haven't been updated.
That's quite bad. It's several months out of date and has plenty of allocated addresses listed as bogons. If it's any use, draft-ietf-grow-no-more-unallocated-slash8s was approved yesterday. Once it has been processed by the RFC Editor it might help convince the stragglers to fix their filter policies. http://datatracker.ietf.org/doc/draft-ietf-grow-no-more-unallocated-slash8s/... Regards, Leo
Matt Brown said the following on 21/10/11 06:40 :
From the other side of the world - last month I had an issue with my ISP here in Dublin filtering 106/8 (allocated in Jan 2011). Linode's new Tokyo datacenter lives in this range.
Their excuse was that they were simply using the Cisco supplied templates (ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-Templates) and didn't know any better, after haranguing them for several days it got fixed, but I note the templates on Cisco's FTP site still haven't been updated.
Arrrgh! I've been trying to get rid of that list for a few years now - it was last updated when a colleague of mine (who owned it) left Cisco. It is several years out of date. Even though I'm no longer at Cisco, I'll try and get rid of this badness once and for all. philip --
On 21/10/2011 9:41 a.m., Don Stokes wrote:
On 10/21/2011 09:22 AM, Andy Linton wrote:
Is anyone still using bogan lists given that all IPv4 addresses have been allocated to the RIRs?
Dunno, how many of those IPv4 addresses are dressed in black tee-shirts and driving around West Auckland in HQ Holdens?
I've never seen an IPv4 address wearing a mullet either... Keith
I have heard rumours that they do like there Cody's and Woodstock's Gareth Davies Systems Administrator - Web Applications DD +64 9 574 0123 EXT 8465 www.fphcare.com -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Keith Davidson Sent: Friday, 21 October 2011 11:12 AM To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Bogan Lists? On 21/10/2011 9:41 a.m., Don Stokes wrote:
On 10/21/2011 09:22 AM, Andy Linton wrote:
Is anyone still using bogan lists given that all IPv4 addresses have been allocated to the RIRs?
Dunno, how many of those IPv4 addresses are dressed in black tee-shirts and driving around West Auckland in HQ Holdens?
I've never seen an IPv4 address wearing a mullet either... Keith _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ____________________________________________________________ This e-mail and any attachments may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
On Fri, Oct 21, 2011 at 09:22:17AM +1300, Andy Linton wrote:
Is anyone still using bogan lists given that all IPv4 addresses have been allocated to the RIRs?
I filter the borders with static rules based on the Team Cymru bogon reference. I used to check the changelog once a week, now it's once a month or so. All they catch now is RFC1918 leakage from our peers. Mark.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, team.
I filter the borders with static rules based on the Team Cymru bogon reference. I used to check the changelog once a week, now it's once a month or so. All they catch now is RFC1918 leakage from our peers.
We will continue to offer the now very limited bogon filters, plus the fullbogons filters through HTTP, BGP, and DNS. https://www.team-cymru.org/Services/Bogons/ Note that the Fullbogons feed is updated several times daily. Thanks, Rob. - -- Rob Thomas Team Cymru https://www.team-cymru.org/ "Say little and do much." M Avot 1:15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBTqGjqFkX3QAo5sgJAQI48wP/ZOFTwGMwr0+/XTOHqOo5epY0BMUDPZ3k bTiUuIEKVA0Idfnp7uNgFI8xm1DVNNDBZCcMsJoyrIlRSt9doQcolrQyQ7D6suZr gWnKqv1/zjzjcbJ03LG4PSgNEJi84R1/Mgi3pf+oOqvjPTPMvl3RO3b2M8UTW7Q2 GeKfHRgoarQ= =7epM -----END PGP SIGNATURE-----
participants (10)
-
Andrew Paternoster -
Andy Linton -
Don Stokes -
Gareth Davies -
Keith Davidson -
Leo Vegoda -
Mark van Walraven -
Matt Brown -
Philip Smith -
Rob Thomas