现有两个网口接入不同的网络，网络A带宽大、延迟高，网段为192.168.4.1；网络B带宽小、延迟低，网段为192.168.8.1想要日常流量走网络A，指定ip或ip段走网络B，可以通过配置路由表实现。网络接入计算机时，系统会默认为该网段添加一条路由表规则 0.0.0.0 （所有ipv4地址）转发 至接入网络的网关地址。多网口设备连接多个网络也是如此。但是他们的越点不同，当匹配到多个规则时系统会选择越点较低的那条规则windows通过route print命令可以查看系统路由表C:\Users\Administratorroute print===========================================================================接口列表 15...c4 83 4f 16 59 c3 ......Intel(R) I210 Gigabit Network Connection 12...00 0c 29 32 93 1c ......Intel(R) PRO/1000 MT Network Connection 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 11...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2===========================================================================IPv4 路由表===========================================================================活动路由:网络目标 网络掩码 网关 接口 跃点数 0.0.0.0 0.0.0.0 192.168.4.1 192.168.4.201 266 0.0.0.0 0.0.0.0 192.168.8.1 192.168.8.102 21其他规则....我这边的情况就是，系统添加了两条0.0.0.0 至对应两个网络的网关规则，流量通过两个网口获取的ip地址出口。我们需要做的是，删掉系统默认配置的0.0.0.0规则，添加0.0.0.0规则出口为网络A（192.168.4.1）,指定ip地址出口为网络B（192.168.8.1）删除默认路由规则route delete 0.0.0.0添加0.0.0.0路由规则至网络Aroute add 0.0.0.0 mask 0.0.0.0 192.168.4.1添加指定的ip出口为网络Broute add 42.194.134.128 mask 255.255.255.255 192.168.8.1以上命令执行后可通过route print查看规则是否添加成功可以在命令末尾追加-p 使配置永久生效。metric 10 指定越点为10示例route add 0.0.0.0 mask 0.0.0.0 主网关IP metric 10 -p我这边只是临时使用，加上电脑不关机，因此没有添加越点和永久生效最后的路由表C:\Users\Administratorroute print===========================================================================接口列表 15...c4 83 4f 16 59 c3 ......Intel(R) I210 Gigabit Network Connection 12...00 0c 29 32 93 1c ......Intel(R) PRO/1000 MT Network Connection 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 11...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2===========================================================================IPv4 路由表===========================================================================活动路由:网络目标 网络掩码 网关 接口 跃点数 0.0.0.0 0.0.0.0 192.168.4.1 192.168.4.201 11 42.194.134.128 255.255.255.255 192.168.8.1 192.168.8.102 21其他规则....这样就实现访问42.194.134.128时走的低延迟的网络B，其他流量走网络A实现大带宽访问互联网

因为屏幕大小限制，经常需要将Iframe页面在新标签页打开，因此开发一个扩展程序快速在新标签页打开IframeChrome扩展程序需要一个manifest.json用于定义一些基础数据manifest.json:{ "name": "Iframe In New Tab", "description": "Open iframe Page In New Tab Quickly", "version": "1.0", "manifest_version": 3, "action": { "default_popup": "popup.html", "default_icon": "newtab_16.png" }, "permissions": [ "contextMenus" ], "background": { "service_worker": "background.js", "type": "module" }, "icons": { "16": "newtab_16.png", "48": "newtab_48.png", "128": "newtab_128.png" }}需要注意action、permissions、backgroundaction定义安装扩展程序后，浏览器右上方扩展程序按钮相关行为，default_popup为点击扩展程序图标后对应的页面，因为我们程序没有交互，因此给出简单提示popup.html：htmlstyle html, body { min-width: 205px; min-height: 33px; } hr { width: 100%; }/stylebody h1/h1 p bIframe In New Tab/b br Right-click the iframe area for options. /p/body/htmlpermissions为该扩展程序需要的权限，我们的扩展程序需要在浏览器创建右键菜单，因此声明contextMenus扩展程序可以在后台通过扩展程序的"service worker"监听浏览器事件,background用于指定你的相关监听代码，我们会在这里监听扩展程序安装事件，为页面创建右键菜单，以及该菜单的点击事件background.js:// 注册扩展程序安装事件，会在扩展程序被安装、扩展程序更新、浏览器更新时执行chrome.runtime.onInstalled.addListener(function () { chrome.contextMenus.create({ id: "iframe_menu", title: 'Open In New Tab', type: 'normal', contexts: ['frame'] });});// 监听菜单点击事件chrome.contextMenus.onClicked.addListener((info, tab) = { if (info.menuItemId === "iframe_menu") { // 获取iframe的URL const frameUrl = info.frameUrl; if (frameUrl) { chrome.tabs.create({ url: frameUrl, index: tab.index + 1 }); } }});将以上代码及相关图片资源放入一个文件夹中，打开Chrome扩展程序页面，启用开发者模式后，点击加载已解压的扩展程序，即可使用扩展程序使用效果展示:[图片]完整源码:Github参考资料：Hello World extension

