Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Elvis Daniel Velea
Hi, On 2/8/21 10:22 PM, Hank Nussbacher wrote: On 08/02/2021 22:14, Justin Wilson (Lists) wrote: It acts like the IP block was blacklisted at some point and got on some bad lists but I don’t want ti limit myself to that theory. I have opened up a ticket with ARIN asking for any guidance.

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Hank Nussbacher
On 08/02/2021 22:14, Justin Wilson (Lists) wrote: It acts like the IP block was blacklisted at some point and got on some bad lists but I don’t want ti limit myself to that theory. I have opened up a ticket with ARIN asking for any guidance. Has anyone ran into

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Jon Lewis
On Mon, 8 Feb 2021, Justin Wilson (Lists) wrote: Folks, Have a gremlin we have been chasing around for several months now and it’s becoming a major issue as we are getting tighter on IPV4 and needing to give some provider assigned space back. In June we received a /22 from ARIN. As is my

RE: [EXTERNAL] Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Mann, Jason via NANOG
Off topic, but curious as to how you were able to procure new ip space? -Original Message- From: NANOG On Behalf Of Justin Wilson (Lists) Sent: Monday, February 8, 2021 2:02 PM To: nanog@nanog.org Subject: [EXTERNAL] Re: Problems with newish IP block assignment issues from ARIN I

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Jesse DuPont
Justin, We have had this with recent ARIN assignments, too. When we'd get reports from customers, we would reach out to the site admin contacts (either domain WHOIS or IP address WHOIS), explain the situation, and in every case, they were either blocking it because

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Job Snijders via NANOG
On Mon, Feb 08, 2021 at 04:02:14PM -0500, Justin Wilson (Lists) wrote: > I enabled 134.195.47.1 on one of our routers. Cool! I noticed the following: from many NLNOG RING nodes I can reach that IP address, but not from 195.66.134.42: deepmedia01.ring.nlnog.net:~$ mtr -z -w -r 134.195.47.1

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Justin Wilson (Lists)
I enabled 134.195.47.1 on one of our routers. Justin Wilson j...@mtin.net — https://j2sw.com - All things jsw (AS209109) https://blog.j2sw.com - Podcast and Blog > On Feb 8, 2021, at 3:46 PM, Job Snijders via NANOG wrote: > > Dear Justin, > > On Mon, Feb 08, 2021 at 03:14:47PM -0500, Justin

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Job Snijders via NANOG
Dear Justin, On Mon, Feb 08, 2021 at 03:14:47PM -0500, Justin Wilson (Lists) wrote: > It acts like the IP block was blacklisted at some point and got on > some bad lists but I don’t want ti limit myself to that theory. > I have opened up a ticket with ARIN asking for any guidance. Has > anyone

Re: Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Eric Kuhnke
One common cause of this issue is entities out there that have very old 'bogons' filters in place for the larger block, as an entire /8, /12 to /16 size of space that, many years ago, was unallocated space. Without getting the end point organizations running the httpd, firewalls or whatever to fix

Problems with newish IP block assignment issues from ARIN

2021-02-08 Thread Justin Wilson (Lists)
Folks, Have a gremlin we have been chasing around for several months now and it’s becoming a major issue as we are getting tighter on IPV4 and needing to give some provider assigned space back. In June we received a /22 from ARIN. As is my workflow I started announcing it but waited a month