So, there has been this problem with netcat that has limited a lot of what I can do with it.So, let's say I start a server:netcat -l -p 11000And then I just spam some crap into the terminal:netcat -l -p 11000wddwdwwweeeAfterwards, I connect locally in another console:netcat localhost 11000And every time, I get all of that crud I spammed earlier sent immediately to me.netcat localhost 11000wddwdwwweeeNow, I have done a million different things to try and get rid of this queued data, which have included messing with buffers and using udp. However, every time, I always get this preliminary data back.This has limited many of my experimental projects, like getting voice chat to work through console. All of the packets include this data, so if the client takes even a second to connect, there will be a delay. Of course, there are the normal voice chat problems that I didn't address, but if you leave the server hanging for 10 seconds, there will be a 10 second delay on initial connection.I have asked this question before, but since that didn't work, I worded it specifically to my problem, and gave an example.Hopefully someone can finally help me.
How to keep Netcat from keeping data before connection to client
netcat