<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Home Lab on 0x2142 | Networking Nonsense</title>
    <link>https://0x2142.com/categories/home-lab/</link>
    <description>Recent content in Home Lab on 0x2142 | Networking Nonsense</description>
    <image>
      <title>0x2142 | Networking Nonsense</title>
      <url>https://0x2142.com/logo.jpg</url>
      <link>https://0x2142.com/logo.jpg</link>
    </image>
    <generator>Hugo -- 0.143.1</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Feb 2022 16:25:52 +0000</lastBuildDate>
    <atom:link href="https://0x2142.com/categories/home-lab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Video] Upgrading my Home Lab - Intel NUC11 &amp; ESX 7.0</title>
      <link>https://0x2142.com/home-lab-upgrade-intel-nuc11/</link>
      <pubDate>Mon, 07 Feb 2022 16:25:52 +0000</pubDate>
      <guid>https://0x2142.com/home-lab-upgrade-intel-nuc11/</guid>
      <description>In the video above, I walk through some of my recent upgrades to my home lab - which include two new Intel NUC 11 mini-PCs which will run ESX 7.0.</description>
      <content:encoded><![CDATA[<div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;">
      <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="allowfullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/141AtMDozt4?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe>
    </div>

<p><sup><em>Note: I may receive commissions for purchases made through links in this post. This is to help support my blog and does not have any impact on my recommendations.</em></sup></p>
<p>In the video above, I walk through some of my recent upgrades to my home lab - which include two new Intel NUC 11 mini-PCs which will run ESX 7.0.</p>
<p>Since most of what I did in the video is specific to my home lab setup, I didn&rsquo;t feel like it made as much sense to write out an entire step-by-step blog for the process.</p>
<p>That being said, I did still want a place to post links to everything I used in the video - including the actual hardware components &amp; the VMware community drivers. So here&rsquo;s where I&rsquo;ll keep that info!</p>
<hr>
<h3 id="vmware-community-drivers-used">VMware Community Drivers Used</h3>
<ul>
<li><a href="https://flings.vmware.com/usb-network-native-driver-for-esxi">Community driver for USB NIC Adapters</a></li>
<li><a href="https://flings.vmware.com/community-networking-driver-for-esxi">Community driver for additional NIC support</a></li>
</ul>
<h3 id="intel-nuc-11-parts">Intel NUC 11 Parts</h3>
<ul>
<li><a href="https://amzn.to/3rx0Xnz">Intel NUC11 Performance Barebones Kit (NUC11PAHi7)</a></li>
<li><a href="https://amzn.to/3ux8CnR">Samsung 970 Evo Plus - 1Tb</a></li>
<li><a href="https://amzn.to/3GyfN1d">Crucial Memory - 64Gb Kit (2x32Gb)</a></li>
<li><a href="https://amzn.to/3GF2Q64">UGREEN 1Gb USB Ethernet Adapter</a></li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>How to: Setting up Google Fi on a Netgear LTE Modem</title>
      <link>https://0x2142.com/how-to-setting-up-google-fi-on-a-netgear-lte-modem/</link>
      <pubDate>Thu, 09 Jul 2020 17:16:31 +0000</pubDate>
      <guid>https://0x2142.com/how-to-setting-up-google-fi-on-a-netgear-lte-modem/</guid>
      <description>Let&amp;rsquo;s walk though how to set up a  Netgear LTE modem to work with Google Fi&amp;rsquo;s cellular service</description>
      <content:encoded><![CDATA[<div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;">
      <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="allowfullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/809Zd4NQnVo?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe>
    </div>

<p><sup><em>Note: I may receive commissions for purchases made through links in this post. This is to help support my blog and does not have any impact on my recommendations.</em></sup></p>
<p>It&rsquo;s been a crazy couple of months recently. With what began as a temporary lockdown &amp; mandatory work-from-home has now become a question of &ldquo;Will we ever return to the office&rdquo;?</p>
<p>Luckily I have a decent home office setup, as my job is already primarily work from home. That being said - it&rsquo;s more important than ever to have a stable, reliable internet connection available. Can&rsquo;t run the risk of being in an important meeting with a customer and drop from the video conference (or have audio issues, etc).</p>
<p>Needless to say, my internet provider is far from perfect. While it does perform reasonably well most days, the spikes in latency &amp; packet loss have increased substantially with everyone in the neighborhood working from home.</p>
<p>I&rsquo;ve been debating for a while on whether or not to pick up a cellular modem. Originally I had planned on having one handy for a complete internet outage (which happens). But more recently I began to wonder if it might be worth it for routing around my primary provider when the connectivity is poor.</p>
<p>To accomplish this, I decided to use <a href="https://g.co/fi/r/KRT0VY">Google Fi</a>. I&rsquo;ve already used the service as my cellular provider for a number of years now and I&rsquo;ve been extremely pleased with the service. One of the awesome benefits they offer for subscribers is free data-only SIM cards. So I could pay nothing for the SIM card itself (no plan/recurring costs either) - then only pay for data as I use it.</p>
<p>First, I went ahead and tested what typical latency &amp; performance was over my cell connection. Occasionally my home internet provider would see latency spikes up to 1200-1800ms. Checking the cell connection - it seemed pretty stable in the 200-300ms range. Still pretty high, but much more bearable than ~1200ms. Seemed like it should work reasonably well for what I wanted.</p>
<p>Then, I had to double check compatability. Google Fi runs over multiple carriers on the backend - as long as you&rsquo;re using a Fi-compatible device. If not, it seems they default to only using T-Mobile&rsquo;s network. So in that case, Fi requires that our device supports LTE bands 2 &amp; 4 at a minimum. The Netgear LB1120/1121 modems do, so we&rsquo;re good there.</p>
<p>Next, I went ahead and ordered a <a href="https://amzn.to/3flccHi">NetGear LB1121</a> LTE Cellular modem. I opted for the power over ethernet model, since I already had a Cat5 run over to where the modem would be placed. The switch I&rsquo;m using is also being backed up by a UPS, so in the event of a power outage the LTE modem would stay online.</p>
<p>Finally - I placed my order for the Google Fi SIM card. Easy process - $0 for the SIM, $0 for shipping, and it arrived in only a few days. As an additional note - the modem requires a micro-SIM, but Fi provides nano-SIM cards. I also had to pick up a cheap adapter kit to make this work.</p>
<hr>
<h1 id="getting-the-modem-set-up">Getting the Modem Set up</h1>
<p>Once the modem &amp; SIM card arrive, it&rsquo;s time to get started. This will be a fairly quick and straightforward process.</p>
<p>On the bottom of the LTE modem, the device will list it&rsquo;s default IP address &amp; the password to log in. Take note of that, as you&rsquo;ll need it later.</p>
<p>Also on the bottom is the slot to insert the SIM card. Remove the cover, insert your SIM card into the micro-SIM adapter, then insert into the cellular modem.</p>
<p>Next, go ahead and power on the modem &amp; get it plugged into a PC.</p>
<p>Once the modem boots up - we should be able to reach it via a web browser @ 192.168.5.1.</p>
<p>Log in with the credentials from the bottom of the modem.</p>
<p><img alt="netgear-landing-page" loading="lazy" src="/content/images/2020/07/netgear-landing-page.PNG#center"></p>
<p>Upon landing on the main page, you may see that the modem auto-connects to T-Mobile&rsquo;s network. While we might be able to use this as-is, ideally we need to change our connection to specifically use Google Fi&rsquo;s information.</p>
<p>Head over to <strong>Settings</strong> &gt; <strong>General</strong> &gt; <strong>APN</strong>:</p>
<p><img alt="netgear-apn" loading="lazy" src="/content/images/2020/07/netgear-apn.PNG#center"></p>
<p>Click <strong>Add</strong> to create a new cellular profile</p>
<p><img alt="netgear-add-gfi" loading="lazy" src="/content/images/2020/07/netgear-add-gfi.PNG#center"></p>
<p>For the network <strong>Name</strong>, enter <strong>Google Fi</strong>. For the <strong>APN</strong> enter <strong>h2g2</strong>.</p>
<p>Click <strong>Save</strong> to add the profile</p>
<p>Then make sure to select the correct radio button to activate the new profile:</p>
<p><img alt="netgear-activate-profile" loading="lazy" src="/content/images/2020/07/netgear-activate-profile.PNG#center"></p>
<p>At this point, I would recommend deleting the old/default T-Mobile profile. I would also suggest rebooting the device to force it to switch to Google Fi.</p>
<p>If all is well - You&rsquo;ll log back in and see that the modem has now connected to the appropriate network:</p>
<p><img alt="netgear-gfi-connected" loading="lazy" src="/content/images/2020/07/netgear-gfi-connected.PNG#center"></p>
<p><em>Note: I&rsquo;ve had some issues where the carrier name doesn&rsquo;t display correctly. It may take a few minutes to finally display &ldquo;Google Fi&rdquo;. However, at this point you should be connected to the correct network and be able to use it with no issues</em></p>
<h1 id="additional-settings">Additional Settings</h1>
<p>One other thing that may be worth noting. Depending on how you&rsquo;re using the modem, you may want to change the way the modem operates.</p>
<p>Let&rsquo;s go ahead and check out a few options on the LAN settings page. This can be found by going to <strong>Settings</strong> &gt; <strong>Advanced</strong> &gt; <strong>LAN</strong>.</p>
<p><img alt="netgear-lan-opts" loading="lazy" src="/content/images/2020/07/netgear-lan-opts.PNG#center"></p>
<p>By default, the modem operates in <em>router</em> mode. What this means is that the modem terminates the connection from Google Fi - and acts as a gateway between your devices &amp; the carrier network.</p>
<p>You would want to use <em>router</em> mode if you have multiple devices you want to use with the modem &amp; you do not have an additional router or firewall. In this case, the modem will handle providing IP addresses to the client devices. In addition, it will act as a firewall and allow client devices to the internet, while blocking any external devices from accessing the clients directly.</p>
<p>The other available mode is <em>bridge</em> mode. In this case, the modem operates as a pass-through device &amp; assumes that there is another device behind the modem that is providing the routing/firewalling functionality.</p>
<p>You may want to use <em>bridge</em> mode if you already have a router or firewall you want to use - and you want to treat the modem as a second internet connection. When the modem connects to the provider, it will automatically pass the public IP address &amp; configuration straight through to whatever device is plugged into it.</p>
<hr>
<p>If you&rsquo;re interested in how I configured the auto-failover to the cellular modem - check back in a bit. I wrote some custom automation to monitor my primary connection &amp; conditionally inject a route over the LTE modem.</p>
<p>I&rsquo;m just wrapping up some of that, and should have something posted here shortly!</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
