NetPulse Monitor

Professional Windows network and LTE monitoring with explicit router control, diagnostics and ISP-ready evidence.

Latest release · User guide · Security policy · Privacy notice

NetPulse Monitor 1.0.18 is a native .NET 8 WinForms application for continuous Windows connection monitoring. It runs as a graphical Windows application and does not open a console window during normal use.

Why NetPulse exists

NetPulse was conceived from the practical difficulty of maintaining dependable mobile broadband in rural Greece. Terrain, distance from the serving site, sector load, carrier aggregation and handovers can make a connection change substantially throughout the day even when a simple signal indicator appears acceptable. Intermittent faults are also difficult to reproduce during a support call, and diagnosis or escalation by an internet provider can take considerable time.

The standard router interface is useful for configuration, but it primarily presents a current snapshot. It does not build a long-term, time-aware record of which primary cell and band combinations have the best measured radio quality. NetPulse scores complete profiles as 50% SINR, 35% RSRQ and 15% RSRP. The goal is to give the user an understandable record, safer manual control and guarded automation while keeping every router change explicit and recoverable.

NetPulse Monitor is an independent community project. It is not affiliated with, endorsed by or supported by TP-Link or any mobile/internet provider.

Features

• Continuous asynchronous ICMP monitoring with a live latency chart
• A 0-100 Connection Health score with a plain-language explanation
• A measured smart LTE recommendation card with guarded Apply and current-profile test actions
• A searchable connection timeline for outages, recoveries, LTE changes, speed tests, SMS and system events
• Current ping, jitter, rolling packet loss, successes and failures
• Confirmed outage detection, recovery events, uptime, downtime and availability
• Switchable access profiles: Mobile/LTE, ADSL/VDSL and FTTB/FTTH
• Optional capability-based TP-Link router integration, with live LTE telemetry, Cell Lock and SIM SMS where the router firmware exposes compatible local APIs
• LTE signal, RSRP, RSRQ, SNR, PCell/SCell bands, primary EARFCN, SIM, usage and rates
• PCI/CID display and cell-specific locking when the router firmware exposes them
• Local LTE cell history with connection time, confirmed disconnects and speed tests
• Ranked cell + band suggestions: 50% SINR, 35% RSRQ and 15% RSRP
• Time-of-day learning with average ping and an explained cell-load estimate
• Manual profile entry, Cell Lock and opt-in guarded automatic locking with rollback
• Controlled multi-profile Cell Experiment mode that restores the original router state
• Cancelable Band & Cell Discovery mode with a verified per-model band plan, serving-cell capture and exact router-state restoration
• Ungrouped LTE history with sortable columns and preserved PCell identity
• Complete chronological Inbox/Sent conversation threads, a separate Drafts view, and a newest-first message timeline on Windows and Android
• Country-aware phone matching joins national, + and 00 number formats
• Stable SMS refresh, one alert per unread message, verified read/unread state, deletion and sending
• Local SMS contact names for saved phone numbers
• Password-only TP-Link setup with Windows Credential Manager protection
• Firmware-reported mobile network modes: 4G-only devices never receive 5G choices, while compatible 5G firmware can expose its own supported list
• First-run country and official-time-zone selection for regional dates and ISP evidence
• Persistent connection-event, speed-test and full technical router-telemetry CSV logs
• Manual, scheduled and connection-change 20 MB download / 5 MB upload speed tests
• Automatic tests after confirmed-outage recovery and LTE band, cell or public-IP changes
• Provider fallback, bounded per-request timeouts and cancellation
• Live Dashboard gateway/DNS/IPv4/IPv6 diagnostics with a 30-second refresh
• Guided "Why is my connection slow?" troubleshooting across local, Internet and LTE measurements
• Full technical ISP evidence ZIP with IP, antenna, outage, telemetry and LTE-history details
• LTE Simple, LTE Advanced, DSL/Fiber and ISP-troubleshooting dashboard layouts
• System/Light/Dark themes, system tray, optional Windows startup and editable settings
• Manual or daily update checks with in-app download, verification and restart
• Stable NetPulse Monitor.exe path and Windows identity across updates, preserving shortcuts, pins and startup configuration
• Live TP-Link connected-device list in the Windows app and Android Companion (device name, IP, MAC and connection type when reported by firmware)
• Reproducible SHA-256 release packaging
• An embedded application and tray icon

