Skip to content

cannot fix the port numbers used #142

@sounds2k

Description

@sounds2k

Describe the bug

port range specified in config.xml is not observed

To Reproduce

I'm running this on a DS1819+, with the synology firewall enabled. I've unblocked port 49154 and cannot connect to the sonos speakers, it is shown in the airplay device list but the connection times out, with the logfile reporting "(device name) mute to discovery, but answers UPnP, so keep it"

I have edited /volume1/airconnect/config.xml, to edit:

<ports>0:0</port>

to

<ports>49155:44</port>

which should limit it to the port range 49155-49199 - and opened this range in the synology NAS firewall. But the connection failures persist - and the log file still shows it binding to port numbers outside of this range, for example:

bind_socket:701 socket binding 7 on port 50572
Start:1133 Starting pico HTTP server on port 50572

as a result, the only way I can get this working is to open the entire range 32768-65535 from devices on the LAN, which isn't ideal - and contrary to the idea of specifying a port range.

Expected behavior

when the port range is specified in the config.xml file, the ports assigned should be within this range.

Logfiles

  • the relevant logfile entries are already above, full config is also attached

config.xml

Hardware

Device on which you are running AirConnect-Synology):

DS1819+
running DSM 7.2.2-72806 Update 4

Package

Which package from the releases page have you downloaded):

AirConnect-dsm7-x86_64-1.8.3-20240403.spk

Additional context

Add any other context about the problem here.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdsm7DSM7 related issues

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions