[labnetwork] Static IP Addresses needed for hardware interlocks

Wed Apr 7 20:48:44 EDT 2021

Thanks Michael.  I will let our engineer answer your question for I am not sure and she has set up our FOM system.

Cheers!

Julia Aebersold, Ph.D.

Manager, Micro/Nano Technology Center

University of Louisville

2210 South Brook Street

Shumaker Research Building, Room 233

Louisville, KY  40292

(502) 852-1572

http://louisville.edu/micronano/<http://louisville.edu/micronano>

________________________________
From: Michael Rooks <michael.rooks at yale.edu>
Sent: Wednesday, April 7, 2021 4:40 PM
To: Aebersold,Julia W. <julia.aebersold at louisville.edu>
Cc: labnetwork at mtl.mit.edu <labnetwork at mtl.mit.edu>
Subject: Re: [labnetwork] Static IP Addresses needed for hardware interlocks

CAUTION: This email originated from outside of our organization. Do not click links, open attachments, or respond unless you recognize the sender's email address and know the contents are safe.

We have the same problem of running out of IPv4 addresses. We started using a router to do port forwarding from the control system (Badger, similar to Coral) to the ethernet relays. The control system, running on AWS, needs just one ip address, blessed and approved by our IT department. The router gets messages on different ports, then maps ports onto the internal IP addresses of the relays. It works a lot like your home wireless router, but with the local addresses set to fixed values. The router connects by wifi to some relays, and by hardwire to others.

This requires the controller to allow address:port addressing, which is easy in Badger. Does FOM let you do the same thing?

--------------------------------
Michael Rooks
nano.yale.edu<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnano.yale.edu%2F&data=04%7C01%7Cjulia.aebersold%40louisville.edu%7C6ea1a773304c4789bfc308d8fa055fdd%7Cdd246e4a54344e158ae391ad9797b209%7C0%7C0%7C637534248281163827%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BGvS8aWfX7S%2F4NC%2BtR90BNoN2%2FoxSST17bwQ82KzZu4%3D&reserved=0>

On Wed, Apr 7, 2021 at 3:50 PM Aebersold,Julia W. <julia.aebersold at louisville.edu<mailto:julia.aebersold at louisville.edu>> wrote:

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/

_______________________________________________
labnetwork mailing list
labnetwork at mtl.mit.edu<mailto:labnetwork at mtl.mit.edu>
https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmtl.mit.edu%2Fmailman%2Flistinfo.cgi%2Flabnetwork&data=04%7C01%7Cjulia.aebersold%40louisville.edu%7C6ea1a773304c4789bfc308d8fa055fdd%7Cdd246e4a54344e158ae391ad9797b209%7C0%7C0%7C637534248281163827%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TDuZEx%2B1sgLgqjDXKsKX8Ik2LManAEIifNkj04KwQ%2Fs%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20210408/cb42d89a/attachment.html>