Re: [44net] 44.170.120.59

Rob, That is why I was saying that every subnet should be registered in the portal. Including end-user subnets. This is also why I do not want to use a separate ipam for the Belgian network as my idea is that every subnet should be available in the portal and for every ham to see who own that subnet. Or every region that has it's own ipam should run a whois server which is then referred to by the portal. (like every registry does) But that is a job for another day and that can be thought out in the future. 73 Ruben ON3RVH -----Original Message----- From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org> On Behalf Of Rob PE1CHL via 44Net Sent: Saturday, January 16, 2021 14:32 To: G1FEF via 44Net <44net(a)mailman.ampr.org> Cc: Rob PE1CHL <44net(a)pe1chl.nl> Subject: Re: [44net] 44.170.120.59 I already knew it is "Croatia". I see no way to identify the invidual behind 44.170.120.59: whois -h whois.ampr.org 44.170.120.59 Network:    44.170.0.0/16 Type:       country BGP:        NO Callsign:   AMPRNET Locator:    IO92ab Description:HR Allocated:  2019-07-21 14:32:05 Updated:    2019-07-21 14:32:05 At least they can maintain a reverse DNS. "it can be handled by abuse(a)ampr.org" but that should be reserved for abuse only I think, I initially wasn't handling this as abuse but still I think we should be able to identify traffic to the originating callsign. Rob On 1/16/21 1:25 PM, G1FEF via 44Net wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net