netdev - Re: Figuring out how vti works

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]

Date:	Thu, 18 Sep 2014 11:06:23 +0200
From:	Steffen Klassert <steffen.klassert@...unet.com>
To:	Joe M <joe9mail@...il.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Figuring out how vti works

On Wed, Sep 17, 2014 at 06:04:07PM -0500, Joe M wrote:
> 
> master# echo "1" | sudo tee /proc/sys/net/ipv4/ip_forward
> 1
> master# modprobe ip_vti
> master# ipsec start
> Starting strongSwan 5.2.0 IPsec [starter]...
> master# ip tunnel add vtil mode vti local 192.168.0.11 remote
> 192.168.1.232 ikey 1 okey 1
> master# ip link set vtil up
> master# sleep 60
> master# ip route add 192.168.1.0/24 dev vtil
> master# ip xfrm state
> src 192.168.0.11 dst <client or alice or bnglr public ip>

Not sure what <client or alice or bnglr public ip> is,
but dst must match the remote tunnel endpoint i.e.
192.168.1.232 in your case.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html