[labnetwork] Static IP Addresses needed for hardware interlocks

[Ryan Taylor]

Hi Julia,

It sounds like you are perhaps using public IP addresses.  You should be 
able to set those up on a private network that is not routeable from the 
outside (something like a 10.0.0.0/16 network).  This should be 
configurable on the switch.  Then, as long as your lab management 
software (such as coral, nemo, etc.) is also on that network, you should 
be good.  This should address security concerns since anybody else on 
the university network will not be able to access those boxes.

Thanks,

Ryan

On 4/7/21 10:54 AM, Aebersold,Julia W. 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/ <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/a5f2f125/attachment.html>