A VPN could be a stopgap while you figure something else out, but yes I agree they are a pain for patrons. Plus from a security standpoint I wouldn't want patrons VPNing into my network, too many holes.
Sent from my iPhone
> On Jan 28, 2014, at 9:26 PM, "Andreas Orphanides" <[log in to unmask]> wrote:
> That's simple for the techs, but VPNs can be a royal pain in the keester if
> you're an end-user, for a variety of reasons. It should be incumbent on us
> as information specialists to unburden the user to the extent possible.
> On Tue, Jan 28, 2014 at 9:23 PM, Aaron Addison <[log in to unmask]>wrote:
>> Some use Squid, its not hard to set up. But most vendors publish rules
>> with ezproxy in mind.
>> The other fairly simple solution is to run a VPN for access, and require
>> people to use that.
>> On Tuesday, January 28, 2014, stuart yeates <[log in to unmask]>
>>> We've just received notification of forth-coming changes to EZProxy,
>>> will require us to pay an arm and a leg for future versions to install
>>> locally and/or host with OCLC AU with a ~ 10,000km round trip.
>>> What are the alternatives?
>>> Stuart Yeates
>>> Library Technology Services http://www.victoria.ac.nz/library/