Re: Ideas solicited: Using Perl to sort through Toxic CIDR blocks

Well, the first order of business would be to provide samples of the input data and desired output. :)

It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

Comment on Re: Ideas solicited: Using Perl to sort through Toxic CIDR blocks

Replies are listed 'Best First'.
Re^2: Ideas solicited: Using Perl to sort through Toxic CIDR blocks by blue_cowdawg (Monsignor) on May 29, 2014 at 20:29 UTC
Thought that wouldn't be necessary since I did say CIDR blocks, but here: `108.177.128.0/17 108.62.0.0/16 109.200.1.0/24 109.200.2.0/23 109.200.4.0/22 109.200.8.0/21 109.200.16.0/20 109.200.6.200/29 109.200.6.208/28 109.200.6.224/27 109.230.192.0/19 109.230.224.0/20 109.230.240.0/21 109.230.248.0/22 109.230.252.0/23 109.230.254.0/24 109.230.255.0/25 109.230.255.128/26 109.230.255.192/27 109.230.255.224/28 109.230.255.240/29 109.230.255.248/30 109.230.255.252/31 109.230.255.254/32` [download] Peter L. Berghold -- Unix Professional Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg	[reply] [d/l]
Re^3: Ideas solicited: Using Perl to sort through Toxic CIDR blocks by boftx (Deacon) on May 29, 2014 at 23:04 UTC
I was more interested in the output format you need. At this point, why not share with us the idea(s) you have tried that you think could be improved on. Apparently the only thing you are looking for is an efficient way of looping through the data, right? It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.	[reply]