Closed xuezbot closed 8 months ago
请自行谷歌
请自行谷歌
很显然谷歌了也找不到一个示例,倒不如说singbox官网的示例本身就挺模棱两可的
{
"inbounds": [
{
"type": "naive",
"listen": "::",
"listen_port": 443,
"users": [
{
"username": "",
"password": ""
}
],
"tls": {
"enabled": true,
"certificate_path": "/root/fullchain.cer",
"key_path": "/root/private.key"
}
}
],
"outbounds": [
{
"type": "direct"
}
]
}
结合教程 https://github.com/chika0801/sing-box-examples/blob/main/wireguard.md 中的服务端示例
{ "inbounds": [ { "type": "naive", "listen": "::", "listen_port": 443, "users": [ { "username": "", "password": "" } ], "tls": { "enabled": true, "certificate_path": "/root/fullchain.cer", "key_path": "/root/private.key" } } ], "outbounds": [ { "type": "direct" } ] }
结合教程 https://github.com/chika0801/sing-box-examples/blob/main/wireguard.md 中的服务端示例
谢谢你的回答,链是链到了,但我不是这意思,socks入站,出站是socks-warp,也就是说把你提到的这个案例包起来再整个socks服务器
你把你现在发的配置中,出站是 "direct",你改成 wireguard.md 中 wireguard 那部分出站就是了。这样的操作你会吧?
有个naive 服务器,用singbox的话可以UDP over TCP,但那服务器IP不行,想套warp或者其它的socks,具体应该怎么搞。