[labnetwork] Static IP Addresses needed for hardware interlocks

[Michael Rooks]

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


On Wed, Apr 7, 2021 at 3:50 PM Aebersold,Julia W. <
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
> https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mtl.mit.edu/pipermail/labnetwork/attachments/20210407/aaee8172/attachment.html>