Transmission Control Protocol

It's so clever.

And to capture the broader network picture, like not just the specific HTTP traffic, but all the raw data packets flying back and forth, you rely on tools like Wireshark, TCP dump and Charles proxy.

Yeah, they record everything on the wire.

So you have a permanent forensic record of the exact sequence of communication.

So I was doing and creating this Bolt8 code, which is basically a noise protocol.

And when I started doing it, I started to point out some nodes and i was still testing locally so i made like some docker and using some containers to connect to those nodes and started sending like a lot of ping messages without reading from tcp connection so normal people would not do that because they went to send messages and like have the exchange of the needs message which is the first message on the lights network which you need to exchange to to announce feature bits and i started sending a lot of those ping messages and not reading nothing from the TCP connection.

So the peers on the other side need to somehow stop reading our message or drop the Pong message.

So I tested it with Core Lightning, LND, and all the Lightning nodes.

And when the connection receives the ping message, for example, it needs to send a pong to that peer.

But with the pong message, it didn't stop reading the connections.

So it would try to send the message, put in the outgoing kill, and continue reading from the TCP connection.

So it started like... uh pushing message adding message to a queue and not being able to send because the peer is not reading the message and starting like uh increasing the memory usage because it's not like being able to send any message and and free the queue so it would it would die by a autistic memory

Yes.

One other bit of magic in here that I talk to folks, even folks who have networking backgrounds there, right, you look at the typical, you start inspecting the traffic that's going over the wire, you look and you see the physical, the back address on the physical layer, layer two, you look at the IP logic around layer three, you look at TCP and all the stuff that's being built in as those things happen, the entire network that you see as a customer is fake.

It is an emulated, virtualized imagining of a network designed to look like networks looked 25 years ago, and it is entirely living on top of what the reality actually is.

And that is wildly exciting.

There were a bunch of early things that came out like, oh, Apple Talk, sure, great, IPX, ISPX, that, yeah.

Things that I don't even remember because they did not win.

TCP on top of IP did.

Very durable.

An Android Trojan hides its payload in the app package, then scans for debug ports left open and installs itself on whatever answers.

Turn off ADB over TCP on your managed Android fleet.

Fifteen.

Where the UEFI shell ships inside Flash, an administrator who can change the boot order can start it and use its memory write commands to turn off the checks secure boot relies on.

So the ad pay forward directive tells the ADB daemon to create a socket connection.

By specifying TCP.31415 as the first argument, you're opening port 31415 on your local computer's loopback interface.

Got it.

Then the second TCP.31415 tells ADB to take any traffic it receives on that local port, shove it through the USB or virtual connection, and spit it out on port 31415 inside the emulator's network stack.

Now, technically, depending on your shell environment, I know you can sometimes omit the TCP protocol declaration.

You can, yeah.

No.

No, it was just a simple TCP packet going out.

So it definitely wasn't just fire and forget.

It was very targeted.