I'm experiencing a significant CPU usage and power consumption issue with WiFiman Desktop on Windows, even when no Teleport VPN connection is active.

Simply having WiFiman Desktop open causes my CPU to remain at approximately 3.5–4.0 GHz, even when the system is otherwise completely idle. The laptop's fan runs constantly, and battery life is severely affected.

As soon as I completely exit WiFiman Desktop, CPU frequencies immediately drop back to approximately 400–1500 MHz, the fan stops, and power consumption returns to normal.

System information

• Laptop: LG gram 17

• CPU: Intel Core Ultra 7 255H

• OS: Windows 11 (Build 26200)

• WiFiman Desktop: Version 1.3.0

• VPN: Disconnected (Teleport not in use)

Measured impact

My typical battery life drops from approximately 12 hours to just 4–5 hours when WiFiman Desktop is running.

I verified the increased CPU activity using Windows' built-in energy diagnostics:

powercfg /energy /duration 60 /output energy-report.html

Results from two consecutive 60-second measurements:

WiFiman closedWiFiman openAverage CPU utilization3.12%10.25%CPU frequency at idle400–1500 MHz3500–4000 MHzFanQuiet/offConstantly runningEstimated battery life~12 hours~4–5 hours

This is a substantial increase in CPU activity for an application that isn't even connected to a VPN.

Investigation: Repeated PowerShell and netsh process creation

I investigated the issue further using Microsoft Sysinternals Process Monitor.

The WiFiman background service (wifiman-desktopd.exe) repeatedly spawns new PowerShell processes, console host processes and Windows networking utilities.

The following commands were observed:

Get-NetAdapter | Select-Object IfIndex, Status, MacAddress, LinkSpeed

[Console]::OutputEncoding = [Text.UTF8Encoding]::UTF8; netsh wlan show interfaces

Get-NetIPInterface -ConnectionState connected -AddressFamily IPv4 | Select-Object IfIndex, InterfaceMetric

Additional commands include:

netsh wlan show networks mode=Bssid
route print 0.0.0.0
arp -a

In a roughly 111-second Process Monitor capture, I identified 72 external process launches initiated by WiFiman, excluding additional conhost.exe instances.

Several of these network queries repeat at approximately 10-second intervals, continuously creating new processes to retrieve adapter, WLAN and routing information.

The repeated PowerShell initialization and network polling appear to be contributing to the elevated CPU activity and preventing the system from spending sufficient time in low-power idle states.

Additional impact on low-power systems

I've also observed this behavior on Intel N100-based thin clients with passive cooling, where the additional activity causes increased temperatures and thermal throttling.

This is therefore not just a laptop battery-life issue but can also affect performance and thermal behavior on low-power systems.

Expected behavior / Suggested improvement

I understand that WiFiman provides WLAN discovery, signal monitoring and network diagnostics, which may require periodic network polling.

However, these features should not continuously consume system resources when they are not being used, especially when WiFiman is only needed as a Teleport VPN client.

I would strongly suggest implementing one or more of the following:

1. VPN-only mode: Allow users to run WiFiman exclusively as a Teleport VPN client, without continuous WLAN discovery, signal monitoring or network polling.

2. Configurable background monitoring: Provide an option to disable background network scanning or adjust its polling interval.

3. On-demand or event-driven updates: Query network information only when the relevant diagnostics view is open or when network configuration changes, rather than repeatedly launching PowerShell processes.

4. Improved process efficiency: Avoid repeatedly spawning external PowerShell and netsh processes where native Windows APIs or cached network information could be used instead.

Steps to reproduce

1. Start Windows and allow the system to settle into an idle state.

2. Observe CPU frequency, utilization and power consumption.

3. Open WiFiman Desktop 1.3.0 without establishing a Teleport connection.

4. Observe the increased CPU utilization and persistently elevated frequencies.

5. Use Process Monitor to observe repeated PowerShell and networking utility process launches.

6. Completely exit WiFiman Desktop.

7. Observe CPU frequencies and system power consumption returning to normal almost immediately.

Conclusion

This seems like an unnecessary amount of continuous background activity, particularly for users who primarily use WiFiman for Teleport VPN connectivity.

The issue persists in version 1.3.0 and has a major impact on battery life, fan noise and thermals.

Could the UniFi team investigate the continuous network polling behavior and consider adding a VPN-only mode or an option to disable background monitoring?

Could you please add our ISP logo to the UniFi Network and WiFiman ISP database?

Here are our network details:

• ISP Name: Quinault Indian Nation

