-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AirPort Express returns "wrong" (different) IP to sleepproxyclient #5
Comments
Thanks for testing my sleepproxyclient. It seems the AirportExpress announced multiple IPs but should not be a problem in general... Please post the script-output too. |
|
It seems the AirPort Express announces the service via It might be also a good idea to check your AirPort Extreme configuration... |
it works if i check for atv2 port: 52442 instead of 63051. |
This looks almost perfect: The sleepproxyclient is working (indicated by Are you sure the sleepproxyclient is not working? (Sorry - I'm just unable to locate the problem...)
(Please note: the server-ports are not fixed. The port will/may change when rebooting the device) |
Sorry - I accidently closed the issue... |
A quick update: |
Hi Andreas, i am in the office and within the next days i'll have some christmas celebrations with friends, employer and so on...i'll get back to this on saturday/sunday. I have to test the actual setup with my workaround using the atv2s' IP... Nils |
ok - could not wait... i changed line 261 to:
That is the work around for the above error. Now im running into another problem! When ATV2 is not powered the client sleeps as expected. When its powered on: it wakes up... Greets Nils |
This seems to be somehow unrelated to this issue but it would be great to get a network dump to be able to investigate this new issue. |
Hi,
im running ubuntu server 12.10 64 bit and installed sleepproxyclient.
Calling the the sleepproxyclient.sh returns an error:
my airportexpress has got following IP: 192.168.178.XX
The sleepproxyserver publishes a different IP: 169.XXX.....
sleepproxyclient.sh sends data to my AirPortExpress (169.XXX....) and it answers from 192.168.178.XX.
This turns into an error and the script breaks.
I used a workaround and use my Apple TV2 as sleepproxyserver. I hardcoded a port-check for the sleepproxy. The ATV2 port differs from the airportexpress port...
ATV2 publishes its own correct IP in the usual style: 192.168.178.XX.
So its an issue due to apples airportexpress behaviour publishing the sleepproxy IP...
any thoughts how to handle the situation?
greets
nils
The text was updated successfully, but these errors were encountered: