Inode protocol re-analysis by Tsy

Inode protocol re-analysis by Tsy

Statement:

1) this report by the blog Park Bitpeach Write, copyright, free reprint, please specify the source, and do not for commercial purposes.

2) If there are any infringing text or images in this document, please contact the author Bitpeach delete the appropriate section. In case of infringement of Huawei Company, please provide relevant advice and materials to the author, e-mail to [email protected], I confirm the company's source without error, the obligation to delete within the next Hour. If I do not check the mail in time, you can contact the blog Park Webmaster Delete.

3) the contents of this document mainly relate to INode the subject of the client reverse study, but relatively simple can be considered as a preliminary introduction, laughable please correct me.

4) For reference purposes only, do not use as evidence to prove the purpose, please make your own choice, verify the reference. Finally, this blog post is open source academic research, emulate, adhering to the GNU GPL v2 License Agreement (due to various factors, to protect the privacy of the packet to do a partial concealment, which is not contrary to the open source purpose of this article.) If some of the packet stealth processing still exposes my information, please comment reminds me, thanks. I don't want to be dug graves. The contents of this article shall not be used for any commercial purpose or benefit, please do not use this article for commercial benefit activities.

There are some problems with the INode.

All of a sudden tonight INode not go up, need to verify that xxx. But the moment can't figure out, so briefly and the great god bitdust A piece grabbed a bag, but the big God ran = =

1.1 - year - month - Day

This time node is the first time I really care UDP the issue of the number of the newspaper.

for the time the years One Month - Day crawl of the package. It can be noted that the packet was still reported through the UDP service .

But today, when we catch today's bag, I can't find this. UDP package, stating that the problem has changed and may not be present in UDP problem, so I searched the keywords, found such a package, very strange.

1.2 guess

The unknown state package may be a new custom pattern, and its format needs to be explored further. I crawled a lot of people's packets and found someone was a similar problem. The summary may appear as follows:

( 1 the client version is not updated because the discipline principal has not changed

( 2 ) A verification number update, does not affect the gateway changes, just server authentication. So there is no switch off the phenomenon, but not on the network phenomenon.

( ) reported by udp Span style= "font-family: the song Body;" > more eap package, very likely to update the procedures, But it is worth validating and discussing. However, the probability is great because udp is to deliver the service as much as possible , delivery is not a problem. That is, if you use udp mode changed to eap So it affects the Internet. This can not be done by the client, only the service side of the thing. Because everyone's client has not changed.

( 4 ) using Bitdust client To some extent can solve this, the great God provides the idea of virtual machine. As for myself there are two ways of thinking that can solve it

I think there are two ways, one is to honestly update and register XXX number. The second is, study bitdust your router, why your router will be no problem, this shows that your router cracked the current Method! = = Great God bitdust you are very powerful! Have foresight. I think it might be socks your new plugin problem? Since you are not blocking your router, your router is a vaccine. It's useful to study it. I want to keep up with your pace and learn the protocol.

Inode protocol re-analysis by Tsy