On Mon, Mar 10, 2014 at 4:48 AM, Radu Radutiu wrote:
> Both servers are directly connected to Internet so NAT should not be
> enabled. I've tried to upgrade again and noticed that pluto keeps dying and
> restarting ervery 30 seconds (just enough for the other VPNs to connect).
>
Correct, they do
Both servers are directly connected to Internet so NAT should not be
enabled. I've tried to upgrade again and noticed that pluto keeps dying and
restarting ervery 30 seconds (just enough for the other VPNs to connect).
Here is the log from the old (working) openswan version when connecting to
Cisc
On Fri, Mar 7, 2014 at 9:56 AM, Radu Radutiu wrote:
> Does anyone else noticed problems after updating openswan to
> openswan-2.6.32-27.2.el6_5.i686 ? In our case a connection to Cisco VPN
>
https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&content=openswan&no_redirect=1&order=changedd
From: Radu Radutiu
> Does anyone else noticed problems after updating openswan to
> openswan-2.6.32-27.2.el6_5.i686 ?
Not the solution but here is what was fixed:
# rpm -qp --changelog openswan-2.6.32-27.2.el6_5.x86_64.rpm
* Thu Feb 06 2014 Paul Wouters - 2.6.32-27.2
- Resolves: rhbz#1050337 (
Does anyone else noticed problems after updating openswan to
openswan-2.6.32-27.2.el6_5.i686 ? In our case a connection to Cisco VPN
3000 Series would no longer work. I can see in the log an ASSERTION FAILED
error and the connection would remain in Pending phase 2.
Mar 7 16:24:40 firewall pluto[
5 matches
Mail list logo
