More flexibility in WLAN management
With LCOS LX 5.36 you get new features and improvements for your LX-based access points. For example, the LANCOM Layer 2 Management (LL2M) functions save the use of time-consuming on-site operations by activating and configuring unreachable devices via other LANCOM devices in the network.
Find out more about LCOS LX here.
Feature Highlights LCOS LX 5.36
LANCOM Layer 2 Management (LL2M)
Whenever a device in the network can no longer be reached and does not respond even via the LANCOM Management Cloud or LANconfig, LANCOM Layer 2 Management is the ideal solution to avoid the time-consuming on-site operations of technicians (e.g. for ceiling-mounted access points). To enable configuration access to a device without an IP connection, the LANCOM Layer 2 Management protocol (LL2M) is used. This integrates a client-server structure so that the inaccessible access point can be found, activated, and configured via another LANCOM device in the network.
With Proxy ARP (Address Resolution Protocol), the access point assumes responsibility for forwarding data packets to the receiving end device. In this way, the access point intercepts ARP requests for the WLAN client and answers them on its behalf. The advantage here: Valuable airtime is saved, because ARP requests do not place an unnecessary load on the wireless network. The end device can remain in power-saving mode until the data is forwarded to it.
Untagged VLAN for Ethernet port
Untagged VLAN gives you more flexibility by allowing you to connect an additional network client to all LX-based access points with two Ethernet ports. You determine the VLAN to be used as untagged VLAN for the port according to your requirements and use the function e.g. to integrate TVs, cash registers or also wired customer devices in the hotel.
LCOS LX improvements 5.36
- LL2M protocol support
- Support for proxy ARP / ARP handling in wireless LAN
- Untagged VLAN/access port configuration of additional Ethernet ports on
- Delayed reboot
- Opportunistic Key Caching (OKC).
Bugfixes / Improvements
- A vulnerability in the zlib library has been fixed (CVE-2018-25032).
- A vulnerability in the OpenSSL library has been fixed (CVE-2022-0778).
- When an access point tried to connect to a LANCOM WLAN controller operating in a remote network, the connection could sporadically fail because the WLAN controller rejected the connection request due to a parameter in the DTLS protocol used that was unknown to the LCOS.
- When a LANCOM WLAN controller tried to enable the ‘Multicast-to-Unicast’ function on a managed LANCOM LW-500, this failed because the LANCOM LW-500 did not use the correct Multicast protocol.
- When using the Fast Roaming function, access points could sporadically restart without warning due to a memory leak.
- An access point has different MAC addresses for the two Wi-Fi interfaces. In a WLAN controller scenario, the access points each reported the MAC address of a different Wi-Fi interface (WTP MAC) to the WLAN controller when adding and deleting Wi-Fi end devices, so that these did not match. This resulted in a discrepancy between the Wi-Fi end devices registered in the station table on
the WLAN controller and the access points.
- When trying to connect via LL2M with specification of the correct interface, it could happen that the specification of the interface was not recognized and the options available for LL2M were output instead. The connection setup via LL2M failed as a result.
- If only one change was made to the netmask in the IP parameter profile in the LANCOM WLAN controller, the WLC transferred this change to the access point. The access point did not accept the change due to a missing comparison function (actual state/setpoint state) and continued to use the old netmask.
- Sporadic packet loss could occur within a WLC tunnel
Release Notes LCOS LX 5.36
Comparison LCOS & LCOS LX
Reference Manual LCOS LX 5.36