It's actually quite simple to change the type to ip4r.
The only issue is that according to ipranges195.113.144.130/28 is a valid record whereas according to ip4r it is not. So searching for such addresses results in internal server error.
As @ph noticed, timeline and events handle the aforementioned type of addresses, the phrase "Invalid address value xxx in search form." is written on the screen. I checked the code and the validation is not actually performed before the form is submitted, although it might seem like it is. In dispatch_request method, there is a try-catch block which handles the exception from the database. I don't like this approach and I would much rather check the value before posting request. I will probably go with high and low functions from ipranges and convert the value to range.
As @ph noticed, timeline and events handle the aforementioned type of addresses, the phrase "Invalid address value xxx in search form." is written on the screen. I checked the code and the validation is not actually performed before the form is submitted, although it might seem like it is. In dispatch_request method, there is a try-catch block which handles the exception from the database. I don't like this approach and I would much rather check the value before posting request. I will probably go with high and low functions from ipranges and convert the value to range.