home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.97k stars 30.52k forks source link

UFW Blocks TP-Link/Kasa Discovery #84675

Closed Bupher closed 1 year ago

Bupher commented 1 year ago

The problem

UFW blocks TP-Link/Kasa device discovery. Disabling UFW immediately fixes it, and I can add devices again. I can still control devices while UFW is enabled, but I cannot add new ones. I added 9999 to my whitelist, but that does not appear to have any effect. I do not see any other documentation requesting other ports be added.

What version of Home Assistant Core has the issue?

core-2022.12.8

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

tplink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink

Diagnostics information

config_entry-tplink-a78ac7cd440f40203810a3fc8f1c6068.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Ubuntu 22.04.1 LTS Docker version 20.10.12, build 20.10.12-0ubuntu4 docker-compose version 1.29.2, build unknown

image image

home-assistant[bot] commented 1 year ago

Hey there @rytilahti, @thegardenmonkey, mind taking a look at this issue as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `tplink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


tplink documentation tplink source (message by IssueLinks)

rytilahti commented 1 year ago

The discovery is done using broadcast packets, so you probably have to find out how to configure ufw to let them pass. If you have logging enabled, you should see the filtered packets in the kernel log which may be useful for debugging such issues.

As this is not related to the homeassistant integration itself, I'll close this issue.