miniupnp.tuxfamily.org Forum Index miniupnp.tuxfamily.org
The forum about miniupnp and libnatpmp
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problems with miniSSDPD on Unifi Dream Machine Router
Goto page 1, 2  Next
 
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpc Bugs
View previous topic :: View next topic  
Author Message
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Thu Jan 14, 2021 11:49 am    Post subject: Problems with miniSSDPD on Unifi Dream Machine Router Reply with quote

Hi guys,

I am running a Unifi Dream Machine with multiple VLANs. One VLAN is for clients, one is for IoT devices. Among the IoT devices are also devices that stream their content over the network and publish it over the network via broadcast / SSDP.

The dream machine has an implementation of minisssdpd, unfortunately I can't tell which version is running here, but it doesn't work as it should.

The command line that the deamon runs:

27515 root /usr/sbin/minissdpd -s /run/minissdpd.sock -p /run/minissdpd.pid -F -i br0 -i br20

br0 = LAN 192.168.1.0/24
br20 = IoT 192.168.20.0/24

When I run this command manually on the CLI, I can see that the service is running and devices are also registering here:

# /usr/sbin/minissdpd -s /run/minissdpd.sock -p /run/minissdpd.pid -d -i br0 -i br20
minissdpd[30431]: SSDP request: 'NOTIFY' (2) ssdp:alive nt=uuid:7076436f-6e65-1063-8074-bc307db902ea
minissdpd[30431]: new device discovered : uuid:7076436f-6e65-1063-8074-bc307db902ea
minissdpd[30431]: ** i=1 deltadev=0 **
minissdpd[30431]: SSDP request: 'NOTIFY' (2) ssdp:alive nt=upnp:rootdevice
minissdpd[30431]: new device discovered : uuid:7076436f-6e65-1063-8074-bc307db902ea::upnp:rootdevice
minissdpd[30431]: ** i=1 deltadev=1 **
minissdpd[30431]: SSDP request: 'NOTIFY' (2) ssdp:alive nt=urn:schemas-upnp-org:device:MediaServer:1
minissdpd[30431]: new device discovered : uuid:7076436f-6e65-1063-8074-bc307db902ea::urn:schemas-upnp-org:device:MediaServer:1
minissdpd[30431]: ** i=1 deltadev=2 **
minissdpd[30431]: SSDP request: 'NOTIFY' (2) ssdp:alive nt=urn:schemas-upnp-org:service:ContentDirectory:1
minissdpd[30431]: new device discovered : uuid:7076436f-6e65-1063-8074-bc307db902ea::urn:schemas-upnp-org:service:ContentDirectory:1
minissdpd[30431]: ** i=1 deltadev=3 **
minissdpd[30431]: SSDP request: 'NOTIFY' (2) ssdp:alive nt=urn:schemas-upnp-org:service:ConnectionManager:1
minissdpd[30431]: new device discovered : uuid:7076436f-6e65-1063-8074-bc307db902ea::urn:schemas-upnp-org:service:ConnectionManager:1
minissdpd[30431]: ** i=1 deltadev=4 **
minissdpd[30431]: SSDP request: 'NOTIFY' (2) ssdp:alive nt=uuid:7076436f-6e65-1063-8074-bc307db902ea
minissdpd[30431]: device updated : uuid:7076436f-6e65-1063-8074-bc307db902ea
minissdpd[30431]: ** i=0 deltadev=5 **
minissdpd[30431]: 5 new devices added


Now when I search for UPnP devices via VLC, the service also gets a request, but doesn't seem to respond:

