可以考虑这里接单，那里发单。

先顾好上半生，除非有特殊原因 50 岁必挂

clatd 在按这个流程建立的 archlinux 里不稳定，现在已经找出原因是因为 systemd-networkd 自动重启的时候会添加一个 default 路由。造成跟 clatd 添加的 default 路由冲突。

找到 systemd-networkd 的设置文件后，我这里是：
/run/systemd/network/10-netplan-eth0.network

在 DHCP 项下面添加一行 UseRoutes=false

保存，重启。

折腾记录在这里： https://github.com/zazitufu/scripts/issues/7#issuecomment-1462491672

我感覺應該直接問 ChatGPT 就有回答了

免费的就是最贵的

@tyzandhr 入岛也未必保险啊，听过绿岛小夜曲吗

先整理 clatd 的安装过程 https://github.com/zazitufu/scripts/issues/7

@yunyuyuan 我找到解决方法，还有解决 clatd 不稳定的方法了。晚点整理一下发上来。

@yunyuyuan 你好，巴黎的开了 4 天终于开出来了。但是按照教程使用 clatd 时，启动这个服务之后显示以下内容：

=====================
○ clatd.service - 464XLAT CLAT daemon
Loaded: loaded (/usr/lib/systemd/system/clatd.service; enabled; preset: disabled)
Active: inactive (dead) since Mon 2023-03-06 14:31:20 UTC; 9s ago
Duration: 1.875s
Docs: man:clatd(8)
Process: 34959 ExecStart=/usr/sbin/clatd (code=exited, status=0/SUCCESS)
Main PID: 34959 (code=exited, status=0/SUCCESS)
CPU: 197ms

Mar 06 14:31:18 v6par systemd[1]: Started 464XLAT CLAT daemon.
Mar 06 14:31:18 v6par clatd[34959]: Starting clatd v1.6 by Tore Anderson <[email protected]>
Mar 06 14:31:18 v6par clatd[34959]: Performing DNS64-based PLAT prefix discovery (cf. RFC 7050)
Mar 06 14:31:20 v6par clatd[34959]: No PLAT prefix could be discovered. Your ISP probably doesn't provide NAT64/DNS64 PLAT service. Exiting.
Mar 06 14:31:20 v6par systemd[1]: clatd.service: Deactivated successfully.
=======================

请问这是我哪里没有作对吗？

另外就是请教一下，我这边在机器上，经常过一段时间，估计大半天左右把，然后 curl -4 google.com 就没反应了。然后重启一次 clatd 服务又可以了。有可能是在什么地方出错了吗？

@yunyuyuan 那现在应该在哪里加呢？请指点一下，谢谢。

我这边的弄的阿姆斯特丹的，cloudflare tunnel 经常掉线。查看日志是显示


Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z INF Retrying connection in up to 1m4s connIndex=3 ip=198.41.200.233
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z ERR Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=1 ip=198.41.200.33
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z INF Retrying connection in up to 1m4s connIndex=1 ip=198.41.200.33
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z ERR Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=2 ip=198.41.192.67
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z INF Retrying connection in up to 1m4s connIndex=2 ip=198.41.192.67
Mar 02 17:19:57 AMS-v6 cloudflared[279]: 2023-03-02T17:19:57Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0
Mar 02 17:20:09 AMS-v6 cloudflared[279]: 2023-03-02T17:20:09Z WRN If this log occurs persistently, and cloudflared is unable to connect to Cloudflare Network with `quic` protocol, then most likely your machine/network is getting its egress UDP to port 7844 (or others) blocked or dropped. Make sure to allow egress connectivity as per https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/configuration/ports-and-ips/
Mar 02 17:20:09 AMS-v6 cloudflared[279]: If you are using private routing to this Tunnel, then UDP (and Private DNS Resolution) will not work unless your cloudflared can connect with Cloudflare Network with `quic`. connIndex=3 ip=198.41.200.233
Mar 02 17:20:09 AMS-v6 cloudflared[279]: 2023-03-02T17:20:09Z INF Switching to fallback protocol http2 connIndex=3 ip=198.41.200.233
Mar 02 17:20:09 AMS-v6 cloudflared[279]: 2023-03-02T17:20:09Z ERR Connection terminated error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=3

我现在用 cloudflare tunnel ,在旧金山的千兆家宽上（上下速率对等）装了个 v2ray 。

但是速度很迷惑，广东电信用 v2rayN ，直连的话 10Mbps ，使用 cloudflare tunnel 的话，有时跟直连差不多，有时能到近 300Mbps （ speedtest.net)。感觉速度不稳定。

请教各位使用 tunnel 的连接速度是否都比较稳定（不管速度高低，只说稳定）？