<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Request for AP3915i WiNG 7 firmware – Home Lab Migration from Identifi in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121646#M10016</link>
    <description>&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Hello KaDar,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Even though the AP3915i (Identifi) hardware is identical to the AP7632 (WiNG), it's not possible to officially change the firmware.&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The argument has always been "Compliance" in the FCC certification.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;There are two solutions for this: try flashing the WiNG firmware via bootrom at your own risk, or migrate to OpenWRT.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I've never tried the first, but I have tried the second and it works well.&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I've already converted AP36xx, AP37xx, and AP38xx; I haven't tried with AP39xx yet, but the procedure is relatively straightforward. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The advantage of OpenWRT is that it has constant updates, and on older equipment it's possible to use WPA3, something that's not possible with the official firmware.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;When it comes to a network with few APs, the lack of centralized configuration isn't a big problem.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Raúl Carbonari&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Apr 2026 17:19:27 GMT</pubDate>
    <dc:creator>Raul_Carbonari</dc:creator>
    <dc:date>2026-04-23T17:19:27Z</dc:date>
    <item>
      <title>Request for AP3915i WiNG 7 firmware – Home Lab Migration from Identifi</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121640#M10014</link>
      <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;I’ve recently acquired three second-hand AP3915i-ROW units for my home network (3-story house). Currently, they are running on the Identifi (Thin AP) firmware and were previously used with an on-premise controller.&lt;BR /&gt;I would like to migrate them to WiNG 7 to use the Virtual Controller feature and manage them locally. Unfortunately, I am a private home user and I don't have an active support contract to download the image from the portal. Also, I cannot register them in XIQ (likely still bound to the previous owner's account).&lt;BR /&gt;Could anyone provide or point me to the WiNG 7 image for AP3915i? I really want to keep these professional units running in my home lab instead of switching to OpenWrt.&lt;BR /&gt;Model: AP3915i-ROW&lt;BR /&gt;Current goal: WiNG 7 Virtual Controller setup.&lt;BR /&gt;Thanks in advance for any help!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 12:50:17 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121640#M10014</guid>
      <dc:creator>KaDar</dc:creator>
      <dc:date>2026-04-23T12:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: Request for AP3915i WiNG 7 firmware – Home Lab Migration from Identifi</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121646#M10016</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Hello KaDar,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Even though the AP3915i (Identifi) hardware is identical to the AP7632 (WiNG), it's not possible to officially change the firmware.&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The argument has always been "Compliance" in the FCC certification.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;There are two solutions for this: try flashing the WiNG firmware via bootrom at your own risk, or migrate to OpenWRT.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I've never tried the first, but I have tried the second and it works well.&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I've already converted AP36xx, AP37xx, and AP38xx; I haven't tried with AP39xx yet, but the procedure is relatively straightforward. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The advantage of OpenWRT is that it has constant updates, and on older equipment it's possible to use WPA3, something that's not possible with the official firmware.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;When it comes to a network with few APs, the lack of centralized configuration isn't a big problem.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Raúl Carbonari&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 17:19:27 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121646#M10016</guid>
      <dc:creator>Raul_Carbonari</dc:creator>
      <dc:date>2026-04-23T17:19:27Z</dc:date>
    </item>
    <item>
      <title>Re: Request for AP3915i WiNG 7 firmware – Home Lab Migration from Identifi</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121648#M10017</link>
      <description>&lt;P&gt;Has anyone successfully migrated AP3915i to WiNG 7 in a lab without an existing support entitlement?&lt;/P&gt;&lt;P&gt;I understand production environments require licensing, but for home labs, it would be really &lt;SPAN&gt;&lt;A href="https://www.ezcardinfo.com.co" target="_self"&gt;ezcardinfocom&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;helpful if there were a documented upgrade or migration path—especially since these APs are widely available on the secondary market.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 04:11:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121648#M10017</guid>
      <dc:creator>joyacehunter01</dc:creator>
      <dc:date>2026-04-27T04:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Request for AP3915i WiNG 7 firmware – Home Lab Migration from Identifi</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121649#M10018</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thank you for the insight regarding the FCC compliance and the hardware identity between the AP3915i and AP7632. That’s a very valuable lead.&lt;BR /&gt;Interesting point about the firmware migration: I actually know for a fact that these specific units I have underwent a firmware change in the past. Originally, they were running a Cloud-ready (Unified) image, and the previous owner's IT provider manually flashed them with the Thin AP (Identifi) image to make them compatible with an on-premise controller.&lt;BR /&gt;Since they were already "converted" once from Cloud/Autonomous to Thin, there must be a way to flash them back or move them to WiNG 7 using the AP7632 image. I have full access to the U-Boot / Bootrom via the console cable.&lt;BR /&gt;Has anyone successfully forced an AP7632 WiNG image onto an AP3915i via TFTP in the bootloader? If so, are there any specific environment variables or hardware ID checks I should be aware of to avoid a brick?&lt;BR /&gt;I’m willing to take the risk on one of my four units to see if it accepts the WiNG 7 "identity". Any tips on the specific image filename or u-boot commands for this cross-flashing would be greatly appreciated!&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2026 05:03:02 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/request-for-ap3915i-wing-7-firmware-home-lab-migration-from/m-p/121649#M10018</guid>
      <dc:creator>KaDar</dc:creator>
      <dc:date>2026-04-24T05:03:02Z</dc:date>
    </item>
  </channel>
</rss>