minissdpd[30431]: SSDP request: 'M-SEARCH' (1) unknown st=urn:schemas-upnp-org:device:MediaServer:1
minissdpd[30431]: SSDP M-SEARCH from 192.168.1.101:56876 ST:urn:schemas-upnp-org:device:MediaServer:1
minissdpd[30431]: ** i=0 deltadev=0 **
minissdpd[30431]: SSDP request: 'M-SEARCH' (1) unknown st=urn:schemas-upnp-org:device:MediaServer:1
minissdpd[30431]: SSDP M-SEARCH from 192.168.1.101:56876 ST:urn:schemas-upnp-org:device:MediaServer:1
minissdpd[30431]: ** i=0 deltadev=0 **
minissdpd[30431]: SSDP request: 'M-SEARCH' (1) unknown st=urn:ses-com:device:SatIPServer:1
minissdpd[30431]: SSDP M-SEARCH from 192.168.1.101:56876 ST:urn:ses-com:device:SatIPServer:1
minissdpd[30431]: ** i=0 deltadev=0 **
minissdpd[30431]: SSDP request: 'M-SEARCH' (1) unknown st=urn:ses-com:device:SatIPServer:1
minissdpd[30431]: SSDP M-SEARCH from 192.168.1.101:56876 ST:urn:ses-com:device:SatIPServer:1
minissdpd[30431]: ** i=0 deltadev=0 **

What is going wrong here?
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Fri Jan 15, 2021 6:44 pm    Post subject: Reply with quote

everything looks OK

you should run tcpdump / tshark on br0 to see the M-SEARCH responses
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Sat Jan 16, 2021 6:59 pm    Post subject: Reply with quote

It seems that only WLAN clients are affected, but they are also tagged in the same VLAN as the directly connected devices, which can see the streaming devices.... Rally strange Sad
Back to top
View user's profile Send private message
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Mon Jan 18, 2021 8:58 am    Post subject: Reply with quote

Perhaps I found something here:

I just tried to find my Receiver with the corresponding app and I got that on the syslog of my router:

miniupnpd interface index not matching 9 != 10
miniupnpd interface index not matching 9 != 11
miniupnpd interface index not matching 9 != 12
miniupnpd interface index not matching 9 != 13

I just had a look at "ip link show":

9: br0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
10: eth0@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:a7 brd ff:ff:ff:ff:ff:ff
11: eth1@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
12: eth2@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:a9 brd ff:ff:ff:ff:ff:ff
13: eth3@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:aa brd ff:ff:ff:ff:ff:ff

And its br0, but without eth in front of it.

Could this be the problem?
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Mon Jan 18, 2021 9:03 am    Post subject: Reply with quote

TheUntouchable wrote:
Perhaps I found something here:

I just tried to find my Receiver with the corresponding app and I got that on the syslog of my router:

miniupnpd interface index not matching 9 != 10
miniupnpd interface index not matching 9 != 11
miniupnpd interface index not matching 9 != 12
miniupnpd interface index not matching 9 != 13

I just had a look at "ip link show":

9: br0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
10: eth0@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:a7 brd ff:ff:ff:ff:ff:ff
11: eth1@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
12: eth2@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:a9 brd ff:ff:ff:ff:ff:ff
13: eth3@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 74:ac:b9:46:8f:aa brd ff:ff:ff:ff:ff:ff

And its br0, but without eth in front of it.

Could this be the problem?


yes miniupnpd rejects the request because it doesn't match the netmask.
One workaround is to cheat on the netmask :
https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/INSTALL#L146
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Mon Jan 18, 2021 10:18 am    Post subject: Reply with quote

Ah cool thank you!

The miniupnpd config is currently like that:

ext_ifname=ppp0
listening_ip=br0
listening_ip=br20
listening_ip=br40


Do I have to change the br0 to br0/24? Because this seems not to work Very Happy
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Mon Jan 18, 2021 8:52 pm    Post subject: Reply with quote

TheUntouchable wrote:
Ah cool thank you!

The miniupnpd config is currently like that:

ext_ifname=ppp0
listening_ip=br0
listening_ip=br20
listening_ip=br40


Do I have to change the br0 to br0/24? Because this seems not to work Very Happy

what's the ip address and mask of each network interface ?

For example if it is
br0 = 192.168.1.0/24
br20 = 192.168.2.0/24
br40 = 192.168.3.0/24