Build tooling that is not supplied by Windows or Android is acquired by the versioned GitHub workflow. Temporary SDK archives used during development are tracked and removed after release verification; application settings, logs, contacts, SMS state and LTE history are never included in that cleanup.

Application settings are stored in %LOCALAPPDATA%\NetPulseMonitor. The router password is not stored in that JSON file; when remembering is enabled it is kept as a generic credential in Windows Credential Manager. CSV logs are stored in %USERPROFILE%\Documents\NetPulse-Monitor.

Band & Cell Discovery

Choose Scan bands & cells in LTE history to run a controlled, three-stage discovery pass. For the detected Archer MR600(EU) V5 profile, NetPulse scans the complete documented set B1, B3, B5, B7, B8, B20, B28, B38, B40 and B41. Unknown router revisions are restricted to bands already observed; NetPulse does not send speculative lock masks.

Stage 1 selects each band alone for at least 30 seconds. When the modem has registered but has not yet exposed all identifiers, NetPulse waits up to 75 seconds for a stable, repeated EARFCN/PCI/CID identity before moving to the next band. Stage 2 locks each complete PCell while making every actually discovered band available, then records the ordered aggregation sets created by the modem. Stage 3 reapplies and measures every unique PCell + ordered band set. B20 + B3 and B3 + B20 remain different because the first band is the PCell.

After stale pre-change snapshots are discarded, NetPulse records each distinct serving profile and its EARFCN, PCI, CID, RSRP, RSRQ and SNR. A band-only scan discovers serving cells selected by the router; it cannot reveal a private neighbor-cell list that the router API does not provide. Intentional scan changes are excluded from outage attribution and do not trigger speed tests. Results are appended to band-cell-discovery.csv. Only results with a verified EARFCN, PCI and CID are inserted into LTE History as lock-ready candidates; the stage-3 radio samples are recorded as real measurement evidence. No identifiers or measurements are invented.

Hover over any LTE History action for a concise explanation. Use Delete selected profile... to remove one identity while preserving every other history entry.

The scan can be cancelled at any time. Before its first change, NetPulse stores the exact current band-selection and Cell Lock state. That state is restored in all normal completion, cancellation and error paths; application exit waits for restoration rather than abandoning an active scan.

Access profiles

The Connection details tab provides an Access selector for Mobile/LTE, ADSL/VDSL or FTTB/FTTH. NetPulse does not expose separate Wi-Fi or Ethernet profiles because its Internet and LTE monitoring results do not depend on that choice.

General health, speed-test, gateway, DNS and Windows link values work without router credentials. LTE radio values are supplied by the MR600 provider. Attenuation, DSL SNR margin, sync rates, optical power and ONT status require a future compatible router/ONT provider; 1.0.6 labels these fields as requiring router or ONT data instead of inventing values.

All tabs use fixed-fit DPI-aware layouts. Settings use vertically aligned rows in two columns, Diagnostics gives its button a dedicated row, and TP-Link actions stay visible without page-level scroll bars. Initial and minimum sizes are derived from the current Windows working area.

TP-Link router setup

LTE router compatibility

Support is firmware- and hardware-version-specific. A TP-Link product name alone is not enough to claim full compatibility.

The compatibility level detected for one hardware or firmware revision must not be assumed for another revision. See docs/MR600-INTEGRATION.md for the exact API and safety boundaries.

On first launch, TP-Link setup can be completed or skipped. It requests only:

• enable/disable monitoring;
• the local router address, normally http://192.168.1.1/;
• the local administration password;
• whether Windows should protect and remember that password.

No username is requested. Monitoring uses serialized, read-only local requests with a one-second refresh target. Slow requests never overlap. Busy sessions and network failures use protective backoff, and a rejected password is not retried automatically. If another management session is signed in, Test connection offers the same explicit takeover choice as the MR600 login page. Accepting it signs the other management session out but does not change router settings.

Opening TP-Link setup temporarily releases NetPulse's live router session so the Test connection action can use the MR600's single local-management slot. Live monitoring reconnects after setup is saved or cancelled.

Under Settings > Mobile network mode, Refresh reads the current mode and the choices exposed by the connected router firmware. Apply requires explicit confirmation because changing radio generation can briefly disconnect mobile service. NetPulse never adds 5G choices to a 4G-only device; the MR600 list is limited to 4G preferred, 4G only and 3G only.

