Some socket tools are recommended. Some socket tools are recommended for TCP, UDP debugging, and packet capture tools.

Remember the fiddler and Charles debugger I recommended a long time ago? They are both powerful and powerful tools for debugging HTTP. Good tools help you get twice the result with half the effort. Basically, I am a complete tool control.

One day, if you are tired of writing "traditional" PHP and want to play socket, engage in emerging languages or frameworks such as Python, nodejs, And go (I'm not saying these languages cannot write Web), or simply use PHP. In fact, the performance of php5.4 has improved a lot, with the socket function of PHP, you can simply write a web socket server (the code is in the comments), and even a very good PHP framework-swoole, he is different from most other common frameworks because he does not rely on the HTTP server! Known as the advanced development framework, "the goal is to challenge first-class frameworks such as Java framework, rails on Ruby, and Python Django pylons" is a PHP framework running in Socket mode. Another name is nanoserv ,...... I say so much to prove that PHP can play well with socket, so socket, TCP, and UDP are approachable.

Description tool

1. Wireshark

This tool is an artifact for packet capture. I don't know whether it has been mentioned in previous articles. In short, he is well-received. Who knows it? I don't want to make a bad introduction, to put it simply, he will intelligently decode the protocol based on the port number. Sometimes he gets confused and chooses not to decode any protocol.

2. sokit

A tcp and UDP socket debugging auxiliary tool written by Chinese people is very easy to use. It is based on the qt framework and can be used in both Linux and Windows. It can easily assemble binary data packets, simulate subcontracting and sticking packages. There are three modes: client, server, and forwarder. The forwarder is actually a transparent proxy. Its principle is similar to that of fidder. Therefore, it can be lightweight for packet capture. Of course, it cannot be used for breakpoint debugging.

I found a small bug with this tool, that is, when sending a Binary Package [], a space is added to the brackets and it will be sent out, once I planted a heel here, and of course I can view the complete package carefully in the log (this story tells us that the log is very important)

3. TCP/IP Builder

This is a tool I used earlier. Now I have sokit and I basically don't use it anymore. This stuff is characterized by small size.

4. TCP/UDP socket debugging tool 2.3

In contrast, this tool has no features. Well, it does not even have an official homepage (a small advertisement is also included on the tool interface). I also recommend it, if you think it is suitable for your taste, at least I used it for a while.

5. tcpview

It is also an artifact in windows. It mainly checks the current TCP connection and UDP connection status, and can also disconnect the connection that is transmitting data. In addition to testing and debugging TCP at ordinary times, she can also find some inexplicable connections, so you should check your system.

6. Some small scripts and gadgets written by myself will not be ugly. What's more, everyone can write them by themselves.

That's all. If you have an amazing collection of artifacts, please contact me.

7. tcpdump
8. ngrep
9. Microsoft Network Monitor
10. Microsoft Research TCP Analyzer

Some socket tools are recommended. Some socket tools are recommended for TCP, UDP debugging, and packet capture tools.