lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191119.163923.660983355933809356.davem@davemloft.net>
Date:   Tue, 19 Nov 2019 16:39:23 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     wenxu@...oud.cn
Cc:     pablo@...filter.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ip_gre: Make none-tun-dst gre tunnel keep
 tunnel info

From: wenxu@...oud.cn
Date: Tue, 19 Nov 2019 15:08:51 +0800

> From: wenxu <wenxu@...oud.cn>
> 
> Currently only collect_md gre tunnel keep tunnel info.
> But the nono-tun-dst gre tunnel already can send packte through
> lwtunnel.
> 
> For non-tun-dst gre tunnel should keep the tunnel info to make
> the arp response can send success through the tunnel_info in
> iptunnel_metadata_reply.

I know that English is not your native language, but there are many
typos in here and I do not understand from your description how all
of this works and what needs to be fixed.

Please try explain things more clearly, showing how collect_md works
for these tunnel types, exactly, compared to non-tun-dst tunnels.

Thank you.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