We've recently upgraded from 5.1 to 6.0. We encountered a problem for our ip range restriction feature.
In 5.1, if we set READ restriction by ip range to all bitstream of certain collection, when an anonymous user is in the ip range, this user doesn't need to login to open the bitstream. But in 6.0, even though the anonymous user is indeed in the ip range, this user still needs to login to open the bitstream. This behavior is obviously different from that of DSpace 5.1. I would like to report it as a bug.