Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • NetworkManager NetworkManager
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NetworkManagerNetworkManager
  • NetworkManagerNetworkManager
  • Issues
  • #13
Closed
Open
Issue created Aug 20, 2018 by Gima@Gima

RFE: Add `connection.llmnr` to set systemd-resolved's link-specific LLMNR value

Request For Enhancement:

Add setting to control systemd-resolved's LLMNR interface-specific value.

Systemd-resolved provides setting for two similar protocols (LLMNR and MDNS). Feature to control MDNS was added to NetworkManager in commit c03a5349 under the name connection.mdns.

Going by that, the new setting for LLMNR could be connection.llmnr = string ("yes"/"no"/"resolve").


LLMNR: Protocol to resolve local network hostnames via multicast UDP
MDNS: Protocol to resolve local network hostnames under ".local" domain via multicast UDP

Edit: Had mixed up the definition of LLMNR and MDNS. Now corrected.

Edited Aug 31, 2018 by Gima
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking