Description of problem: Version-Release number of selected component (if applicable): vpnc-0.5.3-15.svn457.fc18.x86_64 How reproducible: Steps to Reproduce: 1. connect to a vpn 2. wait 1 hour 3. get disconnected Actual results: All works fine exactly one hour an the connection is closed after that Expected results: Unlimited connection time Additional info: People using the windows client never get disconnected, so that why I think that the problem is on client side. Some error logs : 10:23:08 localhost NetworkManager[558]: <info> Starting VPN service 'vpnc'... Feb 1 10:23:08 localhost NetworkManager[558]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 3008 Feb 1 10:23:08 localhost NetworkManager[558]: <info> VPN service 'vpnc' appeared; activating connections Feb 1 10:23:08 localhost NetworkManager[558]: <info> VPN plugin state changed: starting (3) Feb 1 10:23:08 localhost NetworkManager[558]: <info> VPN connection 'Palo Alto' (Connect) reply received. Feb 1 10:23:08 localhost NetworkManager[558]: <warn> /sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring... Feb 1 10:23:09 localhost NetworkManager[558]: <info> VPN connection 'Palo Alto' (IP4 Config Get) reply received from old-style plugin. Feb 1 10:23:09 localhost NetworkManager[558]: <info> VPN Gateway: ***.***.***.*** Feb 1 10:23:09 localhost NetworkManager[558]: <info> Tunnel Device: tun0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> IPv4 configuration: Feb 1 10:23:09 localhost NetworkManager[558]: <info> Internal Address: 10.120.64.78 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Internal Prefix: 32 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Internal Point-to-Point Address: 10.120.64.78 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Maximum Segment Size (MSS): 0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 10.10.10.11/32 Next Hop: 10.10.10.11 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 10.10.10.12/32 Next Hop: 10.10.10.12 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 10.120.0.0/16 Next Hop: 10.120.0.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 10.210.0.0/16 Next Hop: 10.210.0.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 172.29.230.0/23 Next Hop: 172.29.230.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 172.31.1.0/24 Next Hop: 172.31.1.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 172.31.2.0/23 Next Hop: 172.31.2.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 192.168.0.0/23 Next Hop: 192.168.0.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 192.168.2.0/24 Next Hop: 192.168.2.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 192.168.20.0/22 Next Hop: 192.168.20.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 192.168.24.0/23 Next Hop: 192.168.24.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 192.168.28.0/22 Next Hop: 192.168.28.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 172.31.4.0/22 Next Hop: 172.31.4.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Static Route: 172.31.8.0/21 Next Hop: 172.31.8.0 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Forbid Default Route: yes Feb 1 10:23:09 localhost NetworkManager[558]: <info> Internal DNS: 192.168.0.11 Feb 1 10:23:09 localhost NetworkManager[558]: <info> Internal DNS: 192.168.0.13 Feb 1 10:23:09 localhost NetworkManager[558]: <info> DNS Domain: '(none)' Feb 1 10:23:09 localhost NetworkManager[558]: <info> No IPv6 configuration Feb 1 10:23:10 localhost NetworkManager[558]: <info> VPN connection 'Paolo Alto' (IP Config Get) complete. Feb 1 10:23:10 localhost NetworkManager[558]: <info> Policy set 'Système em1' (em1) as default for IPv4 routing and DNS. Feb 1 10:23:10 localhost NetworkManager[558]: <info> VPN plugin state changed: started (4) .... Feb 1 11:23:08 localhost vpnc[3010]: connection terminated by peer Feb 1 11:23:08 localhost avahi-daemon[521]: Withdrawing workstation service for tun0. Feb 1 11:23:08 localhost NetworkManager[558]: VPNC started in foreground... Feb 1 11:23:08 localhost NetworkManager[558]: <info> VPN plugin state changed: stopped (6) Feb 1 11:23:08 localhost NetworkManager[558]: <info> VPN plugin state change reason: 0 Feb 1 11:23:08 localhost avahi-daemon[521]: Withdrawing address record for 10.54.136.68 on em1. Feb 1 11:23:08 localhost avahi-daemon[521]: Leaving mDNS multicast group on interface em1.IPv4 with address 10.54.136.68. Feb 1 11:23:08 localhost avahi-daemon[521]: Interface em1.IPv4 no longer relevant for mDNS. Feb 1 11:23:08 localhost avahi-daemon[521]: Joining mDNS multicast group on interface em1.IPv4 with address 10.54.136.68. Feb 1 11:23:08 localhost avahi-daemon[521]: New relevant interface em1.IPv4 for mDNS. Feb 1 11:23:08 localhost avahi-daemon[521]: Registering new address record for 10.54.136.68 on em1.IPv4. Feb 1 11:23:09 localhost NetworkManager[558]: <info> Policy set 'Système em1' (em1) as default for IPv4 routing and DNS. Feb 1 11:23:09 localhost NetworkManager[558]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Feb 1 11:23:09 localhost NetworkManager[558]: <warn> (4) failed to find interface name for index Feb 1 11:23:09 localhost NetworkManager[558]: nm_system_iface_flush_routes: assertion `iface != NULL' failed Feb 1 11:23:09 localhost NetworkManager[558]: <warn> (4) failed to find interface name for index Feb 1 11:23:13 localhost NetworkManager[558]: <info> VPN service 'vpnc' disappeared (for real it stoped working arround 11:20) I recompiled and install the client for the lastest svn because here they said it was fixed : https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/479632 but I still get disconnected after one hour. If it can help here : http://ubuntuforums.org/showthread.php?t=1560756 some one said that the disconnection "coincides with the rekeying interval (3600 seconds) in the PIX firewall". Sorry for all the ubuntu links, but this problem is very annoying for me I need to re launch my all ssh connection every hours. thanks
Yes, this is driving me nuts. I just updated from F16 to F18. F16 had no problems with VPN disconnecting but F18 does. I see the exact same behavior as above. I am actively working when the connection fails each hour, so all the recommendations online about a 'keep-alive' script seem bogus as a fix for this problem. Please fix this. This patch claims to fix this problem: http://www.gossamer-threads.com/lists/vpnc/devel/3442
The patch here seem to already be in the svn, but the rpm for fedora is quite old and doesnt has it. Maybe a first step, would be to provide an updated version of the package, the current version is based on svn457 (2011-01-27) when the head is version 517 (2012-04-21). (btw for my problem I tried to compile from source but it didn't worked better)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.