{"id":101,"date":"2026-06-12T14:23:01","date_gmt":"2026-06-12T14:23:01","guid":{"rendered":"https:\/\/2026.quickfreeze.com\/engineering-guide\/wifi-networking\/"},"modified":"2026-06-12T14:57:53","modified_gmt":"2026-06-12T14:57:53","slug":"wifi-networking","status":"publish","type":"page","link":"https:\/\/quickfreeze.com\/es\/engineering-guide\/wifi-networking\/","title":{"rendered":"WiFi &#038; Networking"},"content":{"rendered":"<style>\n.qf-eg-eyebrow{display:block;text-transform:uppercase;letter-spacing:.14em;font-size:.85rem;font-weight:700;opacity:.85;margin-bottom:.4rem;}\n.qf-eg-table{width:100%;border-collapse:collapse;font-size:.9rem;margin:1.25rem 0;background:#fff;}\n.qf-eg-table th{background:var(--qf-blue,#005EB8);color:#fff;text-align:left;padding:.55rem .8rem;border:1px solid #c9d4e0;font-weight:600;}\n.qf-eg-table td{padding:.55rem .8rem;border:1px solid #c9d4e0;vertical-align:top;}\n.qf-eg-table tbody tr:nth-child(even){background:#eef2f7;}\n.qf-eg-note{background:#fff8e8;border-left:5px solid #e8a317;padding:1rem 1.25rem;margin:1.5rem 0;border-radius:0 6px 6px 0;}\n.qf-eg-note p{margin:.35rem 0;}\n.qf-eg-faq details{background:#fff;border:1px solid #d9e1ea;border-radius:6px;margin:.6rem 0;padding:.7rem 1rem;}\n.qf-eg-faq summary{font-weight:600;cursor:pointer;color:var(--qf-dark,#101820);}\n.qf-eg-faq details p{margin:.6rem 0 .3rem;}\n.qf-eg-pager{display:flex;justify-content:space-between;gap:1rem;flex-wrap:wrap;}\n.qf-eg-pager a{font-weight:700;color:var(--qf-blue,#005EB8);text-decoration:none;}\n.qf-eg-pager a:hover{text-decoration:underline;}\n<\/style>\n<div class=\"qf-hero\">\n<span class=\"qf-eg-eyebrow\">Engineering Guide &middot; Section 5 of 6<\/span><\/p>\n<h1>WiFi y redes<\/h1>\n<p class=\"lead\">QFMs are outbound-only IoT devices \u2014 no PLC, no inbound connections, no internal network access \u2014 talking HTTPS to two domains at about a kilobyte per unit every five minutes.<\/p>\n<\/div>\n<div class=\"qf-section\">\n<div class=\"qf-container\">\n<h2>What the Network Sees<\/h2>\n<p class=\"section-sub\">The one-paragraph version for your IT security review.<\/p>\n<p>The QFMs are IoT devices that need access to the QuickFreeze cloud \u2014 there is no connection to a PLC or to any controls network. Every connection is initiated outbound from the unit over HTTPS (port 443) to <strong>qfmonitoring.com<\/strong> y <strong>quickfreeze.com<\/strong> only; no inbound ports are opened, and the units need no access to internal network resources. Traffic per unit is roughly <strong>1&nbsp;KB of telemetry every 5 minutes<\/strong> plus a configuration pull about every 15 minutes \u2014 otherwise the radios are idle. A 500-unit fleet generates on the order of a few megabytes per day. This is the profile your firewall team approves in one meeting, not three.<\/p>\n<\/div>\n<\/div>\n<div class=\"qf-section alt\">\n<div class=\"qf-container\">\n<h2>Requisitos de red<\/h2>\n<p class=\"section-sub\">Per MKT-212.8, the current Internet Security Standards and Network Requirements.<\/p>\n<table class=\"qf-eg-table\">\n<thead>\n<tr>\n<th>Parameter<\/th>\n<th>Requirement<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>WiFi band<\/td>\n<td>2.4&nbsp;GHz only \u2014 802.11 b\/g\/n (no 5&nbsp;GHz)<\/td>\n<\/tr>\n<tr>\n<td>Security<\/td>\n<td>WPA2-PSK<\/td>\n<\/tr>\n<tr>\n<td>IP assignment<\/td>\n<td><strong>IPv4 DHCP required<\/strong> \u2014 static IP assignment is not supported; one IP per unit, so size the DHCP scope for the full fleet<\/td>\n<\/tr>\n<tr>\n<td>Firewall<\/td>\n<td>Allow outbound HTTPS (443) to qfmonitoring.com and quickfreeze.com only; outbound-only, no inbound ports<\/td>\n<\/tr>\n<tr>\n<td>Internal access<\/td>\n<td>None needed \u2014 no internal network resources, no PLC, no controls VLAN<\/td>\n<\/tr>\n<tr>\n<td>Bandwidth<\/td>\n<td>~1&nbsp;KB telemetry upload per unit per 5 minutes; configuration pull per ~15 minutes; otherwise idle<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"qf-eg-note\">\n<p><strong>Design pitfall \u2014 working from an older requirements sheet.<\/strong> The earlier 2-pager (MKT-316) stated that DHCP <em>o<\/em> statically assigned addresses could be used. That document is superseded: per MKT-212.8, <strong>DHCP only<\/strong>. If your IT team scoped static addressing from an old copy, re-baseline against the current MKT-212 revision at the permanent URL below \u2014 it always serves the latest version.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"qf-section\">\n<div class=\"qf-container\">\n<h2>Commissioning Flow<\/h2>\n<p class=\"section-sub\">No per-unit programming \u2014 the fleet provisions itself through a temporary SSID.<\/p>\n<p>Units arrive factory-configured to auto-join a setup network, so commissioning is a network exercise, not a box-by-box one:<\/p>\n<table class=\"qf-eg-table\">\n<thead>\n<tr>\n<th>Step<\/th>\n<th>Who<\/th>\n<th>Action<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1<\/td>\n<td>Customer IT<\/td>\n<td>Broadcast the temporary setup SSID <strong>QF_Config<\/strong> (credentials in MKT-212). The signal must blanket the <em>entire<\/em> freezer \u2014 every unit position.<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Install crew<\/td>\n<td>Power up the rows; units auto-join QF_Config. (A 200-unit fleet joining within minutes is normal.)<\/td>\n<\/tr>\n<tr>\n<td>3<\/td>\n<td>Customer + QuickFreeze<\/td>\n<td>Enter the production SSID and password into the QFM dashboard \u2014 no on-site programming of individual units.<\/td>\n<\/tr>\n<tr>\n<td>4<\/td>\n<td>Units<\/td>\n<td>Each unit downloads the new credentials over QF_Config and switches itself to the production network.<\/td>\n<\/tr>\n<tr>\n<td>5<\/td>\n<td>Everyone<\/td>\n<td>Watch the <strong>Disconnected<\/strong> count on the dashboard fall to <strong>0<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td>6<\/td>\n<td>Customer IT<\/td>\n<td>Retire QF_Config \u2014 it is no longer needed once all units are on the production SSID.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>MKT-212 links a tutorial video for the dashboard side of this flow. Connectivity is also what unlocks the performance features \u2014 air temperature, product temperature, and seal-quality data collection, and AutoSense once it is confirmed with collected data \u2014 so treat the network as part of the freezing system, not an accessory.<\/p>\n<div class=\"qf-eg-note\">\n<p><strong>Design pitfall \u2014 the most common commissioning failure.<\/strong> It is not the QFMs: it is a customer switch port that was never activated by their IT department. Confirm port activation and SSID coverage <em>before<\/em> install week, and have your WiFi\/IT point of contact named at project kickoff \u2014 racking, power, and network each get a binary go\/no-go before mobilization.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"qf-section alt\">\n<div class=\"qf-container\">\n<h2>Wired Alternative: the Ethernet Option<\/h2>\n<p class=\"section-sub\">Per MKT-313 \u2014 for facilities that prefer copper to radio.<\/p>\n<table class=\"qf-eg-table\">\n<thead>\n<tr>\n<th>Scope item<\/th>\n<th>Provided by<\/th>\n<th>Detail<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Ethernet drop<\/td>\n<td>Customer (&#8220;by others&#8221;)<\/td>\n<td><strong>1 drop per up to 60 QFM units<\/strong> (more depending on layout; units must be physically adjacent \u2014 in practice, one drop at the end of each row)<\/td>\n<\/tr>\n<tr>\n<td>Ethernet-capable QFMs<\/td>\n<td>QuickFreeze<\/td>\n<td>Specified at order time<\/td>\n<\/tr>\n<tr>\n<td>Modular Ethernet switches<\/td>\n<td>QuickFreeze<\/td>\n<td>1 per unit, plus 2 patch cables per unit<\/td>\n<\/tr>\n<tr>\n<td>Switch power supply<\/td>\n<td>QuickFreeze<\/td>\n<td>1 per switch group, mounted during QFM installation<\/td>\n<\/tr>\n<tr>\n<td>Addressing<\/td>\n<td>Customer DHCP<\/td>\n<td>DHCP only; one IP per unit, same as WiFi<\/td>\n<\/tr>\n<tr>\n<td>Firewall<\/td>\n<td>Customer<\/td>\n<td>Whitelist qfmonitoring.com and quickfreeze.com; same outbound-443-only profile and ~1&nbsp;KB\/5&nbsp;min bandwidth<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Separate 120&nbsp;V drops for network gear are no longer required \u2014 switch power rides the QFM installation. The Ethernet option and WiFi carry identical security posture; choose based on your site&#8217;s RF environment and IT policy.<\/p>\n<\/div>\n<\/div>\n<div class=\"qf-section\">\n<div class=\"qf-container\">\n<h2>Documents<\/h2>\n<p class=\"section-sub\">Permanent URLs \u2014 always the current revision.<\/p>\n<div class=\"qf-grid\">\n<div class=\"qf-card\">\n<span class=\"card-tag\">MKT-212<\/span><\/p>\n<h3>Internet Security Standards &amp; Network Requirements<\/h3>\n<p>The current network standard: band, encryption, DHCP, firewall rules, bandwidth, and the commissioning tutorial video.<\/p>\n<p><a href=\"https:\/\/quickfreeze.com\/es\/docs\/mkt-212\/\">Ver<\/a> - <a href=\"https:\/\/quickfreeze.com\/es\/docs\/mkt-212\/download\/\">Descargar<\/a><\/p>\n<\/div>\n<div class=\"qf-card\">\n<span class=\"card-tag\">MKT-313<\/span><\/p>\n<h3>QFM Ethernet Option<\/h3>\n<p>The wired alternative: drop count, switch hardware, and the by-others vs by-QuickFreeze scope split.<\/p>\n<p><a href=\"https:\/\/quickfreeze.com\/es\/docs\/mkt-313\/\">Ver<\/a> - <a href=\"https:\/\/quickfreeze.com\/es\/docs\/mkt-313\/download\/\">Descargar<\/a><\/p>\n<\/div>\n<div class=\"qf-card\">\n<span class=\"card-tag\">Demo<\/span><\/p>\n<h3>Panel de control de ejemplo<\/h3>\n<p>See what the monitoring side looks like \u2014 the same dashboard used to provision SSIDs and watch the Disconnected count during commissioning.<\/p>\n<p><a href=\"\/es\/sample-dashboard\/\">View the sample dashboard &rarr;<\/a><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"qf-section alt\">\n<div class=\"qf-container\">\n<h2>Networking FAQ<\/h2>\n<p class=\"section-sub\">What IT security teams ask before approving the connection.<\/p>\n<div class=\"qf-eg-faq\">\n<details>\n<summary>Do the QFMs connect to our PLC or controls network?<\/summary>\n<p>No. The QFMs are IoT devices that need access to the QuickFreeze server only \u2014 there is no PLC connection, no controls integration at the network layer, and no inbound access of any kind. Outbound HTTPS 443 to two domains is the entire footprint.<\/p>\n<\/details>\n<details>\n<summary>Can we assign static IPs?<\/summary>\n<p>No \u2014 IPv4 DHCP is required per the current standard (MKT-212.8); static assignment is not supported. An older 2-pager permitted static addressing and is superseded. Each unit needs its own address, so size the DHCP scope for the full fleet plus growth.<\/p>\n<\/details>\n<details>\n<summary>How much bandwidth does a fleet consume?<\/summary>\n<p>About 1&nbsp;KB of telemetry per unit every 5 minutes plus a ~1&nbsp;KB configuration request every 15 minutes. Even at several hundred units, total traffic is a rounding error on any facility uplink.<\/p>\n<\/details>\n<details>\n<summary>Our facility WiFi is 5&nbsp;GHz only. Will that work?<\/summary>\n<p>No \u2014 the units use 2.4&nbsp;GHz 802.11 b\/g\/n with WPA2-PSK. You will need a 2.4&nbsp;GHz SSID covering the freezer interior. The 2.4&nbsp;GHz band also propagates better through racking and product, which is why it is the design choice.<\/p>\n<\/details>\n<details>\n<summary>A unit shows offline after commissioning \u2014 where do we start?<\/summary>\n<p>Physical inspection first: the common findings are damaged control boxes, unplugged cords, and disconnected QFM power cables. With physical issues ruled out, power-cycle the affected boxes and coordinate with IT \u2014 and check whether the relevant switch port was actually activated, which remains the most common root cause of a whole row offline.<\/p>\n<\/details>\n<\/div>\n<div class=\"qf-eg-pager\" style=\"margin-top:2rem;\">\n<a href=\"\/es\/engineering-guide\/power\/\">&larr; Section 4: Power<\/a><br \/>\n<a href=\"\/es\/engineering-guide\/wms-api-integration\/\">Section 6: WMS &amp; API Integration &rarr;<\/a>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"qf-section dark\">\n<div class=\"qf-container\">\n<h2>Get IT in the Room Early<\/h2>\n<p class=\"section-sub\">Network sign-off is one of the binary pre-mobilization checks \u2014 clear it weeks before install, not during.<\/p>\n<div class=\"wp-block-buttons\" style=\"display:flex;gap:1rem;justify-content:center;flex-wrap:wrap;\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link\" href=\"\/es\/quickfreeze-blast-ready\/\">Request a Blast Ready Review<\/a><\/div>\n<div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"\/es\/contact\/\">Hable con Ingenier\u00eda<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Engineering Guide &middot; Section 5 of 6 WiFi &amp; Networking QFMs are outbound-only IoT devices \u2014 no PLC, no inbound connections, no internal network access \u2014 talking HTTPS to two domains at about a kilobyte per unit every five minutes. What the Network Sees The one-paragraph version for your IT security review. The QFMs are&#8230;<\/p>","protected":false},"author":0,"featured_media":0,"parent":96,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_seopress_titles_title":"QFM WiFi & Network Requirements | QFM Engineering Guide","_seopress_titles_desc":"Network design for QFM fleets: 2.4 GHz WPA2 WiFi, DHCP, outbound-only HTTPS, the QF_Config commissioning flow, and the wired Ethernet option.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"class_list":["post-101","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/pages\/101","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/comments?post=101"}],"version-history":[{"count":1,"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/pages\/101\/revisions"}],"predecessor-version":[{"id":117,"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/pages\/101\/revisions\/117"}],"up":[{"embeddable":true,"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/pages\/96"}],"wp:attachment":[{"href":"https:\/\/quickfreeze.com\/es\/wp-json\/wp\/v2\/media?parent=101"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}