<div dir="ltr"><div>Hi Julia,</div><div><br></div><div>I want to piggyback on what some of the others have said.<br></div><div><br></div><div> UCSD uses FOM and we have blocked many of our relay controls from the outside internet by placing them on special subnets/VLANs. Inside each subnet/VLAN, we can set up rules about what the devices can see outside of the subnet/VLAN. I think this is very similar to what Michael and Ryan said above. It should be possible within FOM, but getting IT to work with you is another story. <br></div><div><br></div><div>Please let me know if I can be of further assistance.</div><div><br></div><div>John<br></div><div><br></div><div><br></div><div><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">-----------------------------------<br><pre>John Tamelier
Microfabrication Process Engineer
University of California, San Diego
Atkinson Hall, 5th Floor Front Desk, M/C 0436
9500 Gilman Drive
La Jolla, California 92093-0436
Phone: (858) 246-2735
Fax: (858) 534-9092
E-mail: <a rel="nofollow" shape="rect" href="mailto:jtamelier@ucsd.edu" target="_blank">jtamelier@ucsd.edu</a>
<a href="http://nano3.calit2.net" target="_blank">http://nano3.calit2.net</a><br>-----------------------------------</pre></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 8, 2021 at 4:50 AM Aebersold,Julia W. <<a href="mailto:julia.aebersold@louisville.edu" target="_blank">julia.aebersold@louisville.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Thanks Michael. I will let our engineer answer your question for I am not sure and she has set up our FOM system.</div>
<div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div id="gmail-m_-6254085873445891042gmail-m_-4115430496019504837Signature">
<div>
<div id="gmail-m_-6254085873445891042gmail-m_-4115430496019504837divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif">
<div style="font-family:Tahoma;font-size:13px">
<div style="font-family:Tahoma;font-size:13px">
<div style="font-family:Tahoma;font-size:13px">
<div style="font-family:Tahoma;font-size:13px">
<div>
<div>
<div>
<p style="margin-top:0px;margin-bottom:0px">Cheers!</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">Julia Aebersold, Ph.D.</p>
<p style="margin-top:0px;margin-bottom:0px">Manager, Micro/Nano Technology Center</p>
<p style="margin-top:0px;margin-bottom:0px">University of Louisville</p>
<p style="margin-top:0px;margin-bottom:0px">2210 South Brook Street</p>
<p style="margin-top:0px;margin-bottom:0px">Shumaker Research Building, Room 233</p>
<p style="margin-top:0px;margin-bottom:0px">Louisville, KY 40292</p>
<p style="margin-top:0px;margin-bottom:0px">(502) 852-1572</p>
<p style="margin-top:0px;margin-bottom:0px"><a href="https://urldefense.com/v3/__http://louisville.edu/micronano__;!!Mih3wA!SQsxbaAkcj0DJgUdXOXwvjfrPpRj6T8X9DIo1XwXjvXU-n1Xr58tb-vRon9RrY4s$" target="_blank">http://louisville.edu/micronano/</a></p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div id="gmail-m_-6254085873445891042gmail-m_-4115430496019504837appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_-6254085873445891042gmail-m_-4115430496019504837divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Michael Rooks <<a href="mailto:michael.rooks@yale.edu" target="_blank">michael.rooks@yale.edu</a>><br>
<b>Sent:</b> Wednesday, April 7, 2021 4:40 PM<br>
<b>To:</b> Aebersold,Julia W. <<a href="mailto:julia.aebersold@louisville.edu" target="_blank">julia.aebersold@louisville.edu</a>><br>
<b>Cc:</b> <a href="mailto:labnetwork@mtl.mit.edu" target="_blank">labnetwork@mtl.mit.edu</a> <<a href="mailto:labnetwork@mtl.mit.edu" target="_blank">labnetwork@mtl.mit.edu</a>><br>
<b>Subject:</b> Re: [labnetwork] Static IP Addresses needed for hardware interlocks</font>
<div> </div>
</div>
<div>
<p style="line-height:12pt;background:rgb(255,77,77) none repeat scroll 0% 0%"><b><span style="font-size:10pt;color:black">CAUTION:</span></b><span style="font-size:10pt;color:black"> 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.</span></p>
<div></div>
<div>
<div dir="ltr">
<div dir="ltr">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. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">This requires the controller to allow address:port addressing, which is easy in Badger. Does FOM let you do the same thing?</div>
<div dir="ltr"><br clear="all">
<div>
<div dir="ltr">
<div dir="ltr">--------------------------------
<div><font size="1">Michael Rooks</font></div>
<div><font size="1"><a href="https://urldefense.com/v3/__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__;JSUlJSUlJSUlJSUlJSUlJSUlJSU!!Mih3wA!SQsxbaAkcj0DJgUdXOXwvjfrPpRj6T8X9DIo1XwXjvXU-n1Xr58tb-vRokkga8F7$" target="_blank">nano.yale.edu</a></font> </div>
</div>
</div>
</div>
<br>
</div>
<br>
<div>
<div dir="ltr">On Wed, Apr 7, 2021 at 3:50 PM Aebersold,Julia W. <<a href="mailto:julia.aebersold@louisville.edu" target="_blank">julia.aebersold@louisville.edu</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p>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.
<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Are there alternatives out there beyond the requirement of a static IP address that address current security requirements?<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Cheers!<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Julia Aebersold, Ph.D.<u></u><u></u></p>
<p>Manager, Micro/Nano Technology Center<u></u><u></u></p>
<p>University of Louisville<u></u><u></u></p>
<p>Shumaker Research Building, Room 233<u></u><u></u></p>
<p>2210 South Brook Street<u></u><u></u></p>
<p>Louisville, KY 40292<u></u><u></u></p>
<p>(502) 852-1572<u></u><u></u></p>
<p><u></u> <u></u></p>
<p><a href="https://urldefense.com/v3/__http://louisville.edu/micronano/__;!!Mih3wA!SQsxbaAkcj0DJgUdXOXwvjfrPpRj6T8X9DIo1XwXjvXU-n1Xr58tb-vRounntU32$" target="_blank">http://louisville.edu/micronano/</a><u></u><u></u></p>
<p><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
labnetwork mailing list<br>
<a href="mailto:labnetwork@mtl.mit.edu" target="_blank">labnetwork@mtl.mit.edu</a><br>
<a href="https://urldefense.com/v3/__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__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!Mih3wA!SQsxbaAkcj0DJgUdXOXwvjfrPpRj6T8X9DIo1XwXjvXU-n1Xr58tb-vRog_ymvJA$" rel="noreferrer" target="_blank">https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
labnetwork mailing list<br>
<a href="mailto:labnetwork@mtl.mit.edu" target="_blank">labnetwork@mtl.mit.edu</a><br>
<a href="https://urldefense.com/v3/__https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork__;!!Mih3wA!SQsxbaAkcj0DJgUdXOXwvjfrPpRj6T8X9DIo1XwXjvXU-n1Xr58tb-vRotJtKkZg$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__https://mtl.mit.edu/mailman/listinfo.cgi/labnetwork__;!!Mih3wA!SQsxbaAkcj0DJgUdXOXwvjfrPpRj6T8X9DIo1XwXjvXU-n1Xr58tb-vRotJtKkZg$</a> <br>
</blockquote></div>