cavivie

I'd love to, but before that, can you add more about tun in ss, including unresolved problems and known problems and goals.

Thank you for your description. I think I will take time to integrate it recently.

Ah, ah, first of all, I'm sorry for the reason why I've been busy recently. I want to disassemble the current steps here: 1. > Shall we extract the logic...

> [forward_lwip](https://github.com/VendettaReborn/netstack-smoltcp/blob/auto-detect-interface/examples/forward_lwip.rs) && [forward_smoltcp](https://github.com/VendettaReborn/netstack-smoltcp/blob/auto-detect-interface/examples/forward_smoltcp.rs). I compared smoltcp with lwip on their basic proxy mechanism, and found that the netstack-smoltcp may not work well on ipv6 (lwip is good) I think...

For now, this means we can further work on IPv6 code. Nonetheless, this also seems to mean that the support of the ipv6 part of the smoltcp crate is not...

Here is a pic that some of simple tcp tests shared. `rust-tun` does not currently support ipv6, I want to do something about `rust-tun`'s shortcomings in ipv6 in the near...

> for the outbound handlers, we have the docker test suites, which will cover tcp&udp. For tun, we haven't figure out some good ways to test it on both ipv4...

>a separate crate What I mean is that we may need to use the `rust-tun` patch first, and then merge some patches about ipv6 into `rust-tun` upstream if possible.