Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

global LLMNR=false/no ignored on per-link basis #24863

Closed
msoltyspl opened this issue Sep 29, 2022 · 1 comment · Fixed by #25325
Closed

global LLMNR=false/no ignored on per-link basis #24863

msoltyspl opened this issue Sep 29, 2022 · 1 comment · Fixed by #25325
Labels
bug 🐛 Programming errors, that need preferential fixing resolve

Comments

@msoltyspl
Copy link
Contributor

systemd version the issue has been seen with

systemd 251 (251.3-1~bpo11+1)

Used distribution

debian bullseye 11

Linux kernel version used

5.18.0-0.deb11.4-amd64

CPU architectures issue was seen on

x86_64

Component

systemd-resolved

Expected behaviour you didn't see

As per manual - the expected behavior as per resolved.conf manual is that LLMNR on a per-link basis should be enabled only if both per-link and global setting is enabled. But in practice per-link setting ignores global setting.

Unexpected behaviour you saw

Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (mv-vlan10)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (mv-vlan13)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 10.13.36.2
       DNS Servers: 10.13.36.2
        DNS Domain: touk.pl

Link 4 (mv-vlan17)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 5 (mv-vlan30)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 6 (mv-vlan31)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 7 (mv-vlan47)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 8 (mv-vlan250)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

LLMNR is enabled per-link despite being disabled globally, which conflicts with Note that systemd-networkd.service(8) also maintains per-link LLMNR settings. LLMNR will be enabled on a link only if the per-link and the global setting is on.

Steps to reproduce the problem

Disable LLMNR in resolved.conf, restart relevant services.

Additional program output to the terminal or log subsystem illustrating the issue

No response
@msoltyspl msoltyspl added the bug 🐛 Programming errors, that need preferential fixing label Sep 29, 2022
@Tachi107
Copy link
Contributor

Tachi107 commented Nov 4, 2022

See #25252 for an explanation why this happens

yuwata added a commit to yuwata/systemd that referenced this issue Nov 10, 2022
@yuwata
resolve: provide effective supporting levels of mDNS and LLMNR
1484162 
The per-link settings are ignored if the feature is disabled by the global setting.
Let's announce the effective level, to make not users confused.

Closes systemd#24863.
@yuwata yuwata mentioned this issue Nov 10, 2022
Merged
yuwata added a commit to yuwata/systemd that referenced this issue Nov 10, 2022
@yuwata
resolve: provide effective supporting levels of mDNS and LLMNR
dc16703 
The per-link settings are ignored if the feature is disabled by the global setting.
Let's announce the effective level, to make not users confused.

Closes systemd#24863.
d-hatayama pushed a commit to d-hatayama/systemd that referenced this issue Feb 15, 2023
@yuwata @d-hatayama
resolve: provide effective supporting levels of mDNS and LLMNR
5c29ec6 
The per-link settings are ignored if the feature is disabled by the global setting.
Let's announce the effective level, to make not users confused.

Closes systemd#24863.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 Programming errors, that need preferential fixing resolve
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

resolve: provide effective mDNS or LLMNR settings yuwata/systemd
2 participants
@msoltyspl @Tachi107