In some network environment, 6667 port is recognized as IRC port. 6667端口特定网络环境下cli无法连接

Version: 0.12.0

In some environment, there is a strange failure: the CLI (or writing programs) connects to the IoTDB server but get nothing output, and the server prints nothing log.

If we change to another network (e.g., use your phone to create a shared hotspot, and let your CLI connects to the IoTDB server through the network hotspot, you may find the connection is ok.

If we change the server port from 6667 to other ports, e.g., 8889, everything is ok.

THE REASON:

The reason may be that 6667 port is recognized as the IRC port, and then the network message is translated.

What environment may cause the scenario: unclear.

问题：
在使用cli或代码远程连接server时遇到无法连接的问题，服务端完全没有相关日志，但换一个server端口或客户端连接手机热点就能正常连接，linux客户端连接完全正常

客户端版本：0.12.0
服务端版本：0.12.0

找了不同的环境进行测试，结果如下：
不同的net物理上完全隔离（不同的接入位置，不同的路由器）
2个服务端均为linux，归属不同的网络

| system | pc | net | server1-6667 | server2-6667 | server1-8889 | server2-8889 | hotspot-6667 |
| :--------:| :------: | :------: | :------: | :------: | :------: | :------: | :------: |
| win10 | pc1 | net1 | N | N | Y | Y | Y |
| mac | pc2 | net2 | N | N | Y | Y | Y |
| mac | pc3 | net3 | N | N | Y | Y | Y |
| win10| pc4 | net3 | N | N | Y | Y | Y |
| win10| pc5 | net3 | N | N | Y | Y | Y |
|linux| pc6 | net4| Y | Y | Y| Y| Y|
|linux| pc7 | net5| Y | Y | Y| Y| Y|

类似问题的场景-[网络通信端口选择一定要慎重 -- 可恶的 6667 端口](https://blog.csdn.net/cnm10050/article/details/104929464)

我想知道出现这样的情况是我自己网络环境的问题还是特定环境（操作系统/网络/其他）下6667端口就是有问题
所以，如果你也遇到类似的问题，请在下面留言

Start by reproducing the CLI-to-IoTDB server connection matrix described in the issue, comparing port 6667 with 8889 across the listed operating systems and networks. Check whether the CLI reaches the server and whether the server logs any request; done means identifying the environment-specific cause or documenting a confirmed limitation and its scope.

Written by the indexing model from the issue text.