 |
 |
We do have a comment in on the helpdesk, so hopefully they'll get to that. On Fri, May 31, 2013 at 11:09 AM, Troy Murray <[log in to unmask]> wrote: > Gary, > > Valid point, specifically about missing the new IP ranges that are being > used after the upgrade. > > Since I'm not positive those in charge of the VPN are on this list and > you're the front-runner on this subject would you mind finding out from the > help desk if additional ranges were added and sharing that with us? At > least that'd save the help desk from multiple phone calls for the same > question. > > Troy Murray > Information Technologist II > Michigan State University, Department of Medicine > 1355 Bogue St, Life Science B-136D > East Lansing, MI 48824 > (e) [log in to unmask] (p) 517-432-2760 (f) 517-355-7254 > > On May 31, 2013, at 10:33 AM, Gary Schrock <[log in to unmask]> wrote: > > Ok folks, for those of you that might use a firewall to help restrict > things to ip addresses that the MSU vpn assigns, one thing that IT > Services didn't tell us is that they've added at least the 35.12.76.X > range of ip's to the service when they did this update. No idea if > they've added any others, since their documentation still lists 72 to > 75 as the range that the ip's are assigned from. > > I've got to be honest, personally I think it's bad enough that the > intended notice period was only 1 week before this change (except for > the slipup where they accidentally sent out an email that wasn't > supposed to go out), but to not include that there were changes in the > ip address range as part of that notice is very disappointing. Isn't > the whole point of the advance notice to make sure we're ready to be > able to handle the changes? > > Gary