feat(tun): windows auto-route #561
Conversation
|
实测能通吗？windows api那部分实在是看不懂 |
|
通。那部分别看了直接看cmd的吧。留着以后知道啥原因修好了再用那个。 |
|
别修了吧，感觉没啥用，微软的文档都不全 |
clash_lib/src/proxy/tun/inbound.rs
Outdated
| IpNet::new(std::net::IpAddr::V4(Ipv4Addr::new(128, 0, 0, 0)), 1) | ||
| .unwrap(), | ||
| ]; | ||
| for r in default_routes { |
There was a problem hiding this comment.
shall we make this a two step operation of build_routes & add_routes, thus is can be separated into the routes module
There was a problem hiding this comment.
i'm hoping the 0/1 and 128/1 can work on all platforms so the build_route will just be the same 2 entries
| /// https://learn.microsoft.com/en-us/windows/win32/rras/add-and-update-routes-using-rtmaddroutetodest | ||
| /// FIXME: figure out why this doesn't work https://stackoverflow.com/questions/43632619/how-to-properly-use-rtmv2-and-rtmaddroutetodest | ||
| #[allow(dead_code)] | ||
| pub fn add_route_that_does_not_work( |
There was a problem hiding this comment.
this is how net-route handled the routing table: https://github.com/johnyburd/net-route/blob/f83a447bd13404225c8a78db71af208ee8e7885c/src/platform_impl/windows.rs#L178. it seems that they took a different approach
There was a problem hiding this comment.
yeah i checked their code they used a different set of API. which makes sense. maybe I'll switch to using the crate for this too when I do the macos one
🤔 This is a ...
🔗 Related issue link
#559
💡 Background and solution
https://learn.microsoft.com/en-us/windows/win32/rras/add-and-update-routes-using-rtmaddroutetodest
📝 Changelog
☑️ Self-Check before Merge