[labnetwork] Static IP Addresses needed for hardware interlocks

[Yakimov, Michael]

As far as I understand, you have equipment enable/disable boxes, which need to be accessible by a server, not by outside world.
I would consider getting hardware interfaces into a separate network  with addresses from private pool so nothing but main server is exposed to the internet,  and security considerations are not in play. You really need to talk to your institution IT people about that. Write down all the communications required  for those hardware  boxes, hopefully they can figure it  out for you.
After all, your local IT is there to support you, not the other way around!



From: labnetwork <labnetwork-bounces at mtl.mit.edu> On Behalf Of Aebersold,Julia W.
Sent: Wednesday, April 7, 2021 12:54
To: labnetwork at mtl.mit.edu
Subject: [labnetwork] Static IP Addresses needed for hardware interlocks

We utilize a large array of hardware interlocks within our equipment fleet that interfaces with our software for access, training requests, reservations, invoicing, etc. Each of these relay boxes requires a static IP address.  With recent security certificate requirements in our institution getting a static IP address for new systems is becoming very arduous.

Are there alternatives out there beyond the requirement of a static IP address that address current security requirements?

Cheers!

Julia Aebersold, Ph.D.
Manager, Micro/Nano Technology Center
University of Louisville
Shumaker Research Building, Room 233
2210 South Brook Street
Louisville, KY  40292
(502) 852-1572

http://louisville.edu/micronano/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20210407/84bb4353/attachment.html>