Failed to create listener for avahi-daemon
### Analysis

I have Homebridge v1.8.5 (HAP v0.12.3) (Homebridge 294E) is running on port 51778 of a Synology.

I have switched off all plugins and child bridges but still get this error in the log: 

Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found
WARNING couldn't map socket coming from remote address ::ffff:169.254.106.229:34126     at local address ::ffff:169.254.106.229 to an interface!

I note that 169.x.x.x is not an IP range that I (knowingly) use in my LAN. 

Any ideas what this is please? 

### Expected Behavior

I expect to not see failures and errors in the log file. 

### Steps To Reproduce

Run Homebridge and the error appears. 

### Logs

```markdown
[1/18/2025, 3:26:08 PM] Homebridge v1.8.5 (HAP v0.12.3) (Homebridge 294E) is running on port 51778.
[1/18/2025, 3:26:08 PM] 

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found
WARNING couldn't map socket coming from remote address ::ffff:169.254.106.229:34126     at local address ::ffff:169.254.106.229 to a interface!
```

### Configuration

```json
File not available
```

### Environment

- OS: DSM 7..2.2
- Software: Homebridge in a Container 
- Node: 
- npm:


### Process Supervisor

Docker (Mention image name in `Additional Context`)

### Additional Context

_No response_