Hello, What I want to show you now is using VNC again just for simplicity, for interactive demonstration. I'm going to show you the use of Wireshark to trace network events, and I'm going to send packets between my Jetson Nano and my Raspberry Pi. I'm going to go ahead and build the client server code that we saw before the TCP code and both my Raspberry Pi and on my Jetson Nano. I'm going to go ahead and run the server. Before I do that, just have the address, I'm going to get the address over here on the Jetson Nano, 190.160.1.36. So private address with 36, and I'm going to go ahead and run the iNET server, and it's going to run automatically on that address on port five, four, three, two, one, as you probably remember. So I've started the server up, and what I'm going to do over here is I'm going to sudo Wireshark, not to be confused with Kernelshark. You have to run it as root to get it to work right. There are claims that you can run it not as root, but I just always run it as root and it always works. So I'm going to choose the interface. I'm going to look at my wired ethernet, ethernet zero, which goes through my home wireless access points switch, and you can see there's activity on it. I can just basically hit capture whenever I want to capture packets. So I'm going to connect the client here, iNET client. I'm going to connect it to 192.168.1.36. I've set it up to do 10,000 strings, so a lot of network traffic. So we have plenty of time to come over here and say capture, start and collect information, my application as well as everything else going through my screen. So I'm flooding my network with, this is the first, second, third, server string over and over again. We probably don't need to do this that long to get the idea. We'll go ahead and hit Stop. Wireshark is fantastic for network analysis. I've even used it for things like USB. It has features for other types of networks as well. I can take a look at one of these packets and you can actually see this is the first client string. You can see basically sequence numbers, acknowledgements, you can just go through here and you can see this is the third client strings, so on and so forth. So we can see our actual payload down here, and then we can see the protocol timestamp source destination between 36 and 96, the protocol and detailed information. You could do a lot more than that with Wireshark, there's great manuals on it online. It's been around for decades. It's built on top of tcpdump. An absolutely fantastic tool that I highly recommend, and it's the last of the software inserted trace tools that I think you have to have, you don't even have to spend any money. The only thing I recommend spending money on is an analog discovery for lower level hardware interfaces for these tools, otherwise, everything, software and circuit is absolutely fine. Thank you very much.