• Display Name: Quinault Indian Nation

• ASN: AS21613

• Website: https://www.quinaultindiannation.com

I have attached a high-resolution, square version of our logo to this post. Please let me know if any additional verification or formatting is needed.

Thank you!

Attachments:

• QIN Logo No Background.png

Teleport is already usable for quick access, and I appreciate the existing basics within the Clients page and Settings > VPN > Teleport.

Compared to the rest of UniFi (e.g. WiFi, Site Magic, Client management), Teleport still feels unfinished though. Is there a roadmap for it? What I'm missing:

1. Time-based access

- Expiry for invites (an unused invite stays "Pending" indefinitely) and for authorized clients, e.g. "valid for 24 hours / 7 days / until date"

- Auto-close access after X hours

- A quick on/off toggle in the WiFiman app with an optional timer (e.g. "enable Teleport for 2 hours")

2. Better invite management

- Name/label per invite (e.g. "Mom's iPad"), so you know who it is for. Right now it's only a masked link and the hostname after acceptance

- Clear distinction/explanation of "Revoke Access" vs. "Unauthorize" vs. "Remove", and an option to temporarily disable a client without deleting it

3. Stats and history

- Session history per client (connect/disconnect times, source IP/country, duration)

- Traffic over time (not only current session counters)

- Events/log entries for invite created/accepted/revoked

4. Access control options per invite/client

- Choose which networks/VLANs a Teleport client may reach

- Optional bandwidth limit

- Optional "internet only" vs. "LAN access" mode

5. Network API support

Teleport is not exposed in the official Network API at all. Everything above should be available there too, so it can be used in automations (Home Assistant, scripts, etc.):

- list invites and Teleport clients

- create/enable/disable/revoke

- set expiry

- read stats

Use case: Giving family or friends temporary remote access to a home network or smart home without leaving permanent entries open or cleaning up manually.

Is any of this planned, and is there an estimated timeframe?

Setup: UniFi Network 10.6.109, DR7, WiFiman 1.37.1

Thanks!

The config file (firmware 7.5.15):

/usr/share/fanctrl/usw/ubnt-fanctrl-ed76-default.conf

(ed76 is your systemid; a symlink ubnt-fanctrl-ed76.conf points at it, and the daemon is ubnt-fanctrl, launched by /bin/fanctrl_wrapper.sh.)

It's not a temp→speed table. It's a PID loop. Each sensor has params: [setpoint, Kp, Ki, Kd, interval, min-output]. The CPU line is the one that matters.

Stock:

"CPU": { "params": [90, -1.0, -0.1, 0.0, 2, 30], ... }

That setpoint of 90 is the whole story. The fan isn't idle by accident — the controller is told to hold the chip at 90°C. So at 71° it's perfectly content and leaves the fan at its floor of 30. "Runs hot, fan never spins" is exactly what a 90 setpoint produces. (For reference: SFP targets 65, the PHYs target 105, and the fan PWM is at /sys/class/hwmon/hwmon0/device/pwm1.)

My change — lower the target, ramp harder:

"CPU": { "params": [60, -3.0, -0.2, 0.0, 2, 25], ... }

Setpoint 60, steeper gain, 25% floor. Result: fan runs around 49% and the chip drops from 71°C into the low 60s. Lower the 60 toward 55 for colder/louder, raise toward 65 for warmer/quieter.

Apply it live:

sed -i 's/\[90, -1.0, -0.1, 0.0, 2, 30\]/[60, -3.0, -0.2, 0.0, 2, 25]/' /usr/share/fanctrl/usw/ubnt-fanctrl-ed76-default.conf

kill $(pidof ubnt-fanctrl)

The wrapper respawns the daemon with the new curve in a couple seconds.

Two caveats:

1. It resets on reboot. The rootfs is in RAM, so the edit is gone on every power cycle and reverts to setpoint 90. /etc/persistent survives but nothing runs from it at boot, so there's no clean on-device persistence. I have a script on an always-on box that SSHes in and reapplies the curve whenever it sees the stock value, run from cron — a no-op unless the switch rebooted.

2. SSH voids your warranty. Ubiquiti's own CLI banner says modifying the device outside normal scope voids it. Your call.

Posting in case anyone else is tired of being told 70°C is just fine. It is fine for the silicon, but if you'd rather it ran cooler, now you know where the knob is.

@UI-Team

Today, all of a sudden I cannot connect to any of my Teleport devices. I thought it was authentication so I logged in again, no luck, I re installed WiFiMan 1.3.0 for Silicon over the current installation, again without luck, I restarted my macbook Pro M1 on macOS 27.2 with no luck.

