Review the concept of available ports #43
Replies: 2 comments
|
Yes — in this scenario, the kernel(SO) will happily bind; the firewall will politely ignore the clients. |
0 replies
|
OK, to avoid this scenario (bind a procedure to a port that is available but blocked) and the necessity for the server host to open a range of ports. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
In the above piece of code, used in server stub to server a specific procedure,
you’re asking the OS to bind the socket to any available ephemeral port (port chosen automatically by the kernel).
It looks like available port is different to blocked/not blocked. So, the SO can bind an available port that is blocked by the firewall. I am not sure 🤔
All reactions