Closed kylev closed 9 months ago
I have the same issue
otbr-agent[303]: 00:00:27.167 [N] Mle-----------: RLOC16 8000 -> fffe
otbr-agent[303]: 00:00:27.170 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[303]: 00:00:27.424 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[303]: 00:00:33.926 [N] RouterTable---: Allocate router id 32
otbr-agent[303]: 00:00:33.926 [N] Mle-----------: RLOC16 fffe -> 8000
otbr-agent[303]: 00:00:33.929 [N] Mle-----------: Role detached -> leader
otbr-agent[303]: 00:00:33.930 [N] Mle-----------: Partition ID 0xbd9a83a
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:33.946 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: 00:00:33.966 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:34.373 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:34.686 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[303]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:36.000 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[303]: 00:00:43.815 [W] Platform------: Failed to update ipsets: Failed
Having the same issue here, not sure if this is a Home-Assistant setup issue or an issue with my router config. I'm running TP-Link Omada hardware and have home-assistant os running in a KVM with a physical network adapter passed through and setup as the default.
Logs look nearly identical:
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-web: starting
s6-rc: info: service otbr-web successfully started
[08:13:25] INFO: Starting otbr-web...
otbr-web[242]: [INFO]-WEB-----: Running 0.3.0-9e50efa-dirty
otbr-web[242]: [INFO]-WEB-----: Border router web started on wpan0
[08:13:26] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
otbr-agent[180]: 00:00:25.119 [N] Mle-----------: RLOC16 a000 -> fffe
otbr-agent[180]: 00:00:25.122 [W] Platform------: [netif] Failed to process request#5: Operation not supported
otbr-agent[180]: 00:00:25.564 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[180]: 00:00:32.067 [N] RouterTable---: Allocate router id 40
otbr-agent[180]: 00:00:32.069 [N] Mle-----------: RLOC16 fffe -> a000
otbr-agent[180]: 00:00:32.071 [N] Mle-----------: Role detached -> leader
otbr-agent[180]: 00:00:32.079 [N] Mle-----------: Partition ID 0x76776044
ipset v7.10: The set with the given name does not exist
otbr-agent[180]: 00:00:32.131 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[180]: 00:00:32.147 [W] Platform------: [netif] Failed to process request#6: File exists
ipset v7.10: The set with the given name does not exist
otbr-agent[180]: 00:00:32.202 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[180]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
ipset v7.10: The set with the given name does not exist
otbr-agent[180]: 00:00:34.452 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[180]: 00:00:35.997 [W] Platform------: Failed to update ipsets: Failed
ipset v7.10: The set with the given name does not exist
otbr-agent[180]: 00:00:44.635 [W] Platform------: Failed to update ipsets: Failed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
have home-assistant os running in a KVM with a physical network adapter passed through and setup as the default.
Same thing here, same error message.
Is there any update? because I ran in the same error.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Same error messages on my system
Same here on raspberry pi 4 + HAOS + nrf52840 otbr
up
This is still a problem at the moment.
If reading the error message:
Failed to update ipsets: Failed ipset v7.10: The set with the given name does not exist
is the system trying updating one IP-Set = OK if its already defined.
Then the system is starting the OS is not having custom IP-Sets loaded so first need adding the set it with the first use of it and after that using update all the time. So its looks some have making bad coding here (Silabs standard ?).
not stale
Describe the issue you are experiencing
My thread network is unstable, and also produces a fair number of
ipset
and route problems. During the boot sequence of otbr-agent, I see a singleipset v7.10: The set with the given name does not exist
message. This error continues in the logs over time, often paired with "unavailable" devices and routing errors.What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
OpenThread Border Router
What is the version of the add-on?
2.3.2
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4918 Installed Version | 1.32.1 Stage | running Available Repositories | 1285 Downloaded Repositories | 3Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | October 7, 2023 at 5:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | false remote_server | us-east-1-8.ui.nabu.casa certificate_status | ready can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 10.5 -- | -- update_channel | beta supervisor_version | supervisor-2023.09.2 agent_version | 1.5.1 docker_version | 23.0.6 disk_total | 458.4 GB disk_used | 6.5 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Terminal & SSH (9.7.1), File editor (5.6.0), AirSonos (3.6.0), Silicon Labs Multiprotocol (2.3.2), Matter Server (4.9.0)Dashboards
dashboards | 5 -- | -- resources | 0 views | 4 mode | storageRecorder
oldest_recorder_run | September 6, 2023 at 2:09 AM -- | -- current_recorder_run | September 14, 2023 at 11:36 AM estimated_db_size | 45.23 MiB database_engine | sqlite database_version | 3.41.2Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
During boot:
During a Thread mesh reconfiguration:
Possibly during power off of a device:
Additional information
No response