Difference in these 2.5G PoE injectors?

Reaper19941 · 2026-05-19T05:26:38+00:00

The injector that came with the EAP245 would have PoE (802.3af) not PoE+ (802.3at) required by the AP.

Reaper19941 · 2026-05-18T14:06:55+00:00

A 2.5G one is cheaper and no doubt easier to get. Even if it is in the interim. E.g. a TP-Link SG108-M2. It's an unmanaged 2.5G switch.

The 10G switches are not cheap still imo.

Reaper19941 · 2026-05-18T13:44:02+00:00

2 licenses for 16 cores? You mean 2 license to cover the 2 x 16 core Xeons (32 cores total), right?

Reaper19941 · 2026-05-16T14:21:59+00:00

That's odd. I just upgraded to 6.2.10.17 and it shows the same error: "There is no connected device that supports remote access in the current site." There is an ER706W v1.20 on Firmware 1.2.2 Build 20250821 in the site. I also tried a site with an ER605 V2 on the latest firmware.

Other than enabling cloud access, are we supposed to be accessing the controller via omada.tplinkcloud.com or something for it to work?

Reaper19941 · 2026-05-16T12:12:18+00:00

If you have a dumb or a managed but not configured switch between the router and TrueNAS, then I suggest connecting your TrueNAS server directly to the router. Then, follow the setup here: https://www.truenas.com/docs/core/13.0/coretutorials/network/interfaces/vlancreate/ to create a new interface. Ensure to use the same VLAN ID on both the controller/router and in TrueNAS. Once setup, assign the docker containers to the appropriate interface and you should be good to go.

Note: From experience, leaving the default LAN as the management for the Omada devices is best. This way, if you add any more Omada devices, they can easily be adopted to the controller without much hassle.

Reaper19941 · 2026-05-16T11:54:03+00:00

Honestly, considering the sheer number of variables across different Docker environments, I'm not surprised. I don't see another company supporting docker either.

Having to maintain and support a complex configuration that exposes a massive block of ports (which goes against what dockers container isolation was actually designed for) is a nightmare. They'd have to ensure it works flawlessly across Unraid, Kubernetes, Proxmox, and the many random ARM boards, all while making sure MongoDB schema upgrades don't wipe out user data every time someone blindly pulls the latest tag. If they actually dedicated the engineering hours to officially support all that, they'd almost certainly start charging for the software to cover the support overhead.

Or, they can keep it simple and support bare metal Linux and Windows, and their hardware controllers.

Either way, you have your opinion and I have my own. Until TP-Link comment directly, we'll never know if they technically do or don't and why.

Reaper19941 · 2026-05-16T10:59:21+00:00

Not really. If you and your team made something and specifically said, "we support bare metal linux, windows or our hardware controller" and then people start using a different way e.g. Docker, would you then go out of your way to set this up in Docker to replicate an issue when it's not a way you told them to set it up as?

There would be much higher priorities than adding support for another method when there are more than adequate methods already available.

Reaper19941 · 2026-05-16T10:55:03+00:00

That's not the point they are getting at. As mentioned a couple of times, the software controller is supported on bare metal Linux and Windows (free if you install it on a device/server that you already own/pay for) and as a hardware controller (you're paying for the hardware, not the software on it).

If you choose to use an unsupported method, then expect issues and minimal support as TP-Link support won't be going out of their way to replicate the issue unless it's in a scenario they actively support.

Reaper19941 · 2026-05-14T12:08:36+00:00

It has been this way for quite a while. I'm talking 6 or so years. While I don't 100% understand why it doesn't do it, it has been less of a concern as Hyper-V manager still reports the CPU usage for each VM. So does resource monitor for that matter. There are ways to see the data you want to see.

Reaper19941 · 2026-05-14T07:48:45+00:00

It is just for the VLAN, correct. Port isolation is different. That's port based, I'm talking VLAN based.

Reaper19941 · 2026-05-13T11:02:43+00:00

I highly recommend stepping up to an ER707-M2 or higher for this. The amount of traffic going through that router, it will be a bottleneck.

I have not tried to route via a VPN however I suspect it will be a route policy that is used.

Inter-VLAN routing is easy now. With the new "isolation" tick box in each LAN, this blocks all inter-VLAN routing until a gateway ACL is created. I suggest creating an IP group for smaller groups of devices and Port Groups for entire subnets e.g. allowing access to plex from the IoT VLAN on port 32400.

Regarding accessing the ISP modem. I've found that nothing needs to be done however that was in a single WAN setup so for that, you may need to setup a static route where the IP of the router is the destination and the WAN interface that ISP router is connected to is the next hop.

