bmy001 最近的时间轴更新 bmy001 最近的时间轴更新 |
bmy001V2EX 第 72039 号会员，加入于 2014-08-26 15:52:47 +08:0059
 96  |
bmy001
johnnysun
JohnnyMoe
JohnnySun
| 码了个按 IPLoc 自动选择最优路由的 Clash Config AutoGen，感兴趣的可以玩玩看
1 宽带症候群 • bmy001 • 361 天前 • 最后回复来自 bmy001
|
4 |
| 这两天抽空弄了一个基于 IPinfo.io 数据生成 Geo2Country MMDB 数据库的工程，实现比现在主流的 MaxMind 数据库更准确的 Geo2Country 判断 宽带症候群 • bmy001 • 361 天前 • 最后回复来自 bmy001 | 8 |
| [字节跳动] [内推] 移动端音视频开发工程师
1 酷工作 • bmy001 • 2019-06-14 22:05:28 PM • 最后回复来自 bmy001
|
1 |
bmy001 最近回复了
97 天前 回复了 test0103 创建的主题 › 宽带症候群 › 如何获取各互联网服务商使用的 IP 段？ |
对于 chatgpt 这些 用 sniproxy 配合 dns
97 天前 回复了 test0103 创建的主题 › 宽带症候群 › 如何获取各互联网服务商使用的 IP 段？ |
97 天前 回复了 test0103 创建的主题 › 宽带症候群 › 如何获取各互联网服务商使用的 IP 段？ |
你把 cdn 的 asn 分流就行了
115 天前 回复了 htfcuddles 创建的主题 › 宽带症候群 › 日本方向目前联通最好的线路是哪一个？ |
@htfcuddles 这个路由中间走了一跳 10099 落东京 peer ntt
Host Loss% Snt Last Avg Best Wrst StDev
1. AS??? 192.168.1.1 0.0% 156 0.6 0.6 0.4 2.0 0.2
2. AS4808 221.219.96.1 0.0% 156 3.8 4.1 2.0 14.2 2.6
3. AS4808 125.34.174.165 87.2% 156 3.2 3.6 3.0 4.7 0.4
4. AS4808 125.33.186.209 96.1% 156 3.9 4.3 3.9 4.5 0.2
5. AS4837 219.158.7.230 97.4% 156 26.0 25.4 24.9 26.0 0.4
6. AS4837 219.158.8.202 0.0% 155 28.4 29.8 25.5 34.1 2.4
7. AS4837 219.158.8.178 0.0% 155 29.3 29.9 25.6 34.3 2.0
8. AS4837 219.158.16.214 0.0% 155 60.1 60.3 59.7 73.6 1.1
9. AS10099 202.77.22.226 0.0% 155 65.2 62.7 60.8 74.6 2.2
10. AS??? 61.14.201.125 0.0% 155 56.1 67.5 55.5 209.8 35.5
11. AS2914 ce-0-3-3.a02.tokyjp08.jp.bb.gin.ntt.net 9.0% 155 57.1 60.4 56.3 170.3 17.0
12. AS2914 ae-25.r33.tokyjp05.jp.bb.gin.ntt.net 12.9% 155 58.7 63.5 56.8 86.7 6.6
13. AS2914 ae-7.a00.tokyjp09.jp.bb.gin.ntt.net 0.0% 155 165.3 64.7 55.9 165.3 27.5
14. AS2914 ce-4-2-2.a00.tokyjp09.jp.ce.gin.ntt.net 6.5% 155 50.6 50.5 49.9 51.7 0.3
15. AS142611 vrf-ddos-monitor.cr01.tyo01.jp.nerocloud.io 0.0% 155 52.1 51.3 50.6 52.1 0.3
16. (waiting for reply)
17. (waiting for reply)
18. AS18464 xx.xx.xxx.xxx 0.0% 155 57.1 57.1 56.5 58.8 0.3
Host Loss% Snt Last Avg Best Wrst StDev
1. AS??? 192.168.1.1 0.0% 156 0.6 0.6 0.4 2.0 0.2
2. AS4808 221.219.96.1 0.0% 156 3.8 4.1 2.0 14.2 2.6
3. AS4808 125.34.174.165 87.2% 156 3.2 3.6 3.0 4.7 0.4
4. AS4808 125.33.186.209 96.1% 156 3.9 4.3 3.9 4.5 0.2
5. AS4837 219.158.7.230 97.4% 156 26.0 25.4 24.9 26.0 0.4
6. AS4837 219.158.8.202 0.0% 155 28.4 29.8 25.5 34.1 2.4
7. AS4837 219.158.8.178 0.0% 155 29.3 29.9 25.6 34.3 2.0
8. AS4837 219.158.16.214 0.0% 155 60.1 60.3 59.7 73.6 1.1
9. AS10099 202.77.22.226 0.0% 155 65.2 62.7 60.8 74.6 2.2
10. AS??? 61.14.201.125 0.0% 155 56.1 67.5 55.5 209.8 35.5
11. AS2914 ce-0-3-3.a02.tokyjp08.jp.bb.gin.ntt.net 9.0% 155 57.1 60.4 56.3 170.3 17.0
12. AS2914 ae-25.r33.tokyjp05.jp.bb.gin.ntt.net 12.9% 155 58.7 63.5 56.8 86.7 6.6
13. AS2914 ae-7.a00.tokyjp09.jp.bb.gin.ntt.net 0.0% 155 165.3 64.7 55.9 165.3 27.5
14. AS2914 ce-4-2-2.a00.tokyjp09.jp.ce.gin.ntt.net 6.5% 155 50.6 50.5 49.9 51.7 0.3
15. AS142611 vrf-ddos-monitor.cr01.tyo01.jp.nerocloud.io 0.0% 155 52.1 51.3 50.6 52.1 0.3
16. (waiting for reply)
17. (waiting for reply)
18. AS18464 xx.xx.xxx.xxx 0.0% 155 57.1 57.1 56.5 58.8 0.3
115 天前 回复了 htfcuddles 创建的主题 › 宽带症候群 › 日本方向目前联通最好的线路是哪一个？ |
@htfcuddles 10099 应该是要海外运营商花钱 peer 的 不 peer 不会在 10099 广播路由的
116 天前 回复了 htfcuddles 创建的主题 › 宽带症候群 › 日本方向目前联通最好的线路是哪一个？ |
CUG AS10099 在日本有 pop 这应该是联通的最优线路吧
130 天前 回复了 gz1988 创建的主题 › 宽带症候群 › 北京联通家宽，你们光猫有 IPv6 防火墙吗？ |
北京联通 fttr ipv6 防火墙有。 找联通 让他们找光猫厂商的人下发配置关掉了
156 天前 回复了 hfl1995 创建的主题 › Apple › iOS 18 最难受的 BUG |
我这边升级了 3 台设备， 三台设备都遇到了
159 天前 回复了 hfl1995 创建的主题 › Apple › iOS 18 最难受的 BUG |
ios18 还有个超级恶劣的 bug https://www.reddit.com/r/iOSBeta/comments/1dfegrc/ios_18_db1_system_data_keeps_writing_into_storage/
会持续写入硬盘，导致系统卡死
会持续写入硬盘，导致系统卡死
235 天前 回复了 PatrickLe 创建的主题 › 宽带症候群 › 内网 WireGuard 不支持域名地址，难不成每次都手动开启关闭吗？有没有优雅点的方式？ |
See: https://wiki.archlinux.org/title/WireGuard
After resolving a server's domain, WireGuard will not check for changes in DNS again.
If the WireGuard server is frequently changing its IP-address due DHCP, Dyndns, IPv6, etc., any WireGuard client is going to lose its connection, until its endpoint is updated via something like wg set "$INTERFACE" peer "$PUBLIC_KEY" endpoint "$ENDPOINT".
Also be aware, if the endpoint is ever going to change its address (for example when moving to a new provider/datacenter), just updating DNS will not be enough, so periodically running reresolve-dns might make sense on any DNS-based setup.
Luckily, wireguard-tools provides an example script /usr/share/wireguard-tools/examples/reresolve-dns/reresolve-dns.sh, that parses WG configuration files and automatically resets the endpoint address.
One needs to run the /usr/share/wireguard-tools/examples/reresolve-dns/reresolve-dns.sh /etc/wireguard/wg.conf periodically to recover from an endpoint that has changed its IP.
One way of doing so is by updating all WireGuard endpoints once every thirty seconds[6] via a systemd timer:
/etc/systemd/system/wireguard_reresolve-dns.timer
[Unit]
Description=Periodically reresolve DNS of all WireGuard endpoints
[Timer]
OnCalendar=*:*:0/30
[Install]
WantedBy=timers.target
/etc/systemd/system/wireguard_reresolve-dns.service
[Unit]
Description=Reresolve DNS of all WireGuard endpoints
Wants=network-online.target
After=network-online.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c 'for i in /etc/wireguard/*.conf; do /usr/share/doc/wireguard-tools/examples/reresolve-dns/reresolve-dns.sh "$i"; done'
Afterwards enable and start wireguard_reresolve-dns.timer
After resolving a server's domain, WireGuard will not check for changes in DNS again.
If the WireGuard server is frequently changing its IP-address due DHCP, Dyndns, IPv6, etc., any WireGuard client is going to lose its connection, until its endpoint is updated via something like wg set "$INTERFACE" peer "$PUBLIC_KEY" endpoint "$ENDPOINT".
Also be aware, if the endpoint is ever going to change its address (for example when moving to a new provider/datacenter), just updating DNS will not be enough, so periodically running reresolve-dns might make sense on any DNS-based setup.
Luckily, wireguard-tools provides an example script /usr/share/wireguard-tools/examples/reresolve-dns/reresolve-dns.sh, that parses WG configuration files and automatically resets the endpoint address.
One needs to run the /usr/share/wireguard-tools/examples/reresolve-dns/reresolve-dns.sh /etc/wireguard/wg.conf periodically to recover from an endpoint that has changed its IP.
One way of doing so is by updating all WireGuard endpoints once every thirty seconds[6] via a systemd timer:
/etc/systemd/system/wireguard_reresolve-dns.timer
[Unit]
Description=Periodically reresolve DNS of all WireGuard endpoints
[Timer]
OnCalendar=*:*:0/30
[Install]
WantedBy=timers.target
/etc/systemd/system/wireguard_reresolve-dns.service
[Unit]
Description=Reresolve DNS of all WireGuard endpoints
Wants=network-online.target
After=network-online.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c 'for i in /etc/wireguard/*.conf; do /usr/share/doc/wireguard-tools/examples/reresolve-dns/reresolve-dns.sh "$i"; done'
Afterwards enable and start wireguard_reresolve-dns.timer
Select Language