Product code: L11UG-5HaxD
CPU Dual-Core IPQ-5010 800 MHz
CPU architecture ARM
Size of RAM 256 MB
Storage 128 MB, NAND
Number of 1G Ethernet ports 1
USB port 1 USB 2.0 port type A
Wireless band 5 GHz
Wireless interface model QCN-6102
Wireless 802.11a/n/ac/ax dual chain
Dimensions 107 x 114 x 27 mm
Operating system RouterOS v7, License level 4
Operating temperature -40°C to +70°C
https://www.youtube.com/watch?v=ycaWP5hOax0

ap or cpe? NV2 or 802.11?

Will part of the 6ghz available, if yes does it allow us to add a gps?

I'd imagine it be similar to the hAPaxLite, except with 5Ghz Wi-Fi. I doubt it has 6Ghz, but you'd have to ask Mikrotik.

I just wish it had an M.2 (or even miniPCIe) and SIM slot. That get GPS (and LTE/etc). But looks like it only has headers for slot, not an actually slot. Too bad.

L11UG-5HaxD
5 = 5GHz
H = Hight Power
ax =WiFi6
D = Dual Chain
G = Gigabit
L = Light
1 = series
1 = Port count
U = USB
= NO 6GHz

Dream = L11UG-6HaxD

Product code: L11UG-5HaxD
CPU Dual-Core IPQ-5010 800 MHz
CPU architecture ARM
Size of RAM 256 MB
Storage 128 MB, NAND
Number of 1G Ethernet ports 1
USB port 1 USB 2.0 port type A
Wireless band 5 GHz
Wireless interface model QCN-6102
Wireless 802.11a/n/ac/ax dual chain
Dimensions 107 x 114 x 27 mm
Operating system RouterOS v7, License level 4
Operating temperature -40°C to +70°C
https://www.youtube.com/watch?v=ycaWP5hOax0

Without nstreme or nv2 support this is unuseable for outdoor WISP operation.

Dream = L11UG-6HaxD

Dreaming about device without 5GHz radio? I rather think you're dreaming about L12UG-5HaxD6axD

Without nstreme or nv2 support this is unuseable for outdoor WISP operation.

Why.
There will never be these protocols in Wifi 6.
Wifi 5 wave 2 is already superior to nv2 in some respects.

Dreaming about device ...5HaxD6axD

Why dream so faintly?
7HbeQ, 7HbeO

Turns out there's a lot of new products coming from Mikrotik.

Turns out there's a lot of new products coming from Mikrotik.

Meh. Nothing with 6GHz radio ... or 7GHz 4x4MIMO radio

So it's the same board in two versions (full and crippled), each in two different housings (if no case counts as one ).
And a sub-variant (again in full and crippled versions) in a yet another housing.

I wish at least the station-bridge mode was compatible over-the-air with older a/n/ac devices...
Network upgrades may take a lot of hard work and time, during which there is a mix of older and newer devices.
It's also useful to be able to mix in case some device fails and is difficult to replace immediately, but you have another one available.

I could make good use of these units. I have a pile of mimosa C6x that I've been considering selling off, but they happily connect to a hap ax3 so I expect the L22 units to be great pop-in replacements.

https://www.youtube.com/watch?v=JSoModWAPIw
https://www.youtube.com/watch?v=7MNdlO_msPY

Dreaming about device ...5HaxD6axD

Why dream so faintly?
7HbeQ, 7HbeO

Can we add the letter "R" in these dreams?

Why dream so faintly?
7HbeQ, 7HbeO

Can we add the letter "R" in these dreams?

Throw an "A" for a good measure

All these models probably have same board inside, that's easy way to upgrade products. But it's all good only for setting up outdoor APs for regular devices.
None of this would work in WISP scenario without bridge mode, TDMA, not even basic WDS. There could be some workarounds for that using tunnels but no advanced WIFI control and lack of TDMA will be far worse without any workaround to fix it as that's hardware limitation...