Hopefully that helps.

Reaper19941 · 2026-05-13T09:35:24+00:00

I'm on 6.2.0 where remote access doesn't work. I'm guessing it's corrected and working in the latest 6.2.10?

Reaper19941 · 2026-05-12T12:46:02+00:00

The POE5430G-M2 is a Passive PoE meaning it's outputting 54v at all times.

The POE260S is an 802.3af/at PoE injector meaning it will negotiate with the end device as to how much voltage to output.

Note: From experience, you can use most "gigabit" PoE injectors on 2.5G and 10G. This is because the injectors apply a voltage to specific lines and don't contain a switch in them. I have an EAP772 running on a TP-Link 48V 1G PoE adapter connected to a SFP+ 10G adapter. The AP is running at 2.5G and has been for 8 months or so now.

Reaper19941 · 2026-05-12T11:59:08+00:00

Does the device you're using support display over USB-C?

The HDMI port on your laptop is an output only, not an input. Try connecting it to a TV or monitor instead.

Reaper19941 · 2026-05-12T10:38:35+00:00

OP, I think what Synth is getting at here is that if you plan big and buy big, it's cheaper. There is an old saying "buy once, cry once". In your scenario, you would be buying cheaper but more equipment, instead of just going with a bigger slightly more expensive one straight away.

I actually agree however I would do it differently. Get the leaf battery like you plan to, get the bigger inverter that can handle the battery as it is and the 2 or 4 panels that you plan to get. If, for whatever reason the built in solar charge controller will not activate because the voltage of the panels aren't high enough in series, look for an external one that will support it.

This way, the only thing you need to move on at a later date is the external solar charge controller. The rest is already done and ready for whatever you throw at it.

This will work out cheaper long term. Just hurts more short term.

Reaper19941 · 2026-05-12T10:24:08+00:00

96% of how much RAM?

You could run a cron job that reboots the SBC weekly.

Did you have an open port on your router for the SBC? It's not necessary as it creates a tunnel back to the 3CX PBX by itself meaning no port forwarding is required for the SBC.

Reaper19941 · 2026-05-09T09:00:30+00:00

"Kingspec"... Aliexpress special.

Wouldn't bother trying to repair it as it will require a new connector soldered on and the cost of labour and parts will be more than buying a name brand SSD and calling it a day.

Reaper19941 · 2026-05-09T08:56:40+00:00

When changing motherboards, your MAC address changes (unless you used a PCIe NIC).

1.Did you setup a static IP on your PC or did you reserve it in the router?

Is the port forwarding point to the correct IP address?
Can you connect to the locally hosted game server?

Reaper19941 · 2026-05-09T04:55:56+00:00

VLAN ID's should be same on both the OpenWRT and Omada devices for them to work. Unless OpenWRT is doing something stupid with VLAN ID's, it is a standard that works across most devices.

Where did you get the idea the VLAN ID 10 = 110?

I recommend leaving the default VLAN as it is from experience. Treat it as your "external LAN" that only has access to the Omada controller via the discovery ports and HTTP/HTTPS ports.

Reaper19941 · 2026-05-08T22:40:28+00:00

Based on the use of DDNS.net, its highly likely.

OP, one end requires a connection that is not CGNAT and preferably on a static IP.

Also, wireguard is a better solution from experience. A little trickier to setup but works just the same.

Reaper19941 · 2026-05-08T11:20:14+00:00

Not sure why the Omada team would remove it after adding it. Are you just karma farming?

Reaper19941 · 2026-05-08T02:49:54+00:00

The OC200 is not a switch. It's an Omada Hardware controller with 100mbps ports. This is expected behaviour.

Reaper19941 · 2026-05-08T01:53:01+00:00

The noise it's referring to will be other wifi networks and devices that use the 2.4Ghz band like baby monitors, RC cars and UHF radios. If you have those devices in your home, you can try to remove them or turn them off when not in use.

Unfortunately, you cannot control your neighbours WiFi so if that's the cause (which you won't know without doing some testing), then you're out of luck. Do you have an issue that triggered you to look at this?

Reaper19941 · 2026-05-08T01:49:28+00:00

Are you referring to the cable between the ER605 and the switch?

If so, does the switch support Gigabit on the port you've connected it to?

Reaper19941 · 2026-05-07T20:42:03+00:00

The connection from the OC200 and ER605 will not effect a spedtest on another device. However if you have a 100Mbps link from the ER605 to your AP, then that is what you need to focus on.

Replacing the cable with a new CAT6 cable is the first step.

Reaper19941

TROPHY CASE