Tags
AI 30cloudflare 47debian 10docker 36emby 6LXC 4macOS 1Music 12NAS 3Nextcloud 1OpenWrt 6Tailscale 3TrinityCore 6VPS 1Evolution of Web Forms 2WordPress 48People 1Buddhism 3Medicine 1History 0Image Hosting 6Maps 6Tips & Tricks 20Entertainment World 7Baota 5Home Data Center 143Exploration 44Tutorials 131Mathematics 1Databases 1Culture 4Reflections 0Games 11Manga 0iKuai 6Movies 1Knowledge Engineering 2Spiritual Food 15System View 2Experience Sharing 82Virtualization 3Daily Walk 1Cognitive Structure 12Software Router 9Operations 12Cycling 1World of Warcraft 7
Great blog!! Kudos
Thanks! Welcome to visit often when you have time!
Hello blogger, after I used WARP's proxy mode, directly visiting https://ip.gs and accessing through port 40000 both returned the address after WARP NAT. ChatGPT's answer was that it might be in WARP mode instead of proxy mode, but looking at what you wrote in your article, remote access to the VPS will be directly interrupted after using WARP mode. I also found this to be true when I tried to change it to WARP mode, and the connection only recovered after changing it to proxy mode in VNC. So why do both access methods return the same address after NAT? At the same time, I found that WARP opened a new wgcf port. When WARP is turned off, the local address captured in packet capture shows as the address of this port, but when checking ip route, the default route is shown as the real IP address, indicating that the wgcf port is not the default route. Could you please help me look into why these two situations occur?
This is an abnormal result and is different from what I see, so you might need to find the cause in your own environment. However, if you indeed see that the default route is correct, and it is indeed in proxy mode, but the access effect is still the WARP address, then you should check if you previously used a global proxy pointing to WARP's proxy address and forgot to delete it; or you might as well try the ultimate reboot method. Generally, when encountering supernatural phenomena, if it were me, I would choose to reboot and start over~.
Hello blogger, when I used my own laptop to install and test WARP on a cloud server with Debian 11, after entering the registration command warp-cli registration new, it would not respond for a long time, and then I could no longer connect to the server. How can this problem be solved? I hope you can give me some advice!
Some time ago, WARP briefly revived for a few days but seems to have failed again. If you are accessing directly from the domestic network, I reckon it's highly unlikely to work.
I just went in through the web terminal of the server console and found that it works, and now WARP can be used normally. However, after I enabled WARP's proxy mode according to your tutorial and used tcpdump to capture packets, the captured packets contained traffic like QUIC, WireGuard, TLS 1.3, etc., but no MASQUE and HTTP traffic. Checking the WARP settings shows the proxy protocol is MASQUE. Do you have any insights or opinions on this situation?
Isn't that right? Isn't MASQUE based on QUIC and TLS 1.3? Before MASQUE, it was based on WireGuard. I mentioned in my article about WARP using MASQUE: ”Most relevant to WARP, QUIC offers better performance over low-latency or high-packet-loss networks through packet coalescing and multiplexing. During the handshake, QUIC packets in different contexts can be coalesced into the same UDP datagram, reducing the number of receives and system interrupts; through multiplexing, QUIC can carry multiple HTTP sessions within the same UDP connection. WARP also benefits from the high confidentiality of QUIC, with TLS 1.3 used in the protocol.”
I see. You mean that the captured QUIC and TLS 1.3 traffic is enough to prove that the current WARP communication is through the MASQUE protocol, it's just that in Wireshark, the protocol for this traffic is displayed as QUIC or TLS 1.3, right?
I understand. Thank you very much for your article and patient answers!
The blog is well written, but this JS is a bit dirty, not letting you use anything, don't know who it's trying to annoy.
Regarding the blog content, except for the code-related parts which I have enabled copying, I don't think there is any need for other descriptive content to be copied, and this is also one of the preventive measures to stop articles from being randomly copied and pasted elsewhere (of course, this behavior is not generous enough). However, actually, this kind of method is useless. The nature of HTML determines that what others see using a browser is not under my control, so if you really want to copy, just install any browser extension and it's solved. In addition, this feature is actually just a WordPress plugin. I installed it at the time because of other related needs (at that time, I was considering disabling this feature for subscribed members to improve their sense of happiness, but later I was too lazy to do it). After getting used to it, I felt there was nothing wrong with it. It can also be considered a copyright reminder and a small way to get users to visit often (although it's actually quite useless).
Hello blogger, I've been debugging Debian 12 on a domestic SoC recently. I found that in Debian 12, after the system wakes up from sleep, the Bluetooth node disappears, and I need to load the Bluetooth firmware via a command. I want to start a script to execute this command after waking up from sleep. Do you have any ideas?
In the future, you can just ask ChatGPT directly for this kind of question; your description is already quite clear. I asked for you, and ChatGPT's answer can be found in the link:Invincible File Sharingin the ”Hibernate Wakeup Enable Bluetooth Script.txt” file, and the access password is my blog's domain name.
Hello blogger, your blog loads so fast! Could you introduce your server provider and optimization tips?
I built the site directly using home broadband + idle equipment at home (mac-mini), without using a cloud host. This is actually just a Cloudflare configuration trick. I have actually written about it in my previous articles. Generally speaking, there are two ways: 1. Configure traditional Cloudflare cache rules properly. 2. Use the advanced Worker optimization method to achieve a higher level of acceleration. However, the premise is that your domain name is hosted on Cloudflare.
I wrote a series of tutorials on Cloudflare (there is a Cloudflare learning map in the pinned article). The acceleration configuration is in Part 6 (Cache Rules) and Part 7 (Worker Optimization). However, I recommend reading the series from the beginning, because website speed is not the only thing to focus on; security is also very important, so it's best to have a comprehensive understanding of Cloudflare's solutions.
I wonder if the blogger has set up a group? ＞﹏＜
You can join the TG group:https://t.me/tangwudiblog
The trinitycore 3.3.5 client is on Windows, and the server is on a virtual machine. The client can find the server but cannot log in. What could be the reason?
Could you be a bit more specific? I don't even know what client and what server you are talking about.
Sorry, I will try to be as detailed as possible.https://blog.tangwudi.com/game/trinitycore180/，我在按照您这个教程搭建魔兽世界服务器，环境跟教程一致，是虚拟机下的debian12系统，搭建过程也跟教程一致，没遇到什么问题，服务器也正常启动了，但是我在win11系统下运行wow.exe(wow-3.3.5)时，能通过创建的用户登录，也能选择服务器（按教程里服务器名称应该是叫无敌的艾泽拉斯），但是登录不上服务器，不知道问题可能出在哪里呢？
Being able to log in means that the communication between the client and the authserver process is normal, and there is no problem with the auth database. As for not being able to connect to the server, if everything before that is normal, it must be a communication issue between the worldserver process and the database. Is your database also on the same device as authserver and worldserver, or is the database separated onto another device?
It is on the same device. Are there any error logs I can check? I tried looking for them but couldn't find the cause.
To connect to the Debian database from Win11, I need to change `bind-address = 127.0.0.1` to `bind-address = [local IP]` in the `/etc/mysql/mariadb.conf.d/50-server.cnf` file on the Debian system, otherwise external connections cannot reach the database. However, after changing it, authserver fails to execute. I wonder if this information is helpful?
It should be helpful, but I don't have time to think about it in detail right now as I'm going out for dinner. Let me briefly explain the startup process: the job of authserver is to read the information in the `realmlist` table from the `auth` database, and then, based on the value of the `address` field in the table, direct the client to connect to worldserver. The key is the value of the `address` field. If you want to change it, try changing them all to your local IP.
Okay
Solved! The address in the `realmlist` table of my `auth` database should have used the real IP, but I used the loopback address 127.0.0.1. It worked after I changed it. Thanks to the blogger for the setup tutorial!
Enjoy your very own Azeroth! :)