Vigilans

我打算在`dnspod-shell`里curl对应位置加入`-k`参数来与wget的`--no-check-certificate`选项对应，这样可以修复`dnspod-shell`在你的机器上的工作。 @withero 如果你打算修curl在你的padavan固件上的问题，可以参考下这个帖子 https://serverfault.com/questions/485597/default-ca-cert-bundle-location ，试着找一下curl尝试使用了哪里的证书文件。有两种似乎可行的方案： * `curl -v https://baidu.com`, curl可能会打印`CAfile`的位置，我这边是： ``` # curl -v https://www.baidu.com * Trying 36.152.44.95:443... * Connected to www.baidu.com (36.152.44.95) port 443 (#0) * ALPN, offering http/1.1...

@withero BusyBox的wget里没有手动指定证书的选项(`--ca-certificates`)； 一些嵌入式设备里可能没有/etc/ssl/certs； 以上等等因素考虑起来，相比直接取消CA证书检查，写一个适用所有情况的HTTPS网络请求函数要麻烦不少。 不过考虑到不检查CA证书总归是不好的，按你说的尝试手动指定一下证书位置确实还是可以考虑。

I decide to extend the router to achieve both goals in this PR (how to derive the target IP) and @dyhkwong desires (controlling the destination to use). Following new settings...

I've rebased it to the master branch.

Are there suggestions for why this PR is closed? I may refer to this PR for PacketAddr support to dokodemo inbound.

> I'm shocked that there hasn't been more responses to this, but not being able to sort and see most recent replies at the top like Outlook is an absolute...

It's a year now and still not fixed nor getting any attention. The author has described the issue clearly and has proposed clear fix for it. Another related issue: https://github.com/devplayer0/docker-net-dhcp/issues/29

According to https://github.com/microsoft/vscode/issues/138525#issuecomment-1847679100, diff editor has its own resource url `git:/...` or `gitlens:/...`, so can be specified to use default editor view in `workbench.editorAssociations`: ```json "workbench.editorAssociations": { "{git,gitlens}:/**/*.{md,csv}": "default" },...

Ref https://github.com/cweijan/vscode-office/issues/183#issuecomment-1879592003: > According to https://github.com/microsoft/vscode/issues/138525#issuecomment-1847679100, diff editor has its own resource url `git:/...` or `gitlens:/...`, so can be specified to use default editor view in `workbench.editorAssociations`: > > ```json...

Since this is a draft PR introducing `packetstream`, I'd leave here some draft thoughts on `packetaddr`. I think usage of `packetaddr` in inbound should be moved to dispatcher. This is...