[Feature Request] IP Class has a built-in CDIR handling

[darksheer]

trafficstars

Adding this as an issue so I don't forget it. A large number of feeds I'm adding to YETI have a mix of both IPV4 addresses and IPV4 CIDR's. I guess having a built-in function to handle CIDR's is the best way to go moving forward, but happy to be told otherwise.

Description

The class IP doesn't currently handle CIDR's in-line with standard IPV4 addresses.

Steps to Reproduce

1. Establish a feed that has both IPV4 addresses and IPV4 CIDR addresses.
2. Feed parser will return:

ERROR:root:'23.129.64.102/31' is not a valid 'Ip'
ERROR:root:'31.185.104.20/31' is not a valid 'Ip'
ERROR:root:'50.7.74.170/31' is not a valid 'Ip'
ERROR:root:'50.7.74.172/31' is not a valid 'Ip'
ERROR:root:'51.15.56.122/31' is not a valid 'Ip'
ERROR:root:'51.15.75.120/31' is not a valid 'Ip'
ERROR:root:'64.137.221.170/31' is not a valid 'Ip'
ERROR:root:'65.19.167.130/31' is not a valid 'Ip'
ERROR:root:'65.19.167.132/31' is not a valid 'Ip'
ERROR:root:'65.49.20.10/31' is not a valid 'Ip'
ERROR:root:'77.247.181.162/31' is not a valid 'Ip'
ERROR:root:'77.247.181.164/31' is not a valid 'Ip'
ERROR:root:'79.137.112.4/31' is not a valid 'Ip'
ERROR:root:'81.17.17.130/31' is not a valid 'Ip'
ERROR:root:'85.248.227.164/31' is not a valid 'Ip'
ERROR:root:'87.118.122.50/31' is not a valid 'Ip'
ERROR:root:'89.34.237.214/31' is not a valid 'Ip'
ERROR:root:'89.163.225.6/31' is not a valid 'Ip'
ERROR:root:'89.238.178.122/31' is not a valid 'Ip'

[doomedraven]

solved?

[darksheer]

Haven't had a chance to address this one yet