Wireguard inbound: Fix context sharing problem

[yuhan6665]

#4030

Please take a look @Fangliding

[Fangliding]

其实把content附加回去就行了 之前剥掉content导致嗅探模块没读到嗅探请求导致的嗅探不生效 我没动是因为这样仍然无法解决inbound share

[yuhan6665]

其实把content附加回去就行了 之前剥掉content导致嗅探模块没读到嗅探请求导致的嗅探不生效 我没动是因为这样仍然无法解决inbound share

I thought it should be safe to share inbound object and content object, since they just contain inbound configuration and not mutated. We just need to make sure the outbound object are segregated. Would it work?

[Fangliding]

inbound的source会翻转

[Fangliding]

content的attributes甚至会并发写导致panic

[Fangliding]

session包里有一个deep clone outbound和content的 用那个就能解决问题了 只是inbound解决不了

[yuhan6665]

I see.. looks like we need to find some id between the input of the tun and output of the tun and pass the correct context.

[yuhan6665]

@Fangliding inbound 浅拷贝一下 用上 tun 出口的地址作为 source 你看行不 我之后再梳理一下 context 的用法。。

[Fangliding]

@Fangliding inbound 浅拷贝一下 用上 tun 出口的地址作为 source 你看行不 我之后再梳理一下 context 的用法。。

那也没法正确反映source啊

[yuhan6665]

我大概看了一下 gvisor ForwarderRequest 无法简单的跟主连接 context 关联 目前先这样吧