search

Luligu / matterbridge

Matterbridge plugin manager for Matter
https://github.com/Luligu/matterbridge/blob/main/README.md
Apache License 2.0
198 stars 20 forks source link

Matterbridge Docker with Host network use wrong interface #145

Open simonepittis opened 10 hours ago

simonepittis commented 10 hours ago

I have Matterbridge on docker (v27.3.1), Network-mode Host. In setting I forced mdsn on eth0 but the container use docker0 IF:

[12:17:11.795] [Matterbridge] [notice] Matterbridge is starting... [12:17:11.801] [Matterbridge] [debug] Matterbridge logLevel: info fileLoger: true. [12:17:11.809] [Matterbridge] [debug] Matter logLevel: 1 fileLoger: true. [12:17:11.813] [PluginManager] [debug] Matterbridge plugin manager starting... [12:17:11.818] [DeviceManager] [debug] Matterbridge device manager starting... [12:17:11.820] [PluginManager] [debug] Parsing package.json of plugin matterbridge-zigbee2mqtt [12:17:11.824] [Matterbridge] [debug] Creating node storage context for plugin matterbridge-zigbee2mqtt [12:17:11.852] [Matterbridge] [debug] Using interface: 'docker0' [12:17:11.864] [Matterbridge] [debug] - with MAC address: '02:42:38:14:89:3f' [12:17:11.867] [Matterbridge] [debug] - with IPv4 address: '172.17.0.1' [12:17:11.869] [Matterbridge] [debug] - with IPv6 address: 'fe80::42:38ff:fe14:893f'

image

Luligu commented 7 hours ago

Hi, the 2 things are not correlated. The message you posted means that matterbridge found the first available not local interface in docker0 (that is very strange but has no consequences cause I don't bind it). The mdns setting for matter are another thing. If you don't see warning or error messages means that the interface you choose is correct. Matterbridge check the parameters and let you know if it is not correct.

Are you inside the ha addon maybe?