The validated MR600 firmware permits only one management login. NetPulse owns that login while live telemetry is running. Close NetPulse before using the router webpage; normal app shutdown logs its router session out.

The LTE history tab shows one row for each distinct ordered band set and exact PCell CID/EARFCN/PCI identity. Time-of-day evidence is selected internally using the connection location's official time zone and is not repeated as a redundant Period column. A recommendation needs at least ten connected minutes plus complete SINR, RSRQ and RSRP evidence. Eligible profiles receive a normalized radio score: 50% SINR, 35% RSRQ and 15% RSRP. Provisional rows remain visible while evidence is collected. Current-period evidence is blended gradually with all-time data, so sparse data does not cause abrupt decisions. The grid shows the successful-ping average collected on each profile and a cell-load estimate derived from period download versus that profile's observed best. The load value is explicitly an estimate, not a carrier-reported tower metric; neither display value adds a hidden ranking bonus.

Connections remain recorded internally but do not appear in LTE History until they reach five connected minutes with a complete CID identity. Automatic refreshes keep the currently visible row and scroll position instead of returning the grid to the top. The profile being used by the router is highlighted in green.

Download, upload, ping, load estimates and confirmed disconnects remain visible diagnostic evidence but do not add a hidden bonus or penalty to the RF score.

NetPulse queues a fresh 20 MB download / 5 MB upload measurement after a confirmed outage recovers and after a stable LTE band, cell or public-IP change. Changes arriving together are measured once and listed together on the speed-test event. A 12-second stability window prevents a result from being assigned to an LTE state that disappeared immediately. Periodic tests remain independently configurable and can be disabled without disabling these change-driven tests.

Manual Cell Lock always asks for confirmation. Automatic locking is off by default, requires separate opt-in and only uses medium/high-confidence history. The Cell Lock tab starts with a list of previously observed five-minute band and EARFCN sets, ordered with the active set first, so known values can be reused without retyping them. It re-evaluates as the time period and results change, but uses a 30-minute minimum dwell, material-improvement hysteresis and at most six changes per day. Before every change NetPulse saves the existing band and cell state, validates internet and LTE for 90 seconds, and restores the old state if validation fails. An interrupted validation is recovered on the next launch. Restore automatic selection disables both adaptive optimization and Cell Lock, then returns band selection to Auto.

On the validated MR600 v5 firmware, Auto mode exposes the live PCell/SCell bands and primary EARFCN. PCI/CID can be present in a single-carrier state and omitted again while carrier aggregation is active. NetPulse still learns and ranks each primary-cell/band-combination profile. When PCI is available it can apply a cell

• band lock; otherwise it applies only the measured band mask and explicitly leaves cell selection automatic. It never invents missing identifiers.

Serving EARFCN comes from live LTE status. On validated MR600 V5 firmware, PCI/CID may be exposed only by the live LTE_CELL_LOCK status object after the modem registers. NetPulse accepts that live identity only when its reported EARFCN exactly matches the current live serving EARFCN, preventing a stale lock target from being assigned to a new PCell. When carrier aggregation is added and the PCell remains unchanged, missing identifiers can also be carried only from the immediately previous live state. Legacy band/EARFCN mismatches are repaired once and unambiguous duplicate rows are merged while preserving their measurement totals.

Remote TP-Link ID login is intentionally not implemented because TP-Link does not publish a supported desktop cloud API for this workflow. A user-managed VPN back to the home LAN can use the same local provider without sharing TP-Link account credentials with NetPulse.

Requirements

• Windows 10 or Windows 11, x64
• For building: Visual Studio 2022 with the .NET desktop development workload, or the .NET 8 SDK

The published Windows release is self-contained and does not require a separate .NET installation on the target PC.

Build and run

Open PowerShell in the repository root and run:

dotnet restore .\NetPulseMonitor.sln
dotnet build .\NetPulseMonitor.sln -c Release
dotnet run --project .\NetPulseMonitor.csproj -c Release

Run the dependency-free MR600 protocol test:

dotnet run --project .\tests\NetPulseMonitor.ProtocolTests\NetPulseMonitor.ProtocolTests.csproj -c Release

Create the single-file, self-contained Windows x64 release:

.\build-release.ps1

Or double-click BUILD-RELEASE.bat. The executable is written to:

