strongSwan

15.09.2020

13:47 strongSwan Issue #3563: Route-based VPN - remote TS 0.0.0.0/0.0.0.0

You can close the issue.

13:37 strongSwan Issue #3563: Route-based VPN - remote TS 0.0.0.0/0.0.0.0

I added route to the remote side address and then it is possible to change default gw to ipsec3....

12:43 strongSwan Issue #3563: Route-based VPN - remote TS 0.0.0.0/0.0.0.0

So it is not possible to use remote TS 0.0.0.0/0.0.0.0 in route-based IPsec? It works in policy-based IPsec. In that ...

12:29 strongSwan Issue #3563: Route-based VPN - remote TS 0.0.0.0/0.0.0.0

It cannot be added route 0.0.0.0/0.0.0.0 to ipsecX......

12:09 strongSwan Issue #3563 (Closed): Route-based VPN - remote TS 0.0.0.0/0.0.0.0

There is a mention in documantation about route-based ipsec that it is possible to use 0.0.0.0/0.0.0.0 as local/remot...

21.07.2020

11:30 strongSwan Issue #3496: Route-based VPN - transport mode

Could you guide me a little?
The rule table ID 219 is OK? Or should I use something like 1000X?
Should I add some...

17.07.2020

10:05 strongSwan Issue #3496: Route-based VPN - transport mode

Responder:...

16.07.2020

13:59 strongSwan Issue #3496: Route-based VPN - transport mode

Connections are established on both sides now. But ping does not go through... I see some dropped packets....

10:13 strongSwan Issue #3496: Route-based VPN - transport mode

I am able to create a new table but I am not sure what table number should be set. Or it does not depend on it?

29.06.2020

11:43 strongSwan Issue #3496: Route-based VPN - transport mode

We use strongswan on an embedded device (industrial routers) which have a web user interface for setup. So customer d...