Maintaining Confidentiality of Sensitive Data
The next article for Cybersecurity Month is here! This article defines sensitive data and provides some best practices for securing it.
How do you ensure the confidentiality of sensitive data in your network? Let us know in the comments!
Neil here with the Community team! Just here announcing the update highlights for September. You can find the full list of updates in the links below.
Controller Highlighted Feature Updates
No new updates for Controllers this month. We're working on 6.4, which will add a migration process for the new Fusion Gateways, but there's no concrete ETA just yet. Just keep an eye out for the pre-release firmware on the forums.
As for EAPs, there were a few updates. More EAPs now have the Remote Adoption toggle in Standalone mode. Turning off Remote Adoption will remove the DNS requests for the Omada Controller, clearing up some of that DNS traffic on your networks.
Lastly, some models are now compatible with Controller v6.1, which adds Client Health and IP Group ACLs. I recommend using your browser's Find in Page feature to see whether your model is on the list. If it is, it should automatically expand the relevant dropdown.
Posting something a little lighter to close out September. I spent the month playing with a VIGI NVR, and while it may not be as technically exciting, I hope this at least gives people some ideas for when the Fusion Pros release!
I plan on getting one for myself once they do, so let me know if you'd like to see any specific experiments or tests done with third-party cameras/VIGI cameras!
(If my bosses are looking, this definitely wasn't made just to make a silly thumbnail of my cat.)
How do I control access to my surveillance network?
Our newest reference guide is here! This goes through a few options for controlling access to camera networks, but is by no means incomplete! We've seen some great discussions so far here on reddit! We want to know, what do you consider best practices for securing your surveillance network? Let us know either here on r/Omada_Networks or on the forums!
Hey Omada Community! Did you know we have a collection of highlighted feature updates for our Controllers and EAPs? You can find the archive of monthly updates in the Knowledgebase section of the Forums (or via the links below).
Controller Highlighted Feature Updates
Controllers got a big update with Omada 6.3, which added the following features:
^(1) Denotes a feature previously exclusive to Omada Pro Controllers. Non-Pro Omada APs may require firmware compatible with Controller 6.3 to take advantage of these features.
^(2) Not available on the OC200 (all versions), ER7212PC V1, and ER7212PC V2.
As for EAPs, a few added support for dynamic VLAN assignment through DHCP option 82. Should be helpful for those of you tinkering around! Check the dropdown in the EAP highlights article for an exact model list.
In the future, check the sidebar (Support Resources) for a quick link to the update archives! Let us know if you're looking for any specific features in the future! We'll be sure to include it in the highlights, so you can stay informed on what comes next.
Secure Your Surveillance Network in 5 Minutes — Why Cameras Need Their Own VLAN
You've bought your brand-new security system setup, great! But did you know there's more to setting up a secure surveillance network than just plugging cables in? Our newest reference guide is here, Secure Your Network in 5 Minutes - Why Cameras Need Their Own VLAN, and it goes through a very brief way to secure your surveillance networks. Give it a read, and if you found it helpful, please let us know!
What other guides would you like to see regarding surveillance networks? We're always receptive to feedback and want to provide content that is useful to you.
Our article series, Applying Omada, released its 8th article this morning. This series is meant to provide real-world scenarios that offer some insights into use cases and the troubleshooting process.
This month's article covers a wireless network setup for an apartment complex and some troubleshooting that can be done if (when) issues arise. Got a topic you want to see covered in a similar manner? Let us know in the comments below!
Your Travel Guide to Network Address Translation
Our newest reference guide, Your Travel Guide to Network Address Translation, is out on the forums!
For those just getting into networking, this article gives an explanation of NAT/PAT. As a kid setting up his first video game server, I would have loved an explanation like this. Let me know in the comments if you feel the same, or if you want to see any specific networking features highlighted in their own reference guide!
We just posted a reference guide detailing Access Control Lists (ACLs) and how they work in an Omada network! It goes over the different types of ACLs supported by Omada devices and how you can use them in your networks. Take a look and let us know if you found it helpful or if you'd pass it along to someone just getting started in computer networking!
As always, we're looking to make relevant, helpful content for the community, so if you have any suggestions or topics you want to see covered, please don't hesitate to let us know!
We released our 7th article for Applying Omada today (formerly known as Omada Client Solutions)! The name change reflects our desire to show how Omada devices can be implemented in your networks.
This article briefly goes over the setup of a new LightLink VPN and highlights the benefits of the Fusion Gateways! If you've gotten a Fusion 2.5G already, what benefit or improvement would you want to see? Let us know in the comments below!
The Fusion 2.5G, out now on the Omada Store!
The Fusion 2.5G is now available on the Omada Store! We've got a quick overview of the features along with some common questions on our forums here. Check out some of the highlights of the new gateway here!
All this is supported by the built-in controller with license-free cloud management. Manage your network from anywhere with no annual fees.
Lastly, as a member of your community team here, I'm excited for you all to experience the product for yourselves! Our Pioneers have been giving great feedback and sharing their experiences with us, but I want to invite you all to share yours in the comments below as well! Always happy to see what you all come up with!
Want to learn more? Check out the product overview page here.
Heard enough and want one for yourself? Here's the store link for you!
A Technical Look at VLANs with Omada
Liked our previous VLAN guide but want a bit more info? This reference guide goes a bit more into the technical aspects of VLANs and their use with Omada devices. The doc was made with assistance from one of our community members, so thank you to u/jra11500 for your contributions!
We're always open to any feedback or requests for more reference guides like this; feel free to leave your thoughts and ideas in the comments!
Struggling to understand how to divide your network properly? Take a look at our quick breakdown of 802.1Q VLANs. The guide provides a brief summary of what VLANs do for your network and how to use them.
Let us know what other VLAN-specific topics you'd like to see covered in the form of a reference guide down below!
What's up, r/Omada_Networks! The support team is hard at work making new video guides and content for our users and wants to know what you would find useful! Have you had trouble figuring out why the mounting bracket wouldn't install properly? Is an AP getting too hot because it's too close to the ceiling? Let us know what you'd like to see in video form!
If you've had no problem whatsoever, what do you think would be most useful for someone just getting into Omada products?
Hey r/Omada_Networks, Neil here with the Omada team. I’ve got a few very exciting announcements to share with you all, so strap in!
First, the moment you’ve been clamoring for since its announcement at ISC West 2026: the first Fusion Gateway model is slated for US release next month, on July 20.
Meet the Fusion 2.5G, a gateway with a built-in controller that delivers full 2.5G throughput. Boasting a touchscreen for instant diagnostics, simplified setup over Bluetooth, and seamless site-to-site connectivity with full mesh SD-WAN, the Fusion Gateway is a great fit for prosumers and SMBs alike.
Check out the Fusion 2.5G product page for more info!
Can’t wait a whole month? Apply for the Omada Fusion Gateway Pioneer Program!
Accepting applications until June 30.
Selected Pioneers will get the following benefits:
In return, Pioneers are expected to deploy, test, and share their experience with the Omada team. We’re looking for experienced, enthusiastic users who are eager to help shape the future of Omada.
Think you’re a good fit? Sign up on the landing page!
Using New Reddit (Desktop) and mobile, usernames don't show up on notifications when a user replies to your post. The problem is that it's inconsistent, so I can't really track a pattern, and I use usernames to quickly check at a glance what post is being talked about. Is there any explanation for it, or is my reddit just being buggy?
One of the struggles you may face when designing a network is how to actually keep it up and running consistently. PoE offers a few solutions to help you achieve that goal.
---
Many switch vendors have built-in auto-recovery features to help devices come back online after a power failure, even without user intervention. A switch with auto-recovery will continuously monitor whether a powered device (PD) is transferring and receiving data. If the PD stops sending data to the switch for a specified period, the switch will restart the power on that port.
Omada PoE switches use IntelliRecover to improve on basic auto-recovery features. IntelliRecover is configured via the Omada Controller, which allows management of devices and clients from a single interface. The Omada Controller also maintains event logs and status tracking for network switches, providing visibility into recovery history. You can also configure the number of times a switch will attempt to restart the power on its ports. A switch configured with IntelliRecover will send an alert once the recovery attempt limit is reached, rather than rebooting over and over.
Learn how to configure IntelliRecover on our FAQ here.
Fast PoE is a feature that can help a network get back online sooner. When a switch with Fast PoE restarts, like after an update or power blip, it’ll send power to its PoE-enabled ports without waiting for the switch’s OS to boot. This way, devices turn on faster, which means less downtime. Great for getting the Wi-Fi back up and running without having to check each access point manually.
Like Fast PoE, Perpetual or Continuous PoE is a hardware feature of switches designed to improve a network’s uptime. This feature keeps PoE ports with powered devices on even during a switch reboot. Even if someone decides to update a switch during production hours, critical devices like IP cameras and access control systems will stay on the whole time.
One thing to note is that Fast PoE and Perpetual PoE are both hardware features of switches, not software. These features can’t magically be added to a switch by a firmware update. This also means these features come built-in to switches that have it, no configuration required.
These features help immensely when it comes to network uptime, but nothing can replace proper network planning. An uninterruptible power supply (UPS) is a staple of every serious network for its ability to keep networks running during short outages. This means switches stay on even if the outage lasts for 5 to 10 minutes, and network devices will stay powered during this period with PoE. Add in injectors and splitters, and you can pass the benefits of a UPS onto a wide range of network devices.
PoE, by definition, reduces the amount of cabling in your network by combining data and power cables into one. What this means is if something goes down, there’s only one cable to troubleshoot rather than two, and only one to replace if it's faulty. The Ethernet standard also means cable replacements are far easier to come by; there’s no hunting down proprietary power adapters or waiting weeks for a replacement under warranty.
---
TL;DR: PoE features like auto-recovery, Fast PoE, and Perpetual PoE reduce downtime by restoring or maintaining power to connected devices. Always consider physical network reliability measures, such as UPSes, to make your network more resilient.
Want to make sure you have enough power on your switches for your network? Take a look at our PoE Standards Cheat Sheet here.
Our article series, Omada Client Solutions, released its 6th article on Friday. This series is meant to provide real-world scenarios that offer some insights into use cases and the troubleshooting process.
This month's article covers features of Omada hardware in realistic use cases, such as using PPSK for parental controls. Give it a read and let us know what Omada features you would like to see covered in the future!
Following up on the PoE Cheat Sheet from earlier this week, a few people asked about accessories. We figured it was worth a separate post since the choice between injector, splitter, and extender can genuinely confuse some people, and getting it wrong usually means buying the wrong thing twice.
TL;DR: Injectors add PoE to a non-PoE switch port. Splitters do the opposite — they take a PoE input and break it into separate power and data for a device that doesn’t speak PoE. Extenders push PoE past the 100m Ethernet limit. None of them are magic; each has a real reason to exist as well as a reason not to reach for it.
---
PoE Injectors (sometimes called PoE adapters)
These let you add PoE to a regular non-PoE switch or router port. The injector plugs into a wall outlet and combines power and data over a single Ethernet cable to your powered device.
Practical case: You have a single outdoor AP or a single camera, and your existing switch is non-PoE. Replacing the entire switch for a single device is silly; adding an injector solves the problem cleanly.
When not to use one: If you’re adding more than a couple of PoE devices, you’ll spend more on injectors and outlet space than just getting a small PoE switch. Not to mention, you’ll clutter the deployment in the process.
PoE Splitter
These have the opposite job as injectors. A splitter takes a PoE input and breaks it into separate power and data outputs. This lets you power devices that don’t natively support PoE, like POS terminals, Raspberry Pis, and certain older IP devices. Many splitters let you set the output voltage (commonly 5V / 9V / 12V), and some come with USB-C or barrel connector tips.
When not to use one: If the device you’re powering has its own perfectly fine wall adapter and lives next to an outlet, the splitter solves a problem you don’t have.
PoE Extender
Ethernet has a recommended max run of 100m, and PoE inherits that limit. An extender repeats both data and power over Ethernet, so you can deploy a powered device further out. A typical use case would be an outdoor camera or AP at the far edge of a building or lot.
The catch: you can’t daisy-chain extenders forever. Every meter of cable causes a slight voltage drop, and each extender consumes a small amount of power to run. If too many are linked together, the powered device may not get enough juice to stay stable. As a rough rule, usually 1-3 extenders in series is the maximum for a device, depending on your PoE budget and cable quality. Always verify the minimum power required for a powered device.
When not to use one: When possible, a fiber run to a remote switch and a PoE injector closer to the powered device's deployment location will be more reliable than a long daisy-chained extender run.
---
Quick Decision Frame
If you find yourself having trouble choosing, ask yourself these questions in order:
Check out the Community Knowledgebase for a deeper dive into PoE.
Ever wonder why your PoE switch never delivers the wattage listed on the spec sheet? This reference guide will hopefully answer that question while also providing some key information about other aspects of PoE.
Let’s take a look at this table of measured output vs what’s advertised for PoE.
(what you see vs. what you get)
| Standard | Max per Port (PSE) | Realistic Output (PD) |
|---|---|---|
| 802.3af (PoE) | 15.4 W | 12.95 W |
| 802.3at (PoE+) | 30 W | 25.5 W |
| 802.3bt T3 (PoE++) | 60 W | 51 W |
| 802.3bt T4 (PoE++) | 90 W | 71.3 W |
Key Terms:
Why is the realistic output significantly less than what's advertised? The answer is that some power dissipates as heat in the cable. The amount of loss depends on the length and quality of the cable. To avoid this, when managing the PoE budget for your networks, it's best to leave a 10-15% margin for powering your devices.
Be sure to also check the cabling on your network. Copper Clad Aluminum (CCA) cables are not recommended for PoE usage due to aluminum's higher resistance and the cable's heat buildup (and in some countries, goes against fire safety codes). Cat5e cabling is fine for PoE usage, but for PoE+ and higher, Cat6 is preferred due to its thicker wiring. Thicker wiring means lower heat generation and less performance degradation.
---
Here's an example.
Let's say you have a 24-port PoE switch with a total budget of 250W. You also have a set of APs that use the 802.3at PoE standard. If all APs are running at maximum performance, you can, on paper, power up to 8 APs.
250 W / 30 W ≈ 8 APs
However, with a 10-15% margin, you can only reliably power up to 7.
250 W * 0.9 = 225 W
225 W / 30 W ≈ 7 APs
Even if all ports support PoE, the margins and power draw you can afford will depend on your network environment.
---
For PSEs, consider whether they support Active or Passive PoE. PSEs that support Active PoE perform a “handshake” with connected devices to verify if they need power and ensure safe and efficient power delivery. PSEs that support Passive PoE are “always on” and send electricity regardless of what is plugged into it, which risks permanent hardware failure or device burnout if the PD cannot support the power level.
---
The “max wattage” on spec sheets isn’t what devices actually get because some power is lost as heat in the cable. Best practice is to leave about 10–15% leeway. Don’t use CCA cable for PoE; Cat5e or better is necessary for PoE applications.
What other topics would you like to see covered? Let us know in the comments below!
Want to learn more about PoE? Check out the Community's Knowledgebase article here.