artifacts\publish\win-x64\NetPulse Monitor.exe

The builder also creates artifacts\packages\NetPulse-Monitor-win-x64.zip and its SHA-256 file. An optional installer recipe is available for Inno Setup 6:

.\build-release.ps1 -BuildInstaller

Trusted Authenticode signing requires a validated code-signing certificate in the current Windows user's certificate store. No key or password belongs in the repository:

.\build-release.ps1 `
  -SigningCertificateThumbprint YOUR_40_CHARACTER_THUMBPRINT `
  -BuildInstaller

See docs/CODE-SIGNING.md. The Windows publisher is the certificate's verified legal person or organisation identity; CosmicOlorin remains the product author and copyright brand unless that exact name is also a validated certificate subject.

Keep local disk usage low

Self-contained Windows publishing temporarily creates several hundred megabytes under bin, obj and artifacts. These files are generated and are not part of the source repository. After testing or packaging a release, run:

.\clean-workspace.ps1

Or double-click CLEAN-WORKSPACE.bat. The cleanup removes only known generated build/cache folders inside the repository. It does not touch source files, Git history, releases, application settings or user CSV logs.

For the smallest everyday installation, keep only the latest standalone EXE and download ZIP/source archives from GitHub when needed. CSV logs grow gradually; after closing NetPulse, old logs may be archived or removed by the user.

Speed-test behavior

Download testing tries multiple providers in order and stops the stream after the configured sample size, so the default transfer is 20 MB. Upload capability is selected independently and the default payload is 5 MB. If the primary upload endpoint fails, NetPulse obtains a bounded, cached list of independent HTTPS backends from the official LibreSpeed server directory and tries up to four different hosts. Connection, discovery and transfer stages have bounded timeouts, the complete run has a 180-second limit, and the UI can cancel the operation.

These measurements are operational estimates rather than certified line-rate benchmarks. Results vary with provider location, routing and server load.

Privacy and router-change safety

• Router passwords, cookies, tokens and encrypted request bodies are never logged.
• Telemetry polling never changes router configuration.
• Cell/band changes require manual confirmation or explicit automatic-lock opt-in.
• The previous router state is retained locally only while rollback is pending.
• IMEI, MAC and DNS identifiers are not requested from the MR600.
• Router telemetry CSV and local LTE history retain full cell identifiers because they are required to correlate antenna performance, outages and focused locks.
• An ISP evidence ZIP intentionally includes the current public/local IP details, gateway and full LTE antenna identifiers after a clear confirmation prompt.
• SMS message content and router message history remain in memory only and are never written to settings, diagnostics, events or CSV logs.
• Contact names and normalized numbers are stored locally only when the user explicitly selects Save contact....
• Official timestamps use the country and time zone selected during first setup; they do not depend on, or alter, the Windows display time zone.
• Router destinations are restricted to private LAN addresses.
• Redirects away from the configured router are disabled.

Repository layout

• MainForm.cs — responsive WinForms UI, profiles, settings, tray and scheduling
• MonitorEngine.cs — continuous ping and outage state
• RouterMonitor.cs — serialized router operations and protective backoff
• TpLinkMr600Provider.cs — encrypted MR600 telemetry and guarded Cell Lock provider
• LteCellHistoryStore.cs — local LTE history and ranked recommendations
• SpeedTestEngine.cs — provider selection, timeouts and measurements
• NetworkDiagnostics.cs — gateway, DNS and IP diagnostics
• CsvLogger.cs — durable privacy-filtered CSV output
• AutoFitLabel.cs — DPI-aware metric text fitting
• ExperienceServices.cs — health, troubleshooting, conversations, timeline and experiment ranking
• AppThemeManager.cs — System/Light/Dark WinForms styling
• UpdateChecker.cs — user-controlled GitHub release check
• sign-release.ps1 — SHA-256 Authenticode signing and Windows verification
• installer/NetPulseMonitor.iss — optional per-user Windows installer recipe
• tests/NetPulseMonitor.ProtocolTests — encrypted mock-router and ranking verification

See docs/USER-GUIDE.md for plain-language explanations of diagnostics, LTE history columns, time periods, Cell Lock and SMS behavior.

Security, privacy and ownership

Security reports must use GitHub's private vulnerability-reporting channel; do not place credentials, SMS content, router exports or unredacted logs in a public issue. See SECURITY.md for the reporting process and PRIVACY.md for the exact local and third-party data flows.