you will do
Code:
listening_ip=br0/22
listening_ip=br20/22
listening_ip=br40/22

Got it ?
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Tue Jan 19, 2021 11:45 am    Post subject: Reply with quote

Thanks for that help Wink

The networks are currently configured in that way:

Quote:

br0 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::74ac:b9ff:fe46:8fa7/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1

br20 Link encap:Ethernet HWaddr 76:AC:B9:16:8F:AC
inet addr:192.168.20.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::87f:51ff:fe52:9f1e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br30 Link encap:Ethernet HWaddr 76:AC:B9:26:8F:AC
inet addr:192.168.30.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::a4ee:59ff:fe3b:50bc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br40 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet addr:192.168.40.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::3858:abff:fef2:99a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br50 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet addr:192.168.50.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::90e9:dbff:fefb:f711/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

br60 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet addr:192.168.60.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::8845:98ff:fe04:c46d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:A7
inet6 addr: fe80::76ac:b9ff:fe46:8fa7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth1 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:A8
inet6 addr: fe80::76ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth2 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:A9
inet6 addr: fe80::76ac:b9ff:fe46:8fa9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth3 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:AA
inet6 addr: fe80::76ac:b9ff:fe46:8faa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth4 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:AB
inet6 addr: fe80::76ac:b9ff:fe46:8fab/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

ra0 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:AC
inet6 addr: fe80::76ac:b9ff:fe46:8fac/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

ra1 Link encap:Ethernet HWaddr 76:AC:B9:16:8F:AC
inet6 addr: fe80::74ac:b9ff:fe16:8fac/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

ra2 Link encap:Ethernet HWaddr 76:AC:B9:26:8F:AC
inet6 addr: fe80::74ac:b9ff:fe26:8fac/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

ra3 Link encap:Ethernet HWaddr 76:AC:B9:36:8F:AC
inet6 addr: fe80::74ac:b9ff:fe36:8fac/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

ra4 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AC
inet6 addr: fe80::74ac:b9ff:fe46:8fac/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

ra4.20 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

ra4.30 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

ra4.40 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

ra4.50 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

ra4.60 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AC
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

rai0 Link encap:Ethernet HWaddr 74:AC:B9:46:8F:AD
inet6 addr: fe80::76ac:b9ff:fe46:8fad/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

rai1 Link encap:Ethernet HWaddr 76:AC:B9:16:8F:AD
inet6 addr: fe80::74ac:b9ff:fe16:8fad/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

rai2 Link encap:Ethernet HWaddr 76:AC:B9:26:8F:AD
inet6 addr: fe80::74ac:b9ff:fe26:8fad/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

rai3 Link encap:Ethernet HWaddr 76:AC:B9:36:8F:AD
inet6 addr: fe80::74ac:b9ff:fe36:8fad/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

rai4 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AD
inet6 addr: fe80::74ac:b9ff:fe46:8fad/64 Scope:Link
UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1

rai4.20 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AD
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

rai4.30 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AD
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

rai4.40 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AD
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

rai4.50 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AD
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

rai4.60 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:AD
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1

switch0 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

switch0.1 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

switch0.20 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

switch0.30 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

switch0.40 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

switch0.50 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

switch0.60 Link encap:Ethernet HWaddr 76:AC:B9:46:8F:A8
inet6 addr: fe80::74ac:b9ff:fe46:8fa8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1


So all are /24.

VLANs are configured like that:
Quote:

9: br0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::74ac:b9ff:fe46:8fa7/64 scope link
valid_lft forever preferred_lft forever

10: eth0@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 74:ac:b9:46:8f:a7 brd ff:ff:ff:ff:ff:ff
inet6 fe80::76ac:b9ff:fe46:8fa7/64 scope link
valid_lft forever preferred_lft forever

11: eth1@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 74:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::76ac:b9ff:fe46:8fa8/64 scope link
valid_lft forever preferred_lft forever

