TcpListener constructor now creates socket with ProtocolType.Tcp

[alberk8]

Description

Creating a TcpListener cause an Exception to the thrown.

Motivation and Context

• Fixes TcpListener Error On New Home#1820

How Has This Been Tested?

ESP32 REV3 and ESP32 S3

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

[coderabbitai]

📝 Walkthrough

Walkthrough

TcpListener now initializes its server socket with ProtocolType.Tcp in both the IPEndPoint constructor and lazy Start(int backlog) path. No public APIs or other listener behavior changed.

Changes

TcpListener protocol correction

Layer / File(s)	Summary
Use TCP protocol for server sockets nanoframework.System.Net.Sockets.TcpClient/Sockets/TcpListener.cs	The endpoint constructor and lazy startup initialization now create the server socket with ProtocolType.Tcp instead of ProtocolType.IPv4.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title matches the TcpListener protocol-type fix and follows the formatting rules.
Description check	✅ Passed	The description is clearly related to the TcpListener exception fix and testing context.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Ellerbach]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Ellerbach]

ho! Nice finding!

[josesimoes]

LGTM!