Multi-homed host: ipaddress flag doesn't prevent wrong multicasts

[kapfenho]

I am running AssetUPnP 4.6.3 on a multihomed environment on Debian x86_64. To
run the UPnP service in one network only I use flag

--ipaddress x.x.x.x

TCP and UDP listener bind to the correct socket, other networks are not used.

However, the multicasts are sent to other networks as well, carrying an invalid
URL in the payload (details and config below).

Communication in the configured network is working properly. I noticed that for
restarted control devices it may take a minute to list AssetUPnP - I guess that's
ok for a UPnP service, right?

Cheers, kapfenho

ps: thanks for this outstanding music server

*** good packet

00:00:00.020331 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 348: vlan 500, p 0, ethertype IPv4, 172.16.6.4.35238 > 239.255.255.250.1900: UDP, length 302
....E..J.W@...L.
P.........l.6..NOTIFY * HTTP/1.1
Host: 239.255.255.250:1900
LOCATION: http://172.16.6.4:26125/DeviceDescription.xml
NTS: ssdp:alive
CACHE-CONTROL: max-age=1800
Server: UPnP/1.0, DLNADOC/1.50, AssetUPnP/1.0
USN: uuid:7920C4B2-07A7-3A30-F547-925ABE888F85-abcd-123456789abc::upnp:rootdevice
NT: upnp:rootdevice


*** wrong packet

00:00:13.120738 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 344: 172.16.4.4.39284 > 239.255.255.250.1900: UDP, length 302
E..J)j@...S.
P.......t.l.6..NOTIFY * HTTP/1.1
Host: 239.255.255.250:1900
LOCATION: http://172.16.4.4:26125/DeviceDescription.xml
NTS: ssdp:alive
CACHE-CONTROL: max-age=1800
Server: UPnP/1.0, DLNADOC/1.50, AssetUPnP/1.0
USN: uuid:7920C4B2-07A7-3A30-F547-925ABE888F85-abcd-123456789abc::upnp:rootdevice
NT: upnp:rootdevice


*** processes

10867 ?        S      0:00 AssetUPnP --ipaddress 172.16.6.4
10869 ?        Sl     0:03  \_ /home/upnp/assetupnp-4.6.3/AssetUPnP --fork-is-webconfig --ipaddress 172.16.6.4 --control-pipe 11
12333 ?        Sl    11:36  \_ /home/upnp/assetupnp-4.6.3/AssetUPnP --fork-is-upnp --ipaddress 172.16.6.4 --control-pipe 7
18955 ?        S      0:13  \_ /home/upnp/assetupnp-4.6.3/AssetUPnP --fork-is-umedialibrary --umedialibrary-param s --control-pipe 9


*** sockets

udp    UNCONN     0      0              172.16.6.4:1900                  *:*      users:(("AssetUPnP",pid=12333,fd=29))
tcp    LISTEN     0      20             172.16.6.4:45537                 *:*      users:(("AssetUPnP",pid=10869,fd=8))
tcp    LISTEN     0      20             172.16.6.4:26125                 *:*      users:(("AssetUPnP",pid=12333,fd=32))


*** interfaces

4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 00:00:00:00:83:02 brd ff:ff:ff:ff:ff:ff
    inet 172.16.4.4/24 brd 172.16.4.255 scope global bond0
       valid_lft forever preferred_lft forever
5: bond0.500@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 00:00:00:00:83:12 brd ff:ff:ff:ff:ff:ff
    inet 172.16.6.4/24 brd 172.16.6.255 scope global bond0.500
       valid_lft forever preferred_lft forever


*** route

default via 172.16.4.1 dev bond0 
172.16.4.0/24 dev bond0  proto kernel  scope link  src 172.16.4.4 
172.16.6.0/24 dev bond0.500  proto kernel  scope link  src 172.16.6.4 


*** packets

2016-02-17 23:47:24.718405 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 344: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 302
2016-02-17 23:47:24.738562 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 396: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 354
2016-02-17 23:47:24.758698 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 424: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 382
2016-02-17 23:47:24.778849 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 408: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 366
2016-02-17 23:47:24.799002 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 410: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 368
2016-02-17 23:47:24.819149 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 371: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 329
2016-02-17 23:47:24.839295 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 344: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 302
2016-02-17 23:47:24.859433 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 396: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 354
2016-02-17 23:47:24.879569 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 424: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 382
2016-02-17 23:47:24.899713 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 408: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 366
2016-02-17 23:47:24.919856 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 410: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 368
2016-02-17 23:47:24.939997 00:00:00:00:83:02 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 371: 172.16.4.4.44550 > 239.255.255.250.1900: UDP, length 329
2016-02-17 23:47:24.960337 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 348: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 302
2016-02-17 23:47:24.980541 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 400: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 354
2016-02-17 23:47:25.000712 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 428: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 382
2016-02-17 23:47:25.020870 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 412: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 366
2016-02-17 23:47:25.041010 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 414: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 368
2016-02-17 23:47:25.061167 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 375: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 329
2016-02-17 23:47:25.081327 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 348: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 302
2016-02-17 23:47:25.101486 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 400: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 354
2016-02-17 23:47:25.121634 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 428: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 382
2016-02-17 23:47:25.141791 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 412: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 366
2016-02-17 23:47:25.161950 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 414: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 368
2016-02-17 23:47:25.182095 00:00:00:00:83:12 > 01:00:5e:7f:ff:fa, ethertype 802.1Q (0x8100), length 375: vlan 500, p 0, ethertype IPv4, 172.16.6.4.39182 > 239.255.255.250.1900: UDP, length 329

[PeterP]

Thanks for the bug report, the problem is being investigated. I'll get back to you when a fix is availablel

[PeterP]

New beta posted, both bugs should be gone: UDP packets sent on all interfaces and not replying to search request when a new control point starts up.

https://forum.dbpoweramp.com/showthr...-R4-6-4-beta-6