12: eth2@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 74:ac:b9:46:8f:a9 brd ff:ff:ff:ff:ff:ff
inet6 fe80::76ac:b9ff:fe46:8fa9/64 scope link
valid_lft forever preferred_lft forever

13: eth3@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 74:ac:b9:46:8f:aa brd ff:ff:ff:ff:ff:ff
inet6 fe80::76ac:b9ff:fe46:8faa/64 scope link
valid_lft forever preferred_lft forever

---

58: br20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:16:8f:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.20.1/24 scope global br20
valid_lft forever preferred_lft forever
inet6 fe80::87f:51ff:fe52:9f1e/64 scope link
valid_lft forever preferred_lft forever

59: br30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:26:8f:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.30.1/24 scope global br30
valid_lft forever preferred_lft forever
inet6 fe80::a4ee:59ff:fe3b:50bc/64 scope link
valid_lft forever preferred_lft forever

60: br40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet 192.168.40.1/24 scope global br40
valid_lft forever preferred_lft forever
inet6 fe80::3858:abff:fef2:99a/64 scope link
valid_lft forever preferred_lft forever

61: br50: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet 192.168.50.1/24 scope global br50
valid_lft forever preferred_lft forever
inet6 fe80::90e9:dbff:fefb:f711/64 scope link
valid_lft forever preferred_lft forever

62: br60: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet 192.168.60.1/24 scope global br60
valid_lft forever preferred_lft forever
inet6 fe80::8845:98ff:fe04:c46d/64 scope link
valid_lft forever preferred_lft forever


I will not post any more lines now because I don't want to make it even more confusing Very Happy I could find anything like a spoiler tag here so if you need more output please let me know.


I tried to change the config of miniupdnpd like that:

Quote:

ext_ifname=ppp0
listening_ip=br0/22
listening_ip=br20/22
listening_ip=br40/22


But still the WLAN clients can't see anything, but the LAN clients can and I am still getting the "interface index not matching 9 != 10" message when search for the Receiver (br20) from a WLAN device with the upnp App. I killed both, miniupnpd and minissdpd after changing the config.

To you have any hint here..? I must admit that I am not that deep in that topic.. Do I have to add the ra interfaces too?

And thanks a lot for your help!
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Wed Jan 20, 2021 9:16 am    Post subject: Reply with quote

You didn't got it Wink

it is 192.168.1.1, 192.168.20.1 etc.

So will need to use /16.
(so a source address 192.168.20.X will match 192.168.1.1/16)
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Wed Jan 20, 2021 9:50 am    Post subject: Reply with quote

miniupnp wrote:
You didn't got it Wink

it is 192.168.1.1, 192.168.20.1 etc.

So will need to use /16.
(so a source address 192.168.20.X will match 192.168.1.1/16)


Yes, unfortunately I have to admit that I didn't got it Very Happy

I now changed the config like that:
listening_ip=br0/16
listening_ip=br20/16
listening_ip=br40/16

So all network should be covered.

Tried it again from my laptop (192.168.1.101) which is from br0. It should see the receiver wich has 192.168.20.6 (br20) or my Synology NAS at 192.168.40.3 (br40) but that did still not work. The pc, directly wired with ip 192.168.1.100 (br0) does see the device.

Now I am getting also the logs flooded with:

interface index not matching 60 != 58
interface index not matching 60 != 9

where

60: br40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet 192.168.40.1/24 scope global br40
valid_lft forever preferred_lft forever
inet6 fe80::3858:abff:fef2:99a/64 scope link
valid_lft forever preferred_lft forever

58: br20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:16:8f:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.20.1/24 scope global br20
valid_lft forever preferred_lft forever
inet6 fe80::87f:51ff:fe52:9f1e/64 scope link
valid_lft forever preferred_lft forever

9: br0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 76:ac:b9:46:8f:a8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::74ac:b9ff:fe46:8fa7/64 scope link
valid_lft forever preferred_lft forever


