Setting up network in the right way + wake on unicast messages.

[kjans]

Hi!
I have a Fedora server at home. I don't want it to be running all the time to reduce the power usage and be more green It only works , whet it is really needed. So when it is not in use (no ssh or http connections have been active for some time), a custom python script suspends it. I have set it to wake up on unicast messages, so when somebody connects to it, the server wakes up.
In Fedora 12 everything worked fine: when the server was sleeping and you connected to it using ssh or a web browser, the client waited for couple of seconds until the server was up and then connected (actually it worked even when server was turned off: the command "ssh [user]@[server]" just waited until server was booted up and then connected.)

Now I installed Fedora 13 on the server. When I try to connect to the server when it's sleeping, the client waits for some time (and server wakes up), then the connection just times out. When I try to connect again, it works. When server is up and running, I can connect to it. So when it is sleeping I have to connect twice: first to wake it up and then connect again to log in.
Do you have any ideas what is causing this problem, as it is really annoying for me and I don't want to have it running all the day.

Also, I have not set up the network in the best way, I think. To start the network at boot, i have put the command

ifup eth0

to /etc/rc.local.
To start the network when resurming from suspend, I have creted a script with the same command in /usr/lib64/pm-utils/sleep.d. It works, but it does not seam to be the *right* way to do this. Maybe this is also causing the first problem. So how have you managed to get a working network connection on your Fedora 13 headless server?

Hello,

I am not sure about your wake on lan issue but to have your eth0 up on boot just add "ONBOOT=yes" in /etc/sysconfig/network-scipts/ifcfg-eth0

Hope this Helps,

Ky

[kjans]

Network is working fine using the ONBOOT option, but the wake on lan problem is still there. Any ideas?

[kjans]

OK, I have made some testing and reading some log files and now it's clear that the main problem causing timeout is that server doesn't seem to get the ssh connection package. When I try to establish a ssh connection, the clients sends out the connection package (hello server, i am a client computer and I want to connect to you ). This package wakes server up, but server doesn't get it and will not respond. If server is already up and running everything works. Same problem exists with HTTP connection. So it appears to me that network is brought up too late, if it were brought up earlier, maybe it will accept the package. I know it is possible as it was working on Fedora 12. So any suggestions on what I have to do to make networking to come up earlier?

[GaussNiwre]

Hi there,

I'm new to using fedora (I used Gentoo before). I would like to have exactly the setup khans has but on fedora 15. Could you perhaps explain what are the necessary steps? I don't mind if I have to "ssh twice". The first step would be to get my box to suspend and then wake-on-lan. Eventually I would like it to suspend automatically after a period of no network activity (it is a headless NAS server anyway).

I have wake-on-lan (mode g, aka magic packet) activated at boot-time on my network device. And I also have pm-utils installed, although the later doesn't do anything after a pm-suspend command (btw, the pm scripts directories power.d and speep.d under /etc/pm are empty; is this normal?).

Any help appreciated. I'm happy but a bit confused with the switch from gentoo.

GaussNiwre