All these models probably have same board inside, that's easy way to upgrade products. But it's all good only for setting up outdoor APs for regular devices.
None of this would work in WISP scenario without bridge mode, TDMA, not even basic WDS. There could be some workarounds for that using tunnels but no advanced WIFI control and lack of TDMA will be far worse without any workaround to fix it as that's hardware limitation...

WiFi6 in non-mixed mode doesn't have hidden node problem in OFDMA so it fares far better outdoors. if you run mixed mode ie AC clients then you'll suffer hidden node. That's really all TDMA has ever done on mikrotik since there's not been GPS sync. It's not going to scale super well but for smaller <20 client APs I think it'll be a nice kit. for a 2x2 AP it should be good, 4x4+ APs run into some problems with the default MUMIMO groupings because it's more or less setup to have a small number of heavy stations.

I do really want to see a WDS and/or 802.11s for multiple reasons. I think that's coming though.

Also note that hapax2/3 suport station bridge so I'm not sure why you might think the L11/L22 units wouldn't...

This access point does not support MikroTik AC clients in Station Bridge mode; it only allows pseudo-bridge, which is not useful

Some help on how to use it with a bridge?

This access point does not support MikroTik AC clients in Station Bridge mode; it only allows pseudo-bridge, which is not useful

Some help on how to use it with a bridge?

where do you find this information? v7.13 supports station-bridge and I'm having no issues connecting ac clients up to a hap ax3 I'm using for testing.

where do you find this information? v7.13 supports station-bridge and I'm having no issues connecting ac clients up to a hap ax3 I'm using for testing.

Pretty sure he means MikroTik AC clients using the wireless package. They effectively only work in station-pseudobridge mode with APs running wifi-qcom package.

I get that but I think as of 7.13 that’s not the case anymore…

I get that but I think as of 7.13 that’s not the case anymore…

No everything is still like this and no changes are expected.
Old drivers and wifi-qcom are still not compatible.
In 7.14, the AX drivers learned how to station-pseudobridge

Some help on how to use it with a bridge?

There is still one crutch solution to lay additional EOIP.

I get that but I think as of 7.13 that’s not the case anymore…

Just tried it. Pair of SXTsq 5 ac, both running v7.13.5, one with wifi-qcom-ac package, the other with wireless package.
With the wifi-qcom-ac device using 'ap' mode and the wireless device using 'station-bridge' mode, no connection is established.
With the wireless device using 'ap bridge' or 'bridge' mode and wifi-qcom-ac device using 'station bridge', connection is established but bridging clearly doesn't work (no DHCP etc).

So no, bridging still doesn't work between old/new wireless packages.

So no, bridging still doesn't work between old/new wireless packages.

As the rumours go it'll stay this way ... i.e. no bridging between wifi and wireless drivers ... ever.

Easiest workaround: EOIP across wifi interfaces.

As the rumours go it'll stay this way ... i.e. no bridging between wifi and wireless drivers ... ever.

Which is completely unacceptable, as you have no way to upgrade/forklift your network to the next generation. If you have to swap everything anyways, better swap it with Ubiquiti or Cambium, at least the latter has a working TDD implementation and backwards compatibility with older generation devices.

Easiest workaround: EOIP across wifi interfaces.

That's great for a couple of devices, not when you have 1500 of them. Just managing all those tunnel is a disaster.

With the wifi-qcom-ac device using 'ap' mode and the wireless device using 'station-bridge' mode, no connection is established.

When communicating between old and new drivers, you should use the same settings as for devices from other vendors. That is, use the station-pseudobridge mode. In 7.14 this mode station-pseudobridge appears for wifi-qcom

When communicating between old and new drivers, you should use the same settings as for devices from other vendors. That is, use the station-pseudobridge mode. In 7.14 this mode station-pseudobridge appears for wifi-qcom

Except that breaks a whole bunch of other things (such as STP), is unstable and according to MikroTik's own wiki article, should be avoided whenever possible:

This mode is available for all protocols except nv2 and should be avoided when possible. The usage of this mode can only be justified if AP does not support better mode for L2 bridging (e.g. when non-RouterOS AP is used) or if only one end-user device must be connected to network by means of station device.