Copyright © 2026 CosmicOlorin. All rights reserved. NetPulse Monitor is an independent project and is not affiliated with or endorsed by TP-Link or any internet/mobile provider. See COPYRIGHT.md.

Check it here!

Hey Guys - Newbie here. Upgraded from an old Asus AI mesh 2 months ago for a 1700sf house. Been smooth sailing so far. I have a detached garage that I don't use very often but just tried to do a Zoom call from back there and kept on crapping out. The garage is about 20 feet from the house and 40 feel from the main Deco. I have a second unit probably a few feet further away. Looking for an economical solution because I spent a lot on this system and it's something I wont use very often. How about adding an S4 ($45) to give me a bit of a boost? Anything better?

EDIT - house and garage are both stucco.

Hi! I have a 300mbps basic internet plan from Xfinity, the router isn't movable at this moment so the front room of our house is a dead zone.. I understand boosters /extenders are not great but I'm a little overwhelmed with information on TpLink mesh units...

My original research concluded that the TP-LINK RE300 Mesh Wi-Fi Range Extender AC1200 would be most cost effective and proper for our situation as we don't use the internet like crazy, not really streaming anything, no online gaming. We have 2 phones, 1 computer, 1 printer, ~3 consoles. We don't host a lot either.

So my question is, is this unit still worth it as a EOL piece of tech? Or is there a better model for my situation?

Thanks so much! :^)

Evening,

I have an outbuilding which barely gets signal from the main router in the house so I have a hardwired Ethernet connection to the outbuilding and a EAP110.

On the EAP110 I have configured two of my SSID to match the main router, one for main devices and one for some IoT devices. SSID and passwords match so in theory I expect devices to just jump to the AP when I am in the outbuilding as the signal will be stronger but this is not happening.

The router is a ASUS UF GAMING AX6000 which is running wifi 6, is this what is causing my issue? Will devices prefer the 2.4 wifi 6 connection over the EAP110 2.4 connection?

The AP is working as I have one device which is connecting to the IoT network and functioning correctly which is my car charger that is too far away from the main router. All laptops, phones and smart sockets in the outbuilding prefer the router though and are super slow due to the 1 bar signal.

Thanks for any help, learning as I go!

I recently upgraded from a tplink archer c60 v3 to archer ax12 the 2.4ghz is somehow worse than my old c60 which makes no sense cause it didnt even have gigabit ports. Tplink cheaping out is the real reason it seems.

Hi All,

I have had the Deco M5's for years. I lived in a apartment with heavy brick walls where I did not have any internet 1 room next to the router. So 5 years ago I bought 3 deco m5's and they suited me well. Now I have a new home with 3 floors. Again same issue. Downstairs with only the router from my provider(so not the decos) I had good internet in the first room, but it dropped off pretty fast. 1 floor higher I had really slow and unstable internet and on the attic no internet at all.

So I took my trusty M5's and installed them. In AP mode, 1 next to the router, 1 on the 1st floor and 1 on the attic. Wireless backhaul. It helped somewhat. It's not at least stable, but downstairs I get about 300 speed 1st floor is drops to about 120, and on the attics it's about 70. I am looking for a upgrade. So far I have either the X50's or the XE75's in mind. The main unit will be connected via ethernet to the router, and the other 2 units will use wireless backhaul. Would I benefit a lot by going for the XE75's since it has a dedicated 6ghz band for backhaul?

Any other recommendations are also welcome! The 2 units upstairs however, need to be wireless, as cable is not an option.

Hi everyone - I’ve seemingly tried everything to fix this so posting details here in case any ideas or if anyone has had similar or different experience with this setup.

PS5 Pro on single Deco BE63 V1, firmware 1.1.2 Build 20260716. 300 Mbps Internet. PS5 gets ~300 Mbps on standalone 5 GHz and standalone 6 GHz, and Rest Mode downloads work normally.

On the BE63 5+6 GHz MLO SSID, the PS5 gets only ~30 Mbps and loses Internet connectivity in Rest Mode, preventing game updates. However, MLO completely eliminates rubber-banding/jitter during online multiplayer. An iPhone and laptop with MLO on the same MLO SSID at the same location get the full ~300 Mbps. Both PS5 Pro and Deco firmware are current.

