You are not logged in.
The UPNP announce of my server takes about 5-10 min.
What I do:
I have kodi standalone running on a serve and I want to use kodi UPNP build in services. I installed all optional dependencies and activated upnp.
I can use totem on my laptop to discover the upnp library of kodi. The problem is, this discovering of kodi takes about 5-10 min. In the beginning, there is no kodi server, and then after some time it pops up. Any Idear what I can do to improve/investigate this?
What I did:
I think I found out its related to my network settings. I was using a bridge configured with netctl and a vpn based on tinc. I temporary disabled this and configured a static ip with the following profile:
Description='A basic static ethernet connection'
Interface=enp2s0
Connection=ethernet
IP=static
Address=('172.16.1.10/20')
Gateway=('172.16.1.1')
DNS=('172.16.1.1')
## For IPv6 autoconfiguration
IP6=no
Kodi is discovered immediately.
If I enable the bridge profile with:
Description="Example Bridge connection"
Interface=br0
Connection=bridge
BindsToInterfaces=(enp2s0)
IP=static
Address=('172.16.1.10/20')
Gateway=('172.16.1.1')
DNS=('172.16.1.1')
## Ignore (R)STP and immediately activate the bridge
#SkipForwardingDelay=yes
## Statless IPV6 config for the bridge
IP6=no
The discovery is extremely delayed.
And now I disabled ufw and volia, it seems to work with the bridge running. I guess I just had created some ufw rules to prevent avahi from working with the bridged interface.
Last edited by deisi (2018-01-02 15:14:13)
Offline