home-assistant[bot]
commented
1 week ago Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (network) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `network` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign network` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
network documentation network source (message by IssueLinks)
The problem
I noticed my homeassistant.local was resolving to a 802.11q tunneled vlan interface (vlan10) I use for my IoT network. In spite of it having a higher metric and not being the "primary" interface, this interface was always chosen over the primary. In addition the "Auto Configure" showed the right "primary" (eno1) interface but only if I unchecked it and selected the primary interface manually, does it work properly.
What version of Home Assistant Core has the issue?
core-2024.10.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
core
Link to integration documentation on our website
https://www.home-assistant.io/integrations/network/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Sorry, I can't find any log information for mdns, the network interfaces, or the configuration of homeassistant.local.