This entertaining little item <
https://acid.vegas/blog/the-port-that-does-not-exist/> (linked from <
https://www.osnews.com/story/146330/the-port-that-does-not-exist/>)
relates the tale of what happened when some curious hackers set out to
discover what happens when you try to connect to TCP port 0.
Normal network protocol stacks (like the one built into the Linux
kernel) do not (easily) allow the use of this port number for either
making connections or accepting them. The network protocol specs
themselves do not say that this port number is invalid; it is just a
convention from the earliest days that specifying a port number of 0
on a network function call means ?give me any available port at our
end?.
So what did the article writers do? Having worked out a mechanism for *accepting* connections on port 0, they then set out to discover what
nodes out on the wide, wild Internet would allow *connecting* to port
0 at their end. And they found a remarkable motley of very odd things
...
--- PyGate Linux v1.5.19
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)