nimrodel50

Hi, For the s3 sleep script changing the line on the script solves the array monitoring but not sure how to keep on the config after reboot: from: array=($(grep -PB12 '^type="(Parity|Data)' $ini|grep -Po '^device="\K[^"]+')) to array=($(grep -PB13 '^type="(Parity|Data)' $ini|grep -Po '^device="\K[^"]+')) on the file /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep hope that helps someone.

New question, if I bond two network cards does the script should handle that right? Or do I must change something? Thanks

Thanks, I will try that.

Hi I keep having this on the log when I resume from sleep, I'm doing the avahidaemon restart. Jul 2 21:25:37 UnRaid avahi-daemon[16749]: Server startup complete. Host name is UnRaid.local. Local service cookie is 369886240. Jul 2 21:25:37 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:25:38 UnRaid avahi-daemon[16749]: Service "UnRaid-SMB" (/services/smb.service) successfully established. Jul 2 21:25:38 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:25:39 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:25:41 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:27:47 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:27:47 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:27:50 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:27:51 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:27:55 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:27:56 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:28:16 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:28:17 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:35:28 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:35:29 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:37:47 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:37:48 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. Jul 2 21:37:56 UnRaid avahi-daemon[16749]: Service name conflict for "%h" (/services/afp.service), retrying with "UnRaid #2". Jul 2 21:37:57 UnRaid avahi-daemon[16749]: Service "UnRaid" (/services/afp.service) successfully established. any clue? thanks.

Ok thanks I will try this, is it also good doing this before sleep?

I have a mixed windows and Mac system, normally if no windows is involved everything seems to work nicely, but when the windows send a wol packet to wake up the system (not using the sleep proxy server) the system is not able to register because the sleep proxy still thinks the machine is sleeping and the avahi registers my server as a new server adding a number at the end. For me it seems that the sleep proxy is no releasing the services or the name if I wake the system on a different way . Does it make sense? Thanks for your help

@awein when the system is waked up from a windows the machine name can't be registered with avahi and create a new name with the #2 at the end. Do you know if after the machine is waked up we need to unregistered from the sleep proxy? Thanks

I think finaly I got a solution using the script from https://github.com/awein/SleepProxyClient without any modification. First we need to install this packages: openssl-1.0.1c-i486-3.txz python-2.7.3-i486-2.txz python-netifaces-0.8-i486-1alien.tgz dnspython-1.10.0-i486-1alien.tgz they can be download from: http://slackware.cs.utah.edu/pub/slackware/slackware-14.0/slackware/ http://www.slackware.com/~alien/slackbuilds/ then we have to install manually this other package: IPy-0.75.tar.gz it is easy, once it is uncompressed on the pen drive the only thing you need to write on the go files is: cd IPy-0.75 phyton setup.py install That make the original script work, but it still take the wrong ip for my sleep proxy, for that I found a way to cheat the system, adding this routes to the go file seems to help. route add default dev eth0 metric 99 route add -net 169.254.0.0 netmask 255.255.0.0 dev eth0 metric 99 my sleep proxy is working since last thursday with out any problem.

I'm doing this by memory but something like that, just add a if to check if the ip is the fake one and then change it for the static ip you want. hope you get the idea. def discoverSleepProxies(interface): # discover all available Sleep Proxy Servers proxies = [] cmd = "avahi-browse --resolve --parsable --no-db-lookup --terminate _sleep-proxy._udp 2>/dev/null | grep '=;.*;IPv4;'" p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT) for line in p.stdout.readlines(): lineArr = line.rsplit(";") # check length if (len(lineArr) < 10) : p.terminate() break ip = lineArr[7] if (ip == "your fake ip"): ip= "your ip" port = lineArr[8] proxies.append({ "ip" : ip, "port" : port}) retval = p.wait() return proxies main()

With my Timecapsule it happens the same not detecting the right IP, So I decided to change the script to use the ip manualy, so when detects the wrong IP I replaced by the timecapsule static ip. Seems to work.