Hi,
But out of the 2 tunnels only 1 is reachable. The other one doesn't ping.
Does that tunnel work if you don't establish the other one?
No, it doesn't.
Besides, once the 192.168.3.0/24 host is behind the NAT'ed gateway, neither of
the tunnels work.
Also, I'd try to disable IPComp for
Hi,
The configuration is quite classical: net-to-net ( 192.168.3.0/24 ===
192.168.4.0/24 )
msc-hmnet{5}: INSTALLED, TUNNEL, ESP SPIs: c5329687_i c0101bc4_o, IPCOMP
CPIs: dcf5_i ab46_o
But out of the 2 tunnels only 1 is reachable. The other one doesn't ping.
[root@academ strongswan]#
Hello,
We are migrating from strongswan-4.5 to strongswan-5.1.1 and currently running
into the routing problems.
Could you help us to settle a weird situation with the strongswan-5.1.1, which
we built on the Centos 5.3 distribution?
The configuration is quite classical: net-to-net (
Hello,
We are migrating from strongswan-4.5 to strongswan-5.1.1 and currently running
into the routing problems.
Could you help us to settle a weird situation with the strongswan-5.1.1, which
we built on the Centos 5.3 distribution?
The configuration is quite classical: net-to-net (
Hello,
We are migrating from strongswan-4.5 to strongswan-5.1.1 and currently running
into the routing problems.
Could you help us to settle a weird situation with the strongswan-5.1.1, which
we built on the Centos 5.3 distribution?
The configuration is quite classical: net-to-net (