Attached privately a log file, hope to find a solution fast.

@UI-Team

Thank you,

/F

I use WiFiman to keep an eye on my UniFi network, and I noticed the app doesn't yet fill the iPhone Duo display. Good news: it runs fine today, and Apple's guidance makes the upgrade fairly small. A rebuild with Xcode 27.1 removes most of the letterboxing, and the biggest wins are usually deciding layouts on size classes instead of orientation, replacing UIScreen.main, and letting toolbars and tab bars move to the side.

Three places to start:

• Prepare your app for iPhone Duo (Tech Talk): https://developer.apple.com/videos/play/tech-talks/111461/

• Three steps to make your app shine on iPhone Duo: https://developer.apple.com/iphone-duo/prepare/

• Prepare and submit your apps for iPhone Duo (note: iPhone Duo screenshots are required from April 2027): https://developer.apple.com/news/?id=kkphp5qo

Happy to share what I saw if useful. Thanks for the great app!

Best,

Jan-Pieter

In addition, once a device has accepted a Teleport invitation, it can connect without any further authentication. If the device is lost or stolen, anyone with access to it can reach the internal network. There is currently no option to require a second factor when connecting.

Request 1 - Standalone Teleport client:
Please provide a dedicated, lightweight Teleport VPN client app (Windows, macOS, iOS, Android), separate from WiFiman, that focuses only on:

• Connecting to / disconnecting from Teleport

• Managing Teleport invitations and saved sites

• Basic connection status (connected site, assigned IP, latency)

• Optional auto-connect / on-demand rules (e.g., connect when on untrusted Wi-Fi)
  

Alternatively, offer a "Teleport-only mode" in WiFiman that hides all non-VPN features.

Request 2 - Optional two-factor authentication on connect:
Please add an option for administrators to require MFA each time a Teleport connection is established, similar to how FortiClient SSL VPN works with FortiGate (username/password plus OTP token). Suggested options:

• TOTP (Google Authenticator, Microsoft Authenticator, etc.)

• Push approval via the UniFi app / UI account 2FA

• Per-user or per-device enforcement, configurable in UniFi Network

• Configurable re-authentication interval (e.g., every connection, every 24 hours)

• Logging of successful and failed authentication attempts
  

Benefit:
A focused VPN client would be simpler for end users and family members, easier to deploy, and use fewer resources. Optional MFA would close the gap with enterprise VPN solutions, protect the network if a device is compromised, and make Teleport a secure, first-class remote access solution for both home and business users.

@UI-Team I'd appreciate it if the product team could review this request, especially the optional MFA for Teleport connections. Thank you!

Use case:

Teleport makes efficient and painless provisioning via guest invite URL. While this guest invite URL overcomes basic deployment scenarios, where the UniFi gateway (UDM) is behind an upstream NAT device that is assigned a dynamic IP address, the Fedora Linux desktop is not able to connect via a teleport guest invite due to not having a WiFiman client.

Client computers running Fedora Linux are not able to launch and connect with a teleport guest invite.

Caveat of a A WireGuard VPN Server facilitated by UniFi Gateway (UDM):

Using a WireGuard VPN Server, in lieu of the Teleport architecture, is not feasible when the UDM is behind an upstream NAT device that is also using a dynamic IP address.

For example, the following statements are shown when setting up a WireGuard VPN Server hosted by the UniFi Gateway (UDM).

• “The server port needs to be forwarded on the upstream router as the UniFi Gateway is behind NAT.”
  and

• “This WAN IP is dynamically assigned and may change at any time. Enable Dynamic DNS and configure the Alternate Address so that clients can connect to the hostname.”

@UI-Team please continue the great work the @UI-Team does, and thank you for any thoughtful consideration to the above request.

Setup: self-hosted Network app on a Raspberry Pi (latest version, no UI account). UXG-Lite at .1, U6 Pro at .147 (6.8.2), UAP-AC-M at .169 (6.8.2), meshed to the U6 Pro. WiFiman 1.37.1 on iOS 27.0.1. The phone, my test Mac, and all UniFi devices are on the same LAN (192.168.1.0/24).

Ruled out: DNS filtering, client isolation, broadcast and multicast filtering, toggling the WiFiman setting, and toggling Network Discovery.

Findings:

• UAP-AC-M: mcad is listening on UDP 10001. A tcpdump on the AP shows WiFiman’s probes from the phone arriving by multicast (233.89.188.1) and broadcast, along with probes from the Network app host and the gateway. The AP never replies.

