Hi All, We are having a little trouble with a new IPv4 address range recently received from APNIC. The range is 223.165.16.0/22 (although according to APNIC it affects the entire /8). Please see the attached email. It seems that there are some routers which have blocks on this range, which need to be lifted. Some of the sites we cannot connect to include: airnz.co.nz and dse.co.nz. We suspect some email is also not getting through. Can anyone suggest how best to get these routing blocks lifted? My shiny new IP address range is starting to feel distinctly second-hand. Any help you can provide would be warmly welcomed. Thanks Richard -- Richard Bourne Technical Director, Vistagate International Ltd Phone: +64 4 931 9330, Fax: +64 4 931 9322 DDI: +64 4 931 9324 Cellphone: 021 818 999 mailto:richard.bourne(a)vistagate.com http://www.vistagate.com/ Making your net worth more -- From: APNIC-NO-REPLY [mailto:apnic-no-reply(a)apnic.net] Sent: Friday, 15 October 2010 6:17 p.m. To: Richard Bourne Subject: Filtering Previously Unallocated Addresses _______________________________________________________________________ Filtering Previously Unallocated Addresses _______________________________________________________________________ APNIC recognizes that as the IANA pool of unallocated IPv4 addresses nears exhaustion, there may be increasing community concern about the quality of the new address blocks made available for distribution. It is important that you ensure your router Access Control Lists (ACLs) are updated so addresses are not mistakenly filtered through your routers. It may also be time to consider whether you should stop any form of BOGON filtering. This is especially important for newly allocated address blocks: * 1.0.0.0/8 * 14.0.0.0/8 * 27.0.0.0/8 * 49.0.0.0/8 * 101.0.0.0/8 * 223.0.0.0/8 Keep informed about IANA allocations at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml For those with recently allocated address space here are several tips to check whether your IP Addresses are filtered: * Your own firewall might be blocking the new IP addresses by default, if you set up your servers to block bogon IP ranges. To avoid blocking potential new customers, consider whether you should stop any form of BOGON filtering. * Run a traceroute to see if the new IP is consistently blocked along the same network path. It is advisable also, to test forward and reverse paths. Use of technology like the Routing Information Service (RIS) is highly recommended to assist in identifying routing conditions for prefixes under test. http://www.ripe.net/projects/ris/index.html * Do a search on your IP address and contact those organizations that appear to be blocking you. You may be blocked due to activity of one of your customers. http://whatismyipaddress.com/blacklist-check * Use a looking glass service as part of the diagnostic tool, set to detect network filters. http://www.ris.ripe.net/cgi-bin/lg/index.cgi Ongoing testing --------------- As part of our service commitment to our Members and the wider community, APNIC is working hard to evaluate the usability of address space allocated to APNIC before it is distributed. For further information on Resource Quality Assurance and the testing results, visit: http://www.apnic.net/rqa For further assistance, contact: helpdesk(a)apnic.net ____________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61 7 3858 3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net _______________________________________________________________________ * Sent by email to save paper. Print only if necessary.
On 2010-10-17, at 21:48, Richard Bourne wrote:
We are having a little trouble with a new IPv4 address range recently received from APNIC. The range is 223.165.16.0/22 (although according to APNIC it affects the entire /8). Please see the attached email. It seems that there are some routers which have blocks on this range, which need to be lifted. Some of the sites we cannot connect to include: airnz.co.nz and dse.co.nz. We suspect some email is also not getting through.
Can anyone suggest how best to get these routing blocks lifted? My shiny new IP address range is starting to feel distinctly second-hand.
223 is the last /8 in what was once called class C, immediately below the threshold for class D (multicast). Through the years people have made assumptions about reasonable use of such dark corners of the addressing plan, and you can expect a certain amount of pain. You are not the first person to experience this. Your shiny white allocation is in fact rather stained and grey, but since that's all there is left you might find you have to find ways to live with it. Welcome to the end of days. You might try - making noise on mailing lists (you never know, it might work) - performing active measurements to many remote networks and trying to identify the autonomous systems whose internal policies seem at odds with your expectations, then contact them and see if they can help - start harvesting examples from your logs of half-open connections, delivery failures, connection failures, etc, and attempt to contact the remote organisations involved There is no magic bullet. Joe
Richard, Can you provide a pingable host in 223.165.16.0/22 ? Then people could explore things a bit for you. It doesn't cost much to run a ping and traceroute and mail you the results. Regards Brian Carpenter On 2010-10-19 02:37, Joe Abley wrote:
On 2010-10-17, at 21:48, Richard Bourne wrote:
We are having a little trouble with a new IPv4 address range recently received from APNIC. The range is 223.165.16.0/22 (although according to APNIC it affects the entire /8). Please see the attached email. It seems that there are some routers which have blocks on this range, which need to be lifted. Some of the sites we cannot connect to include: airnz.co.nz and dse.co.nz. We suspect some email is also not getting through.
Can anyone suggest how best to get these routing blocks lifted? My shiny new IP address range is starting to feel distinctly second-hand.
223 is the last /8 in what was once called class C, immediately below the threshold for class D (multicast). Through the years people have made assumptions about reasonable use of such dark corners of the addressing plan, and you can expect a certain amount of pain.
You are not the first person to experience this. Your shiny white allocation is in fact rather stained and grey, but since that's all there is left you might find you have to find ways to live with it. Welcome to the end of days.
You might try
- making noise on mailing lists (you never know, it might work) - performing active measurements to many remote networks and trying to identify the autonomous systems whose internal policies seem at odds with your expectations, then contact them and see if they can help - start harvesting examples from your logs of half-open connections, delivery failures, connection failures, etc, and attempt to contact the remote organisations involved
There is no magic bullet.
Joe _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
participants (3)
-
Brian E Carpenter -
Joe Abley -
Richard Bourne