[kolla][wallaby][neutron][vpnaas]

Franck VEDEL franck.vedel at univ-grenoble-alpes.fr
Mon Jul 12 08:37:49 UTC 2021


Hi,

I come back with the same problem: vpnaas ok with victoria, does not work with wallaby.

Does anyone have a vpnaas that works with wallaby? on Centos?
If so, how can I debug this problem? Can you give me some hint ? 

thank you in advance
Franck VEDEL


> Le 9 juil. 2021 à 20:19, Franck VEDEL <franck.vedel at univ-grenoble-alpes.fr> a écrit :
> 
> Hello, and first excuse my English please… thanks a lot. I hope you will understand my problem.
> 
> I have a problem with the following configuration: kolla-ansible, centos, wallaby.
> I need the vpnaas service. 
> I create internal networks, configure these networks, the routers, and I create a vpnaas between two internal networks (2 cirros instances for example). 
> To the left; net1: 192.168.10.0/24 Right, net2: 192.168.20.0/24 VM 
> On the left: ping VM on the right (ex 192.168.20.30). The ping goes to the internet, it is handled by the default route on the router leaving net1.
> 
> I do the same with Victoria: it works. I am testing a VPN between net1 and an internal network behind a real network, behind a watchguard. With Victoria, it works. 
> With Wallaby, it doesn't work. 
> Neutron-l3-agent logs says: Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl ») 
> 
> Is there a bug in wallaby? 
> What could be the problem, the configuration and the hardware is the same, it works with victoria, not with wallaby. 
> 
> Thanks for your help. 
> 
> Franck 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210712/2505625d/attachment.html>


More information about the openstack-discuss mailing list