Inconsistent behavior with sockets about wsa HOT 1 OPEN

UPDATE:

I use Java's ServerSocket to create a socket that listens to a specific port (without specifying the interface or the IP address). Before the "Local network access" feature was available, when I was listening to a port in all interfaces with the previous "Advanced Networking" mode, I could connect to that port by creating a Socket client that connects to 127.0.0.1 and that port. Unfortunately, now with the "Local network access" feature, the Socket client cannot connect to the server socket.

I used netcat (the nc command) to test the functionality of inner communication in WSA and saw the following:

• Running the command nc -s 127.0.0.1 -lp 1234 starts a server port in the lo interface. In this case, we can connect to the port using the command nc 127.0.0.1 1234.
• Running the command nc -s 0.0.0.0 -lp 1234 starts a server port that should listen to all interfaces. In this case, we can connect to the port using the command nc 127.0.0.1 1234.
• Running the command nc -s <ip-address-of-eth0> -lp 1234 starts a server port in the eth0 interface. In this case, we cannot connect to the port using the command nc 127.0.0.1 1234.
• • Running the command nc -lp 1234 starts a server port that should listen to all interfaces (should be the same as nc -s 0.0.0.0 -lp 1234). In this case, we cannot connect to the port using the command nc 127.0.0.1 1234.

from wsa.