# Reclaim RAM used for WiFi firmware?

**URL:** <https://forum.gl-inet.com/t/reclaim-ram-used-for-wifi-firmware/58339>\
**Category:** Router\
**Created:** [May 10, 2025, 11:59am UTC](https://forum.gl-inet.com/t/reclaim-ram-used-for-wifi-firmware/58339 "2025-05-10T11:59:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![9b9e69c2-4b75-4420](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/9/a587f6/32.png) [@9b9e69c2-4b75-4420](https://forum.gl-inet.com/u/9b9e69c2-4b75-4420)\
**Post date:** [August 18, 2025, 11:13pm UTC](https://forum.gl-inet.com/t/reclaim-ram-used-for-wifi-firmware/58339/8 "2025-08-18T23:13:11Z")

</div>

Shutting down some `service | grep 'running'` might be an easy choice if you want to keep the GL GUI then.

Two thoughts:

- OWRT runs on x86\_64
- OWRT x86\_64 [runs in a VM](https://forum.gl-inet.com/t/gl-ar300m-vs-gl-ar300m16-questions/58000/4)

I model in a VM before pushing to bare metal. Vbox's 'snapshot' feature makes it so I can safely fawk around _and_ find out.

> **[\[OpenWrt Wiki\] OpenWrt on VirtualBox HowTo](https://openwrt.org/docs/guide-user/virtualization/virtualbox-vm)**

---

_[View the full topic](https://forum.gl-inet.com/t/reclaim-ram-used-for-wifi-firmware/58339)._