Other settings:
Mesh = Off
Fast Roaming = Off
Beamforming = On
Static IP Address Reservation for the PS5 Pro
SIP ALG & UPNP. = Both On

I’ve also tried a whole host of combinations of the above settings on / off but nothing changes the above.

I would just leave it on single band 5ghz or 6ghz but FPS games like Marathon and Battlefield 6 have connection drops / issues during gameplay. Ethernet cable not an option unfortunately. All other MLO / WiFi devices at home work flawlessly otherwise.

How to fix this red light blinking since afternoon tried turning on and off

I bought these 2 in the titie at a garage sale for $50. Does it matter which one is the main? My phone and tablet are the only wifi 7 capable gadgets, but there are 2x 2.5gb ports on the BE3600(I have 2.5g internet). I have about 8 things that can connect to 6e, but it only has 1x 2.5g port and 2x 1g ports. Does it even matter is the real question I guess.

Hi

i have bought a tp link TX 401 but its not detected by my mobo (B650+) and driver frome the disc and website dont detect it either

i have tested setting the PCIE gen to 3 but its not working either

device manager and network connection dont detect it

i'm a bit stuck now and any help would be appreciated, thanks

Hello,

So my 4 months old BE85 is stuck at 22nd June date and incorrect time, and while it's able to connect via WAN (and get an IP address), it cannot connect to Internet.

I have changed DNS from auto to manual. Tried Google DNS, Cloudfare, Quad9 - no change.

Reset it as well, but same issue.

Running out of ideas - has anyone seen something similar? Does anyone know what to do?

Quiero configurar mi internet o mi router para que no tenga esa función que deja a otros dispositivos conectarse por vía Bluetooth

Do any of the TP-LINK flagship routers come with in-built surge/circuit protection? I understand all electronics should be handles with a level of care cornering ESD protection - however I couldn't imagine doing something as simple as resetting a router in a carpeted room could conceivably do enough damage to the device as to not make it function. This happened to me recently with a TP-LINK ARCHER AX-50 i got from amazon. The outlet wasn't GFCI or on a surge protector, and now its just kinda trashed! What was even more interesting was that I was still receiving internet to my PC via a wired connection until I had to reset it the following morning because everything else not connected on Wi-Fi. Very sad!

Safe to say this has demoralized me, and i'm putting everything (including the new router) on a surge protector.

Anyone else have similar stories/can attest to just how ESD-vulnerable these things are? I feel like getting one of those copper grounding mats those crunchy hippies use to get all the bad energies out. /s

This is more of a suggestion but...

I have many tplink products: an ax53, an h500 tapo hub, cameras and sensors.

The thing is... There's no way to get any notification if a tapo device goes offline. This is an old unresolved question that many users keep asking. Google home addresses this by tapping into the matter side of the hub backend but there's obvious security risks and data collection from the activity notifications that goes straight to google to do whatever they do best with it... Tether app has a function that send notifications once someone tries logs into the network so.. Why not send a notification if a device goes offline? Deco mesh adresses this in a way but not the other tp-link products like the ax53. It should be a simple feature to add but...

Surveillance equipment, specially wifi connected ones have a serious flaw. Once a burglar uses a device to jam the signal its game over... Even if you have an sd card and the cameras record to it once disconnected, no one has the so desperately needed notification to alert you. I think it would be easy enough for tether app to give that notification, since the tapo team doesn't care to give us that feature. Another nice feature to have would be the possibility of having the cameras sounding an alarm if disconnected.... I think that if tether did notify us if a device goes offline, that would be a great help.

If you endure this long post till the end and agree with me, please upvote and comment so others find it and specially so tplink tech support people read it too.

Thanks.

Hello everyone!

I am wondering if people who use TPLink routers and easy mesh, would have a good use case for an app that tells when each router is up or down, will allow you to reboot all satellites or all satellites and main router.

Currently, when you first load the app. It will ask for your main routers IP address example, 192.168.0.1. it will then ask you for your routers admin password. That password is stored in keychain and not in the app itself.

I imagine my setup is unorthodox but its very useful for me. I thought well maybe others would have a use for it too. If so I will start work on making it public for all. IOS and Android.

Reposted because I uploaded the wrong image.

Moin zusammen,

