iHsin
iHsin
> well isn't this mostly duplicating changes in #343 ? Yes i cherry pick [one commit](https://github.com/Watfaq/clash-rs/pull/362/commits/cb0f783e6cc95c7e1bbe963034c0f23d7f83f7cd) from #343. just for respect the proxy node specific mark and iface conf And...
> the clash.meta has this option in every outbound, including the outbound group. But so far, i think it's kinda useless. Agree as well, i cannot think of any use...
> Actually, i am thinking about re-using the shadowsocks-rust's infra: https://github.com/shadowsocks/shadowsocks-rust/blob/b37c6e4dfa13af7bc65b34606baa01e78927199e/crates/shadowsocks/src/net/option.rs#L47. They have done a great job in supporting the fwmark and bind_interface as well as other options across different...
I think we could merge this pr as a workaround for now. I could change those things if they don't match our need. @ibigbug @VendettaReborn
> any ideas about on how to test it? You mean unit test？ I dont have any idea. actually.
> I've went through the issue list of clash.meta, and one of the most frequently asked issue is about tun, and it even got routing loop in some conditions. So...
> @Itsusinn still planning to work on this ? Yes maybe another simplified edition of global mark
UPX actually increase memory usage by 50%. Unless in small-flash devices, there is no need for such small size binary.
我也赞成在 v11 定义额外的 trait 再于v11 impl 相应的代码 但是要怎么向v11用户隐藏 位于 https://github.com/abrahum/Walle-core/blob/042add1e8b250486dcf30fec5475e2029cc6fe94/src/app/bot.rs#L34-L38 的实现呢 是用cargo feature吗？
请问您有qq或者telegram吗？