What I am still not getting? Very Happy

EDIT: And is there a donation link..? Wink Found it Very Happy
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Wed Jan 20, 2021 1:44 pm    Post subject: Reply with quote

that's a complicated matter.

I believe "interface index not matching" is just a warning so it shouldn't prevent miniupnpd from working.

Or maybe i'm confusing miniupnpd with minissdpd Sad

What exactly does not work ?
(explain your software setup more precisely)
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Thu Jan 21, 2021 10:17 am    Post subject: Reply with quote

I will try to explain it in all details Very Happy

I am running a Laptop (CLIENTS 192.168.1.101/24 - WLAN) and a PC (CLIENTS 192.168.1.100/24 - LAN) with the media player VLC. Also I am running a TechniSat Technicorder ISIO STC (IoT 192.168.20.6/24 - WLAN) which is running a twonky media server, that publishes the TV streams in the network and a Synology NAS (DMZ 192.168.40.3/24 - LAN) which also publishes video and music on the network.

If I now start VLC on the PC and hit Universal Plug`n Play, it takes a short time and I can see the Reseiver and browse the folders and streams there. Also possible for the NAS after a little more time.

If I do the same from any wireless device, I can't see the receiver or the NAS in that view.

Current config of minissdpd:
Quote:
/usr/sbin/minissdpd -s /run/minissdpd.sock -p /run/minissdpd.pid -F -i br0 -i br20 -i br40


Current config of miniupnpd:
Quote:

#
# Generated automatically by ubios-udapi-server
#

enable_upnp=yes
enable_natpmp=no
secure_mode=yes
system_uptime=yes
lease_file=/run/upnp.leases
minissdpdsocket=/run/minissdpd.sock
uuid=37129085-50fd-4d8e-8483-b40fd9f2d697

manufacturer_name=Ubiquiti Networks
manufacturer_url=http://ui.com
model_url=http://ui.com
friendly_name=UniFi Dream Machine
model_name=UDM
model_description=UniFi Dream Machine
serial=*removed*
model_number=00026f27

ext_ifname=ppp0
listening_ip=br0/16
listening_ip=br20/16
listening_ip=br40/16


If you have any additional question please let me know Smile
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Thu Jan 21, 2021 12:07 pm    Post subject: Reply with quote

on which machine does miniupnpd / minissdpd run ?
on which machines are all the UPnP Services running and what are they ?

minissdpd is useful if you run several upnp services on the same machine.
It also serves as service discovery cache on the client side.
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
TheUntouchable



Joined: 14 Jan 2021
Posts: 9

PostPosted: Fri Jan 22, 2021 12:00 pm    Post subject: Reply with quote

miniupnp wrote:
on which machine does miniupnpd / minissdpd run ?
on which machines are all the UPnP Services running and what are they ?

minissdpd is useful if you run several upnp services on the same machine.
It also serves as service discovery cache on the client side.


The deamons are running on my router, the upnp service is running on my receiver and nas, everything else is already in my post before mentioned Smile

The whole thing is working when I am searching from a client which is connected via LAN, but as soon as I am using a WLAN device in the same VLAN as the LAN devices, its not working anymore.
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1536

PostPosted: Fri Jan 22, 2021 5:55 pm    Post subject: Reply with quote

TheUntouchable wrote:
miniupnp wrote:
on which machine does miniupnpd / minissdpd run ?
on which machines are all the UPnP Services running and what are they ?

minissdpd is useful if you run several upnp services on the same machine.
It also serves as service discovery cache on the client side.


The deamons are running on my router, the upnp service is running on my receiver and nas, everything else is already in my post before mentioned Smile

The whole thing is working when I am searching from a client which is connected via LAN, but as soon as I am using a WLAN device in the same VLAN as the LAN devices, its not working anymore.

If there is only miniupnpd as UPnP service on the router, why do you run minissdpd ?
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpc Bugs All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP
© 2007 Thomas Bernard, author of MiniUPNP.