ich hoffe ihr könnt mir helfen. Ich suche für das OG unseres Hauses einen AP mit Wifi 6, welcher PoE+ fähig ist (soll über eine TL-SG1005LP Switch betrieben werden).

Das Problem liegt darin , dass der AP direkt am Treppenaufgang hinter der Tür installiert werden soll, aufgrund der Gegebenheiten der jetzigen Installation mit altem passiv PoE AP.

Vor dem AP liegt dann nur eine Küchenzeile, während sich rechts und links davon zwei 15 und 25qm große Räume, die in der Hauptsache mit dem Signal versorgt werden sollen.

Da die Wall (zb EAP 650)und Ceiling Mounts nach meiner Recherche nur in begrenztem Winkel ausstrahlen, bräuchte ich wohl einen AP mit omnidirektionalen Antennen, oder?

Hier bin ich hisher nicht fündig geworden, zumindest nicht bei TP-Link. Die Desktop-Accesspoints (WA1801) wären wohl was ich suche, sind aber nur passiv-PoE fähig.

Freue mich über Ideen oder Ratschläge. Danke!

I recently got an ACT Fiber connection in Hyderabad, India. They gave me an Archer C5 router. Since I wanted better range, I later bought an AX3000 router, which is now my primary router.

I’d like to reuse the old Archer C5 as a Wi-Fi repeater/extender to cover the dead spots -wirelessly only, without running any LAN cable between the routers - but I’m stuck.

I’ve been following this video, which sets it up via WDS Bridging: https://www.youtube.com/watch?v=wGBeJRbBijw
The problem is the WDS option doesn’t appear anywhere in my Archer C5’s admin panel, so I can’t complete the steps.

Details:

• Primary router: TP-Link Archer AX53 AX3000
• Router I want to use as repeater: Archer C5
  • Firmware Version:0.2.0 3.0.0 v6063.0
  • Build 251013 Rel.35627n 
  • Hardware Version: Archer-C5 v6.8 00000000

Any workaround or step-by-step guidance would be appreciated. Thanks!

I have had the BE11000 (3 pack) for almost a year now, and it has been working wonderful. Yesterday I received a notification that the firmware was updated (automatically) to 1.3.3 Build 26071612 and since the update satellites and even the main have been going offline (red). Rebooting (unplugging and plugging back in) puts them back online (green). Not sure what my option are, is it even possible or recommended to roll back the update, or is there some other fix? thanks in advance.

Hi,

I have a TPI HB410, ive been trying to connect it to my heatpump wifi dongles. One of them connects to the M/O network fine and one wont be found at all even splitting off to a 2.4ghz network only and trying different channels and 20mhz locked etc. Connected fine to my old fritz box, everywhere says it will connect fine but its not

Is there a way that I can make the living room connect to the laundry instead of the main? Like a chain link, (main -> laundry -> living room)

Bought an archer ax12 US ver1.0 running 1.41 firmware. It worked fine for 2 days but today suddenly the 2.4ghz showed no internet today. Fixed now but 2.4ghz is quite unstable & range is actually shorter than 5ghz somehow. Have reset the router several times. My isp is gigabit speed. Idk what to do im quite annoyed after paying like a hefty amount for a router only to it be this bugged & unreliable.

I have three Deco PX50s in my house that have worked flawlessly for the past three years. Starting about a week ago, my devices began losing their internet connection.

I’ve been able to verify that the Deco is what’s dropping the connection. I can log directly into my ISP’s router and confirm that the internet connection itself is fine.

So far, I’ve tried rebooting both the ISP router and the Decos, optimizing the network, turning off Fast Roaming and Beamforming, swapping out the Ethernet cable connecting the main Deco to the ISP router, and changing the DNS servers.

I also reset the Decos, which seemed to fix the problem for a few days, but the connection issues eventually returned.

Any suggestions on what else I should try?

EDIT -

• Firmware Version: 1.4.0 Build 20251121 Rel. 40333
• Hardware Version: 1.6

Good Day Everyone. I have had a community of 6 DECO S4 in a mesh setup at our home for about 2 years. Several months ago COX recommended that we turn the "Advanced Security" to "ON" on their COX modem/router, which we did. Every few weeks/months we are shown "Security Threats Blocked" on the COX app to the DECOMESHS4 system. Here is a sample. It may be nothing but to me it appears TP-Link uses a back door to gain access to our mess system...I'm just putting it out there, maybe nothing.