LANCOM SYSTEMS LCOS LX 7.12 Addendum LX Devices
Specifications
- Product Name: LCOS LX 7.12
- Version: 7.12
- Release Date: 10/2025
Product Usage Instructions
mDNS Filter Configuration
The mDNS filter feature allows you to control which mDNS-based services are permitted for forwarding over the WLAN network.
Configuring mDNS Services
- Access the Setup menu on the device.
- Navigate to the mDNS-Filter section.
- Add services to the whitelist based on the mDNS Services table.
- Specify the Network-Name and select the desired services to be forwarded.
Service List Configuration
The Services list operates as a whitelist, allowing only the specified mDNS services for forwarding over the WLAN. If the list is empty, all services are permitted.
Setup Menu Additions
The Setup menu includes additional options related to mDNS filter configuration:
mDNS-Filter
The mDNS-Filter option allows you to manage Multicast DNS services for service discovery in the network. It enables selective forwarding of mDNS requests over WLAN while optimizing airtime usage.
Copyright
- © 2025 LANCOM Systems GmbH, Würselen (Germany). All rights reserved.
- While the information in this manual has been compiled with great care, it may not be deemed an assurance of product characteristics. LANCOM Systems shall be liable only to the degree specified in the terms of sale and delivery.
- The reproduction and distribution of the documentation and software supplied with this product and the use of its contents is subject to written authorization from LANCOM Systems. We reserve the right to make any alterations that arise as the result of technical development.
- Windows® and Microsoft® are registered trademarks of Microsoft, Corp.
- LANCOM, LANCOM Systems, LCOS, LANcommunity, LANCOM Service LANcare, LANCOM Active Radio Control, and AirLancer are registered trademarks. All other names or descriptions used may be trademarks or registered trademarks of their owners. This document contains statements relating to future products and their attributes. LANCOM Systems reserves the right to change these without notice. No liability for technical errors and/or omissions.
- This product contains separate open-source software components. These are subject to their own licenses, in particular the General Public License (GPL). License information relating to the device firmware (LCOS LX) is available on the CLI by using the command show 3rd-party-licenses. If the respective license demands, the source files for the corresponding software components will be made available on request. Please contact us via e-mail under gpl@lancom.de.
- Products from LANCOM Systems include software developed by the “OpenSSL Project” for use in the “OpenSSL Toolkit” (www.openssl.org).
- Products from include cryptographic software written by Eric Young (eay@cryptsoft.com).
- Products from LANCOM Systems include software developed by the NetBSD Foundation, Inc. and its contributors.
- Products from LANCOM Systems contain the LZMA SDK developed by Igor Pavlov.
- LANCOM Systems GmbH
- A Rohde & Schwarz Company Adenauerstr. 20/B2 52146 Würselen, Germany Germany
- www.lancom-systems.com
Addendum to LCOS LX version 7.12
- This document describes the changes and enhancements in LCOS LX version 7.12 since the previous version.
2 mDNS filter
- mDNS (Multicast DNS) is used for simple service discovery in the (W)LAN. Prominent applications based on this are Bonjour / AirPlay and Google Cast.
- Since mDNS requests are sent as multicast, transmission at the WLAN level must use the lowest permitted data rate, which can consume significant airtime depending on the volume of mDNS requests. With the mDNS filter, requests to definable mDNS services can be selectively allowed for forwarding over the WLAN.
- Configure the mDNS filter under Wireless LAN > WLAN Networks > mDNS filter.
mDNS Services contains the most common mDNS-based services by default, but it can also be manually extended.
- Name
- The name of a service.
- Service-Type
- The type of this service.
- Comment
- Comment for this entry.
In the Services list, configure filters based on the services from the mDNS Services table.
4 The Services list works as a whitelist: If the list is not populated, all mDNS services are allowed. If the list contains entries, only the permitted services are allowed. All other services are filtered.
Network-Name
Here you can configure the WLAN network name for which the filter should apply.
Services Here you can add one or more of the mDNS-based services defined in the Services table for which requests should be forwarded.
Additions to the Setup menu
mDNS-Filter
- mDNS (Multicast DNS) is used for simple service discovery in the (W)LAN. Prominent applications based on this are Bonjour / AirPlay and Google Cast.
- Since mDNS requests are sent as multicast, transmission at the WLAN level must use the lowest permitted data rate, which can consume significant airtime depending on the volume of mDNS requests. With the mDNS filter, requests to definable mDNS services can be selectively allowed for forwarding over the WLAN.
SNMP ID:
- 2.46
Console path: Setup
Services
The Services table contains the most common mDNS-based services by default, but it can also be manually extended.
SNMP ID: 2.46.1
Console path: Setup > mDNS-Filter
Name The name of a service.
- SNMP ID: 2.46.1.1
Console path: Setup > mDNS-Filter > Services
Possible values:
- Max. 32 characters from
- 2.1.1.1.2 Service-Type The type of this service.
- SNMP ID: 2.46.1.2
- Console path:
- Setup > mDNS-Filter > Services
- Possible values:
- Max. 128 characters from
- Max. 128 characters from
- 2.1.1.1.3 Comment Comment for this entry.
- SNMP ID: 2.46.1.3
- Console path:
- Setup > mDNS-Filter > Services
- Possible values:
- Max. 128 characters from
- Max. 128 characters from
2.1.1.2 Services-List
Configure filters here based on the services from the Services table.
The Services list works as a whitelist: If the list is not populated, all mDNS services are allowed. If the list contains entries, only the permitted services are allowed. All other services are filtered.
SNMP ID: 2.46.2
Console path: Setup > mDNS-Filter
Network-Name
Here you can configure the WLAN network name for which the filter should apply.
SNMP ID: 2.46.2.1
Console path:
Setup > mDNS-Filter > Services-List
Possible values: Max. 64 characters from 
Services
Here you can add one or more of the mDNS-based services defined in the Services table for which requests should be forwarded.
SNMP ID: 2.46.2.2
Console path:
Setup > mDNS-Filter > Services-List
Possible values: Max. 255 characters from 
Cloud-managed Hotspot: Walled Garden
Walled Garden allows you to define IP addresses or hostnames that should be reachable for hotspot clients who are not yet logged in. Typically, these are hosts that provide additional resources required by the landing page (e.g., graphics, fonts, or even entire third-party login services).
Full integration of the Walled Garden configuration into the LANCOM Management Cloud hotspot configuration is planned.
Additions to the Setup menu
Walled-Garden
Walled Garden allows you to define IP addresses or hostnames that should be reachable for hotspot clients who are not yet logged in. Typically, these are hosts that provide additional resources required by the landing page (e.g., graphics, fonts, or even entire third-party login services).
To configure the Walled Garden, proceed as follows:
- Create a Cloud-managed Hotspot in the LANCOM Management Cloud.
- Next, determine the name of this Cloud-managed Hotspot from the table under Setup > WLAN > Hotspot > Hotspots.
- Now create one or more entries in this table, with “Hotspot” containing the name of the hotspot configuration and “Hostname” containing the host or IP address to be allowed. The use of wildcards such as “*.lancom.de” is possible.
- If a Walled Garden host should only be accessible without login when the LANCOM Management Cloud is not reachable, then for each entry the switch “LMC-unreachable-only” can additionally be set.
- Finally, save the configuration using the command “flash”.
DNS requests from unauthenticated clients in the hotspot network are analyzed, and the resolved IP addresses are cached in the background to support the use of wildcards.
To simplify the process, it is recommended to perform these configuration steps in the LANCOM Management Cloud using an add-in.
SNMP ID: 2.20.12.2
Console path: Setup > WLAN > Hotspot
Hotspot
Name of the hotspot.
SNMP ID: 2.20.12.2.1
Console path:
Setup > WLAN > Hotspot > Walled-Garden
Possible values: Max. 32 characters from
Hostname
Enter here the host to be enabled or its IP address. The use of wildcards such as “*.lancom.de” is possible.
SNMP ID: 2.20.12.2.2
Console path:
Setup > WLAN > Hotspot > Walled-Garden
Possible values: Max. 255 characters from 
LMC-unreachable-only
If a Walled Garden host should only be accessible without login when the LANCOM Management Cloud is not reachable, this switch can additionally be set to “Yes”.
SNMP ID: 2.20.12.2.3
Console path:
Setup > WLAN > Hotspot > Walled-Garden
Possible values:
- No
- Yes
Cloud-managed Hotspot: Make local RFC1918 networks accessible
- In networks operated as a Cloud-managed Hotspot, traffic to RFC1918 networks is generally prohibited. This affects the following networks:
- 10.0.0.0/8
- 192.168.0.0/16
- 172.16.0.0/12
- With this feature, traffic to these networks or to individual hosts can be selectively allowed.
An add-in is required in the LANCOM Management Cloud.
The configuration is only possible via the CLI.
Additions to the Setup menu
Allowed-Targets
- In networks operated as a Cloud-managed Hotspot, traffic to RFC1918 networks is generally prohibited. This affects the following networks:
- 10.0.0.0/8
- 192.168.0.0/16
- 172.16.0.0/12
- With this feature, traffic to these networks or to individual hosts can be selectively allowed.
An add-in is required in the LANCOM Management Cloud.
SNMP ID: 2.20.12.3
Console path: Setup > WLAN > Hotspot
Hotspot
Name of the hotspot.
SNMP ID: 2.20.12.3.1
Console path:
Setup > WLAN > Hotspot > Allowed-Targets
Possible values: Max. 32 characters from 
IP-Network
Allowed IPv4 network for this hotspot.
SNMP ID: 2.20.12.3.1
Console path:
Setup > WLAN > Hotspot > Allowed-Targets
Possible values: Max. 19 characters from 
DHCP: Add Circuit ID (Option 82) and Remote ID
- The access point can add the Circuit ID and/or Remote ID to relayed DHCP packets. The DHCP server can make decisions based on this information, such as assigning specific IP addresses.
- LANconfig: Interfaces > DHCP Snooping
Port Here you can configure the WLAN network name or a LAN port (depending on the device model ETHx or LANx) on which DHCP requests should be supplemented.
Circuit-ID The Circuit ID can be configured here using these placeholders:
- %i: Inserts the name of the interface where the relay agent received the DHCP request.
- %n: Inserts the name of the DHCP relay agent as specified under Setup > Name.
- %s: Inserts the WLAN SSID if the DHCP packet originates from a WLAN client. For other clients, this variable contains an empty string.
- %r: Inserts the system-wide MAC address.
- %%: Inserts a percent sign.
Remote-ID
Here you can configure the Remote ID using these placeholders:
- %i: Inserts the name of the interface through which the relay agent received the DHCP request.
- %n: Inserts the name of the DHCP relay agent as specified under Setup > Name.
- %s: Inserts the WLAN SSID if the DHCP packet originates from a WLAN client. For other clients, this variable contains an empty string.
- %r: Inserts the system-wide MAC address.
- %%: Inserts a percent sign.
Additions to the Setup menu
Bridge
SNMP ID: 2.45
Console path: Setup
DHCP-Snooping
The access point can add the Circuit ID and/or Remote ID to relayed DHCP packets. The DHCP server can make decisions based on this information, such as assigning specific IP addresses.
SNMP ID: 2.45.1
Console path: Setup > Bridge
Port
Here you can configure the WLAN network name or a LAN port (depending on the device model ETHx or LANx) on which DHCP requests should be supplemented.
The identifiers of the LAN ports can be viewed in the CLI table Status > LAN > Ports.
SNMP ID: 2.45.1.1
Console path:
Setup > Bridge > DHCP-Snooping
Possible values: Max. 64 characters from 
Circuit-ID
The Circuit ID can be configured here using these placeholders:
- %i: Inserts the name of the interface where the relay agent received the DHCP request. a %n: Inserts the name of the DHCP relay agent as specified under Setup > Name.
- %s: Inserts the WLAN SSID if the DHCP packet originates from a WLAN client. For other clients, this variable contains an empty string.
- %r: Inserts the system-wide MAC address.
- %%: Inserts a percent sign.
SNMP ID: 2.45.1.2
Console path:
Setup > Bridge > DHCP-Snooping
Possible values:
Max. 64 characters from 
Remote-ID
Here you can configure the Remote ID using these placeholders:
- %i: Inserts the name of the interface through which the relay agent received the DHCP request.
- %n: Inserts the name of the DHCP relay agent as specified under Setup > Name.
- %s: Inserts the WLAN SSID if the DHCP packet originates from a WLAN client. For other clients, this variable contains an empty string.
- %r: Inserts the system-wide MAC address.
- %%: Inserts a percent sign.
SNMP ID: 2.45.1.3
Console path:
Setup > Bridge > DHCP-Snooping
Possible values:Max. 64 characters from 
Factory default active services according to EN 18031 GEC-4
In LCOS LX 7.12, the following network services are active in the factory default state:
| Service | Function | Port |
| SSH | Device management | TCP 22 |
| HTTPS | Device management | TCP 443 |
| LL2M | Device management | Layer 2 |
| WTP | WLAN controller connection | UDP 1027 |
| LMC | Connection to LANCOM Management Cloud | TCP 443 |
| TFTP | Device search with LANconfig | UDP 69 |
FAQs
Q: What is the purpose of the mDNS filter?
A: The mDNS filter controls the forwarding of specific mDNS-based services over the WLAN network, helping to manage airtime usage efficiently.
Q: How can I configure the mDNS filter for my network?
A: To configure the mDNS filter, access the Setup menu, navigate to the mDNS-Filter section, add desired services to the whitelist, and specify the network name for filtering.
Documents / Resources
 |
LANCOM SYSTEMS LCOS LX 7.12 Addendum LX Devices [pdf] User Guide LCOS LX 7.12, LCOS LX 7.12 Addendum LX Devices, Addendum LX Devices, LX Devices |