Fixed the issue of rtmp not being able to listen to ipv6, added ipv6 port verification code.

[hzt1234hf]

Hello administrator, I recently fixed a small issue with listening to the rtmp IPv6 port. Please review.

• Issue source: Issue Configuring Failed to Start IPV6
• Issue: The original problem was mainly due to a slight difference in the listening method between IPv4 and IPv6 ports. For IPv4, it only needs to write the port number to listen, while for IPv6, it needs to write at least [::]:port to listen. Therefore, an error occurs during verification.
• Modification: Added validation code for IPv6, currently only supports the format [::]:port.
• Usage and effect: Modify the settings, start SRS, and after testing, it can correctly listen to the IPv6 port, and both pushing and pulling streams work normally.
  • 
  • 
  • 

---

TRANS_BY_GPT3

[codecov-io]

Codecov Report

Merging #2157 (5d86143) into 3.0release (4f01340) will decrease coverage by 0.00%.
The diff coverage is 58.33%.

@@              Coverage Diff               @@
##           3.0release    #2157      +/-   ##
==============================================
- Coverage       52.91%   52.91%   -0.01%     
==============================================
  Files              82       82              
  Lines           26693    26703      +10     
==============================================
+ Hits            14125    14130       +5     
- Misses          12568    12573       +5     

| Impacted Files | Coverage Δ | |'

'| Impacted Files | Coverage Δ | |
|---|---|---|
| trunk/src/app/srs_app_config.cpp | 81.07% <58.33%> (-0.12%) | ⬇️ |

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f01340...5d86143. Read the comment docs.

TRANS_BY_GPT3

[chen-guanghua]

#2581, the mentioned issue has been fixed.

TRANS_BY_GPT3