Add option to set listening address family

[aler9]

Describe the feature

This allows to stop listening on IPv6 as requested in #1385

Prototype:

# whether to use IPv4, IPv6 or both.
addressFamily: any|ipv4|ipv6

[aler9]

@pikachu937 in the end i didn't add an option, but hacked the server in order to listen on IPv4 only when listen IP is 0.0.0.0. This is the only one problematic IP, while in every other case the server listen only on the address family of the listen IP.

[pikachu937]

i checked and this work only if set in config file ip address and port - 0.0.0.0:55544

rtspDisable: no
protocols: [udp, tcp]
rtspAddress: 0.0.0.0:55544
rtpAddress: 0.0.0.0:22222
rtcpAddress: 0.0.0.0:22223

but, this is does not work if set in config file only port :55544(by default in config file)

rtspDisable: no
protocols: [udp, tcp]
rtspAddress: :55544
rtpAddress: :22222
rtcpAddress: :22223

can you make it automatically detect and not have to set a separate IP address?

[aler9]

@pikachu937 that's exactly as intended. When a user wants to listen on IPv4 only, he can set the listen IP to 0.0.0.0, if he wants to listen on IPv6 only he can set the listen IP to [::1], otherwise the server listens on all IP families. This is more versatile than checking the OS setting (that is something OS-dependent that may not be possible to implement on all supported platforms), since it allows to disable listening on IPv6 even when IPv6 is enabled on the OS.

[pikachu937]

hmm… if look from this side, it is logical and really works correctly. but wouldn't it be easier to do as you originally suggested through a separate setting:

# whether to use IPv4, IPv6 or both.
addressFamily: any|ipv4|ipv6

I just think it's more obvious, but like everyone else, I could be wrong

[aler9]

added in v0.22.1

[longdq01]

Hi I add option "addressFamily" but it's not working (v0.23.8 armv7)

[longdq01]

I'm listening hls address via vpn localhost:8888 -> 10.8.0.3:8888. but when I using localhost it's work, vpn return 404

[aler9]

@ftvdexcz as written above, the "addressFamily" parameter was not added but instead the server was edited in order to listen on IPv4 when a listening address contains an IPv4 IP.

Open a dedicated issue if you have problems and describe how to replicate them.

[longdq01]

@aler9 Thanks you for quick response! I'm struggling when connect via vpn. Issue describe in #2175

[github-actions]

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.