• U6 Pro: it answers only v1 probes, and only as UFP-UAP-B / Unifi-Protect-UAP-Bridge (config_status: default/unmanaged), not as a U6 Pro.

• UXG-Lite: it has no discovery responder. Port 10001 is held by dpi-flow-stats, and nothing binds it when Identification is disabled.

Did 6.8.x (or recent UXG-Lite firmware) intentionally stop adopted devices from answering discovery? Is there a way to restore WiFiman device identification on a self-hosted setup?

Attachments:

• Screenshot_WiFiman.jpg

OVERVIEW

Clicking Disconnect in WiFiman Desktop after using Teleport / WireGuard triggers a Blue Screen of Death (BSOD) on Windows 11 24H2.

The issue is caused by the bundled wireguard.exe located in C:\Program Files\WiFiman Desktop\WireGuard\, which is running version 0.5.3 (from 2022). The teardown routine in 0.5.3 has an asynchronous race condition during adapter and pool buffer deallocation against the hardened kernel heap manager and updated NDIS stack in Windows 11 24H2.

ENVIRONMENT

- OS: Windows 11 Pro / Enterprise (Version 24H2, Build 26100+)

- Application: WiFiman Desktop for Windows

- Bundled WireGuard Binary: C:\Program Files\WiFiman Desktop\WireGuard\wireguard.exe (Version 0.5.3)

SYMPTOMS AND CRASH DETAILS

When clicking Disconnect, the system immediately crashes with one of two stop codes:

1. 0x0000013A: KERNEL_MODE_HEAP_CORRUPTION

  - Parameter 1: 0x0000000000000011 (0x11)

  - Meaning: The kernel-mode heap manager detected an invalid internal state during pool free (heap corruption or double-free) during virtual adapter teardown.

2. 0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

  - Meaning: The tunnel driver was unloaded before all pending I/O packets and asynchronous unbind operations finished.

Event log sequence:

- Service Control Manager (Event 7045):

 Service Name: WireGuard Tunnel: wgwfm<id>

 Service File Name: "C:\Program Files\WiFiman Desktop\WireGuard\wireguard.exe" /tunnelservice "C:\Program Files\WiFiman Desktop\wgwfm<id>.conf"

- User clicks Disconnect in WiFiman

- WER-SystemErrorReporting (Event 1001):

 The computer has rebooted from a bugcheck: 0x0000013a (0x0000000000000011, 0xffffe20cc6000140, 0xffffe20cc6433300, 0x0000000000000000)

ROOT CAUSE

WiFiman Desktop spawns its tunnel service using its local binary:

"C:\Program Files\WiFiman Desktop\WireGuard\wireguard.exe" /tunnelservice <conf>

- Bundled version: 0.5.3

- Current official WireGuard version: 1.1.1 (WireGuardNT 1.1)

In Windows 11 24H2, kernel memory integrity and heap checking were made stricter. When wireguard.exe 0.5.3 stops the tunnel service, its adapter teardown logic frees memory pools while packets and IRPs are still draining, triggering an immediate BugCheck 0x13A or 0xCE.

VERIFICATION AND WORKAROUND

Replacing the bundled executables in C:\Program Files\WiFiman Desktop\WireGuard\ with the official 1.1.1 binaries completely resolves the crash.

Verification steps:

1. Closed WiFiman Desktop.

2. Backed up wireguard.exe and wg.exe in C:\Program Files\WiFiman Desktop\WireGuard\.

3. Copied wireguard.exe and wg.exe from the official WireGuard for Windows 1.1.1 installation into the WiFiman directory.

4. Relaunched WiFiman Desktop.

Log confirmation:

Before (crashed on disconnect):

[TUN] [wgwfm7141a335] Starting WireGuard/0.5.3 (Windows 10.0.26300; amd64)

After (disconnects cleanly, zero crashes):

[TUN] [wgwfm43ae538b] Starting WireGuard/1.1.1 (Windows 10.0.26300; amd64)

WiFiman continues to orchestrate connections, manage UI state, and disconnect without any issues using the 1.1.1 binaries.

REQUEST FOR UBIQUITI

Please update the bundled WireGuard and WireGuardNT components in the next WiFiman Desktop release from 0.5.3 to 1.1.x+ so Windows 11 24H2 is supported natively out of the box.

When I try to connect using Teleport, my network connection is completely lost during the connection process.

I uninstalled version 1.3.0 and reinstalled version 1.1.3, and Teleport works perfectly again on the same PC and network.

1.3.0 → Teleport disconnects the network

1.1.3 → Works correctly

No other configuration was changed.

It looks like a regression in 1.3.0, possibly related to the WireGuard/Teleport adapter or routing.

Is anyone else experiencing this issue?

Ready to shop Enabot? Before completing your order, take a moment to check the Enabot Discount Code "TAKEOFF".

The advertised promotion offers eligible shoppers an opportunity to get 35% OFF on qualifying purchases. That means you can check for potential savings before committing to the final checkout price.

🎯 Your 35% OFF Opportunity

Enabot Discount Code: "TAKEOFF"

Advertised Savings: 35% OFF

Apply: During the applicable checkout process

Instead of immediately paying the standard price, enter "TAKEOFF" and verify whether the promotion is successfully applied to your order.

✨ Why Check "TAKEOFF"?

A simple promotional code can make your shopping budget go further. The advertised 35% OFF may be useful when purchasing Enabot products for your home, pets, or smart living setup.

With the promotion, you can:

• Check for 35% OFF savings
• Potentially reduce your final order cost
• Apply the offer directly during checkout
• Verify your savings before payment
• Get more value from an eligible purchase

🛒 How to Use the Enabot Discount Code

1. Choose Your Enabot Product

Browse the available products and select what you want to purchase.

2. Go to Checkout

Review your cart and continue to the applicable checkout page.

3. Enter "TAKEOFF"

Find the promo or discount field and enter "TAKEOFF" exactly as shown.

4. Confirm the Discount

Check your order summary to see whether the advertised 35% OFF has been applied.

5. Complete Your Purchase

If you are eligible and the promotion is displayed correctly, proceed with your order.

💡 Don't Leave Savings on the Table

Promotional offers can change, and eligibility may vary by product, customer, or purchase conditions. That's why checking the Enabot Discount Code "TAKEOFF" before payment is an important step.

Even a quick check can tell you whether the advertised 35% OFF is available for your current order.

🔥 Ready to Check Your Savings?

If you're searching for an Enabot Discount Code, start with "TAKEOFF".

Enter "TAKEOFF" → Check 35% OFF → Review Your Final Price

Don't complete your purchase before checking whether the advertised 35% discount is available.

Use "TAKEOFF" at checkout and make your Enabot shopping experience more rewarding.

Whether you're choosing a proxy service for business activities, research, data collection, or other legitimate online needs, checking for an active promotion before payment can help you make a more cost-effective decision.

💎 Why "9P_WG18TWig" Is Worth Checking

A discount can make a noticeable difference, especially when selecting a longer-term or higher-value plan. The advertised 35% OFF associated with "9P_WG18TWig" gives shoppers an opportunity to potentially reduce their total spending.

Key highlights include:

• 35% advertised savings
• Easy to check during checkout
• Applicable to qualifying purchases
• Helps reduce the overall service cost
• Useful for customers comparing proxy plans

🛒 How to Get the 35% Discount

Applying the promotion is straightforward.

First, visit 9Proxy and explore the available services.

Next, choose the plan that fits your requirements and proceed to checkout.

Then, enter "9P_WG18TWig" into the appropriate coupon or promotion field.

Finally, review the order total and confirm that the advertised 35% discount has been applied before making your payment.

📈 Get More Value From Your 9Proxy Purchase

When purchasing proxy services, it's useful to compare pricing, features, usage requirements, and available promotions. A valid coupon can potentially make your chosen plan more affordable without changing the service you need.

That's why checking "9P_WG18TWig" before completing your order can be worthwhile.

🔥 9Proxy Discount at a Glance

Coupon: "9P_WG18TWig"

Discount: 35% OFF

Service: 9Proxy

Usage: Apply during eligible checkout

Availability: Subject to current promotional terms

❓ Common Questions

What is the 9Proxy Coupon Code "9P_WG18TWig"?

"9P_WG18TWig" is the promotional coupon associated with the advertised 35% discount for qualifying 9Proxy purchases.

How can I receive the discount?

Enter "9P_WG18TWig" in the applicable promotional field during checkout and verify the final order price.

Can the promotion change?

Yes. Promotional availability and eligibility may change. Always check the current terms before completing your purchase.

🚀 Don't Miss the Potential Saving

If you're ready to purchase a 9Proxy plan, don't complete checkout before checking the available promotion.

Enter "9P_WG18TWig", verify the advertised 35% discount, and enjoy the best available value if you're eligible for the offer.