Hibernate works fine for me - I only ever re-boot to see how Windows is getting on! - but I notice that I always lose connection to machines I link to with OpenVPN when coming out of hibernation.
This doesn't really worry me, but I just wondered if it is caused by my failure to include some package?
I should say that I am running Fedora-12/KDE.
On Sat, 20 Mar 2010 14:50:24 +0000 Timothy Murphy gayleard@eircom.net wrote:
Hibernate works fine for me - I only ever re-boot to see how Windows is getting on! - but I notice that I always lose connection to machines I link to with OpenVPN when coming out of hibernation.
More or less because the remotes destroy the connections on their end when your client fails to respond (probably to keep alive requests).
Your client only detects that after coming out of hibernation, of course, and there isn't much that you can't do except maybe enabling some sort of auto-connection to the remotes when the client detects a connection failure.
Cheers
F
Timothy Murphy gayleard@eircom.net wrote:-
I only ever re-boot to see how Windows is getting on! -
Oh, you needn't concern yourself. Laden with viruses and End-User License Agreements as always.
but I notice that I always lose connection to machines I link to with OpenVPN when coming out of hibernation.
With all the kernels that I've tried under both F10 and and F11, I have been unable to get the network to function after coming out of hibernation. No amount of monkeying with ifconfig or restarting /etc/init.d/network will fix it. I finally gave up on hibernation and just shut down completely.
I'm planning to try Tux on Ice sometime soon, but haven't gotten around to it yet.
Don Quixote
On 3/22/10, Don Quixote de la Mancha quixote@dulcineatech.com wrote:
With all the kernels that I've tried under both F10 and and F11, I have been unable to get the network to function after coming out of hibernation. No amount of monkeying with ifconfig or restarting /etc/init.d/network will fix it. I finally gave up on hibernation and just shut down completely.
Have you tried pm-suspend? Or is that not an option for some reason? I ask this because I've had problems with pm-hibernate on F12, but pm-suspend works fine.
Andras
François Cami wrote:
Hibernate works fine for me - I only ever re-boot to see how Windows is getting on! - but I notice that I always lose connection to machines I link to with OpenVPN when coming out of hibernation.
More or less because the remotes destroy the connections on their end when your client fails to respond (probably to keep alive requests).
OK, thanks, that sounds reasonable. As you say, I should be able to automate re-connection.
On Mon, 2010-03-22 at 00:15 +0100, Andras Simon wrote:
I've had problems with pm-hibernate on F12, but pm-suspend works fine.
This is going to depend on a lot of factors, such as what motherboard/chipset you have, what software you are running, which kernel version you have, etc. Hibernate/suspend in Linux is a moving target.
On my systems (one desktop and one laptop with up-to-date F12) both hibernate and suspend work quite well. I have another desktop at work with Ubuntu, and hibernate/suspend works quite well on that one too. Not all software recovers gracefully however. For example, I added a script that kills all ssh sessions on hibernate or suspend, because they never survive across a hibernate/suspend and then I have a bunch of dead windows that I have to manually close. Killing all ssh sessions on hibernate/suspend avoids having all the dead windows on wakeup.
Related to the original topic, I use an ipsec-tools style VPN, and it recovers automatically on wakeup. It was a pain to get configured and working to start with, but once in place, it is virtually automatic using certificates to authenticate.
--Greg
Timothy Murphy wrote:
Hibernate works fine for me - I only ever re-boot to see how Windows is getting on! - but I notice that I always lose connection to machines I link to with OpenVPN when coming out of hibernation.
This doesn't really worry me, but I just wondered if it is caused by my failure to include some package?
I should say that I am running Fedora-12/KDE.
My experience is that resume in Fedora simply doesn't work for network connections, because the logic is ass backwards. The VPN or NFS connections *seem* to be tried before the network connections are restored. If I have a an NFS "soft" mount, I can take the server down, put it in my car, drive it to the new data center, and install it, and the mount survives. Let me hibernate long enough to walk from an office to a meeting room and everything is dropped.
This amuses people using Windows.
I don't have the problem with the new 2.6.32 FC12 kernel, it never wakes from suspend or hibernate on any of my laptops. 2.6.33-ck1 works flawlessly, but still drops the network mounts.
I suggested using automount to a client, he says it works, but I haven't used it myself. Wouldn't help your VPN case, though.
Tuxonice may well solve the network problem, if not tell Nigel, stuff there gets fixed. Wish there were an rc.resume file, users could fix stuff like this.
Greg Woods wrote:
Related to the original topic, I use an ipsec-tools style VPN, and it recovers automatically on wakeup.
I'm not sure what this means. What did you do, exactly?
It was a pain to get configured and working to start with, but once in place, it is virtually automatic using certificates to authenticate.
On Mon, 2010-03-22 at 21:43 +0000, Timothy Murphy wrote:
Greg Woods wrote:
Related to the original topic, I use an ipsec-tools style VPN, and it recovers automatically on wakeup.
I'm not sure what this means. What did you do, exactly?
To fully answer this question would be a major research project, since it has been an ongoing project for several years and I have never really documented everything I did. But basically it involves installing the ipsec-tools package, creating a racoon.conf file on each end, generating a cert for the server and client (and installing them on each side), and generating an appropriate config file for "setkey" to route traffic through the tunnel. Cert authentication can happen with no intervention, the tunnel is set up inside the kernel automatically. The racoon daemon is only for doing the session key negotiation (IKE).
Complicating this has been dealing with one of the clients being behind a NAT box, the NAT box itself having a dynamic IP address, etc. But it works reliably and it comes up automatically on resume.
You can start with the ipsec-tools home page at:
http://ipsec-tools.sourceforge.net/
--Greg
I have a strange problem with NetworkManager since yesterday. I was connected through WIFI all the afternoon. At some point I got many:
NetworkManager: <WARN> nm_call_store_remove(): Trying to remove a non-existant call id.
Still the network worked. Then I rebooted the computer, and since then NetworkManager just states "Networking disabled" with no possible action. Enquiring, it seems that I have some dbus service that disappeared (don't ask I do not know why).
Both the files /usr/share/dbus-1/system-services/org.freedesktop.NetworkManagerSystemSettings.service and /usr/sbin/nm-sttings have disappeared (provided they exist of Fedora 12, my reference system is a Fedora 10 one).
My problem is that those two file do not belong to any rpm ?? How can I restore them ??
Is it normal to have such important files (or actually any file at all) not dealt with rpm ?? In my (probably simplistic) view, every non-generated system file should be assigned to an rpm...
Thank's for any help.
Theo.
On 03/23/2010 01:21 PM, Theodore Papadopoulo wrote:
My problem is that those two file do not belong to any rpm ?? How can I restore them ??
Is it normal to have such important files (or actually any file at all) not dealt with rpm ?? In my (probably simplistic) view, every non-generated system file should be assigned to an rpm...
To reply to myself. Those files are in the rpm NetworkManager in fedora 10 (wrong option in rpm -q). But I removed and re-installed those packages (in Fedora 12) and they have not been installed. There is cleraly something I do not understand...
Theo.
On 03/23/2010 01:30 PM, Theodore Papadopoulo wrote:
On 03/23/2010 01:21 PM, Theodore Papadopoulo wrote:
My problem is that those two file do not belong to any rpm ?? How can I restore them ??
Is it normal to have such important files (or actually any file at all) not dealt with rpm ?? In my (probably simplistic) view, every non-generated system file should be assigned to an rpm...
To reply to myself. Those files are in the rpm NetworkManager in fedora 10 (wrong option in rpm -q). But I removed and re-installed those packages (in Fedora 12) and they have not been installed. There is cleraly something I do not understand...
Theo.
To reply once more to myself, I finally found the problem and it has little to do with the above... The cure was:
rm /var/lib/NetworkManager/NetworkManager.state
For some reason, this file was containing something like: [main] NetworkingEnabled=false WirelessEnabled=false WWANEnabled=false
This setup was surviving to every reboot or restart of NetworkManager and I do not know who plugged this settings there. Suppressing the file and restarting NetworkManager cured all my troubles.
All the best.
Theo.