最新版chrome136禁用了默认--user-data-dir的调试功能，--user-data-dir的默认路径为C:\Users\dell\AppData\Local\Google\Chrome\User Data\Default以前只需要指定--remote-debugging-port=9222即可调试，现在需要额外指定--user-data-dir"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="C:\Chrome_data"vscode文档已经更新提示:if this flag isn't given, then the command will open a new window of any running browser and not enter debug mode更改了远程调试开关以提高安全性attaching-to-browsers

使用的旧版centos7系统导致使用let's Encrypt证书的网站无法访问，比如docker使用了cf的dns，会连接cf的registry。ab012f07497a: Waiting e0979c892644: Waiting error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/6a/6aedcda31f51881fd13e67674d84cd6661e278547dc7b23602672fb5a1f76ee4/data?expires=1744254640signature=S%2BTo9ZcvNHuuweoW7qCirv%2Fe9Uo%3Dversion=2: x509: certificate signed by unknown authority[root@13 ~]# curl -v https://xxx* About to connect() to xxx port 443 (#0)* Trying xxx...* Connected to xxx (xx) port 443 (#0)* Initializing NSS with certpath: sql:/etc/pki/nssdb* CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none* Server certificate:* subject: CN=xxx* start date: Apr 08 18:01:56 2025 GMT* expire date: Jul 07 18:01:55 2025 GMT* common name: xxx* issuer: CN=R11,O=Let's Encrypt,C=US* NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER)* Peer's Certificate issuer is not recognized.* Closing connection 0curl: (60) Peer's Certificate issuer is not recognized.More details here: http://curl.haxx.se/docs/sslcerts.html研究发现是系统信任的根证书过期导致需要更新ca-certificates程序包,更新ca-certificates程序包后会自动更新系统信任的根证书查看已安装的版本1.debian/ubuntu# 查看已安装版本dpkg -l ca-certificates | grep ^ii# 或直接提取版本号dpkg-query -W -f='${Version}' ca-certificates2.centos/RHEL# 查看已安装版本rpm -q ca-certificates# 或结合 yum 查看信息yum info ca-certificates | grep -E "Name|Version" [root@13 ~]# yum info ca-certificatesLoaded plugins: fastestmirrorRepodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fastDetermining fastest mirrors * elrepo-kernel: mirror.fcix.net * epel: irltoolkit.mm.fcix.netInstalled PackagesName : ca-certificatesArch : noarchVersion : 2015.2.6Release : 73.el7Size : 1.1 MRepo : installedFrom repo : anacondaSummary : The Mozilla CA root certificate bundleURL : http://www.mozilla.org/License : Public DomainDescription : This package contains the set of CA certificates chosen by the : Mozilla Foundation for use with the Internet PKI.Available PackagesName : ca-certificatesArch : noarchVersion : 2022.2.54Release : 74.el7_9Size : 911 kRepo : updates/7/x86_64Summary : The Mozilla CA root certificate bundleURL : http://www.mozilla.org/License : Public DomainDescription : This package contains the set of CA certificates chosen by the : Mozilla Foundation for use with the Internet PKI.发现已安装的是2015年的版本了更新ca-certificates# Debian/Ubuntusudo apt update sudo apt install --reinstall ca-certificates# CentOS/RHELsudo yum update ca-certificates# Fedorasudo dnf update ca-certificates# Alpine Linuxsudo apk update sudo apk add ca-certificates更新完成后应该就可以使用了，若不行可尝试执行手动更新update-ca-trustupdate-ca-trust force-enableupdate-ca-trust extractdocker需要重启才能生效参考：CentOS 7 更新根证书（root certificates）"docker pull" certificate signed by unknown authority