[Openswan Users] Interpreting "no connection is known" (FreeSwan 1.97)
bob at computerisms.ca
Sun Jun 9 23:31:44 UTC 2013
> The other end of the site-site VPN is the same hardware, but I did a
> firmware upgrade at some point. pluto reports Openswan 2.6.20dr2 but
> I'm not having any better luck.
The newer version should make a significant difference. This is still a
fairly old version, but much much newer than the previous.
> I've tried several versions of virtual_private, such as
> 000 virtual_private (%priv):
> 000 - allowed 0 subnets:
> 000 - disallowed 0 subnets:
> 000 WARNING: Either virtual_private= was not specified, or there was a
> 000 error in that line. 'left/rightsubnet=%priv' will not
You need to use the virtual_private line to exclude your local subnet.
This config will allow any connection from any non-routable subnet, but
if that subnet is the same as the subnet behind the vpn server, nothing
will know how to route between the two (different/same) networks. for
example, the subnet for my office lan is 192.168.25.0/24, so I need to
append "%v4:!192.168.25.0/24" to my virtual_private line to prevent any
remote users in that same subnet from connecting.
This topic has been discussed extensively on this list before, if you
need more info on how it works, I am sure you will be able to find a
> Users at lists.openswan.org
> Micropayments: https://flattr.com/thing/38387/IPsec-for-Linux-made-easy
> Building and Integrating Virtual Private Networks with Openswan:
More information about the Users