PDA

View Full Version : I'd like to file a bug report but I don't know where: Controller or Receiver ?



epoch1970
2008-10-02, 06:39
As said in the title, I bought a "Duet", and while I am getting more and more intimate with it, I don't know who goes wrong here, the Controller or the Receiver.
The problem is simple: the Duet in bridged mode does not wake my SC server. It never did.

Isn't the *Receiver* supposed to send the WOL packets over the network ? I see bugs filed (and resolved...) about the Controller being able to send WOL packets but nothing much about the Receiver.

Anyone in bridged mode with a server that wakes-up ? Is this issue in the radar already ?

This is a test trace:

1) Setup a listening host on my lan sudo tcpdump -vvv -x -i 1 -n -t -l -s 256 "(multicast or broadcast) and udp"
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 256 bytes

2) Sleep SC 7.2 server, music playing.

3) On some host: wol -vvv 00:17:31:38:46:c8
Waking up 00:17:31:38:46:c8 with 255.255.255.255:40000...

Reads this on listening host:
IP (tos 0x0, ttl 64, id 5955, offset 0, flags [none], proto: UDP (17), length: 130) 192.168.1.198.56406 > 255.255.255.255.40000: [udp sum ok] UDP, length 102
0x0000: 4500 0082 1743 0000 4011 a0ba c0a8 01c6
0x0010: ffff ffff dc56 9c40 006e 4295 ffff ffff
0x0020: ffff 0017 3138 46c8 0017 3138 46c8 0017
0x0030: 3138 46c8 0017 3138 46c8 0017 3138 46c8
0x0040: 0017 3138 46c8 0017 3138 46c8 0017 3138
0x0050: 46c8 0017 3138 46c8 0017 3138 46c8 0017
0x0060: 3138 46c8 0017 3138 46c8 0017 3138 46c8
0x0070: 0017 3138 46c8 0017 3138 46c8 0017 3138
0x0080: 46c8

Server wakes-up

4) Sleep SC server

5) Squeezecenter classic, playing until buffer is empty, looses server and goes black screen, remote control a bit numb, then able to do right arrow to reconnect. Says "Waking-up SqueezeCenter":

Reads this:
IP (tos 0x0, ttl 64, id 17664, offset 0, flags [none], proto: UDP (17), length: 130) 192.168.1.252.3483 > 255.255.255.255.8900: [udp sum ok] UDP, length 102
0x0000: 4500 0082 4500 0000 4011 72c7 c0a8 01fc
0x0010: ffff ffff 0d9b 22c4 006e 8a97 ffff ffff
0x0020: ffff 0017 3138 46c8 0017 3138 46c8 0017
0x0030: 3138 46c8 0017 3138 46c8 0017 3138 46c8
0x0040: 0017 3138 46c8 0017 3138 46c8 0017 3138
0x0050: 46c8 0017 3138 46c8 0017 3138 46c8 0017
0x0060: 3138 46c8 0017 3138 46c8 0017 3138 46c8
0x0070: 0017 3138 46c8 0017 3138 46c8 0017 3138
0x0080: 46c8

Server wakes-up

6) Sleep SC server, power down squeezebox classic

7) Duet bridged mode, playing, immediate blue fan on the Controller, Controller keeps responding to inputs (not being able to pass them on to the server), then displays a "Wait" message.

Reads this:

IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 130) 192.168.1.251.32779 > 255.255.255.255.7: [udp sum ok] UDP, length 102
0x0000: 4500 0082 0000 4000 4011 77c8 c0a8 01fb
0x0010: ffff ffff 800b 0007 006e 6298 ffff ffff
0x0020: ffff 0004 2016 2582 0004 2016 2582 0004
0x0030: 2016 2582 0004 2016 2582 0004 2016 2582
0x0040: 0004 2016 2582 0004 2016 2582 0004 2016
0x0050: 2582 0004 2016 2582 0004 2016 2582 0004
0x0060: 2016 2582 0004 2016 2582 0004 2016 2582
0x0070: 0004 2016 2582 0004 2016 2582 0004 2016
0x0080: 2582

This is the Controller (.251) trying to wake the Receiver (.250)...

The Recever never sends a WOL packet to the server, hence the server does not wake-up. It sends frames however, but they don't exactly look like WOL packets and I can't see my servers MAC in it:

The most often seen are like this:
IP (tos 0x0, ttl 64, id 1267, offset 0, flags [none], proto: UDP (17), length: 46) 192.168.1.250.3483 > 255.255.255.255.3483: [udp sum ok] UDP, length 18
0x0000: 4500 002e 04f3 0000 4011 b32a c0a8 01fa
0x0010: ffff ffff 0d9b 0d9b 001a 7116 6400 072f
0x0020: 0000 0000 0000 0000 0004 2016 2582

And from time to time this longer one:
IP (tos 0x0, ttl 64, id 1238, offset 0, flags [none], proto: UDP (17), length: 107) 192.168.1.250.17784 > 255.255.255.255.32772: [udp sum ok] UDP, length 79
0x0000: 4500 006b 04d6 0000 4011 b30a c0a8 01fa
0x0010: ffff ffff 4578 8004 0057 c2b4 0002 0000
0x0020: 0000 0000 0001 0004 2016 2582 0001 c001
0x0030: 0000 0100 0100 090c 0f77 6169 745f 736c
0x0040: 696d 7365 7276 6572 0b02 3037 0a04 3030
0x0050: 3035 0902 3437 030a 7371 7565 657a 6562
0x0060: 6f78 0207 416e 7469 6265 73

Reconnect fails. Controller "forgets" the SC server, game over.
And then the Controller said "battery empty". Sure, I can fix that.

fcm4711
2008-10-02, 10:27
Hi there

SBC: Right now WOL from a SBC works only if it's connected directly to a wireless router which means that isn't an option for you.

SBR: If an SBR gets disconnected from SC and its LED is blue, pressing the button on SBR sends out a WOL packet. (This was added in fw >= 42 which is included in SC 7.2)

Cheers
Felix

epoch1970
2008-10-02, 11:46
Felix,
thanks for the info. I tried twice.

However, pressing the button on the Receiver didn't woke up the computer (I am using firmware 47, SC 7.3 right now). As I insisted on the button, the SBR turned to "red fan" mode... Had to restore and re-pair the Controller.
Well, at least I had a good laugh.

Let's say it works with SC stable. This solution remains quite unsatisfactory. An SB wakes the server from the remote control. I want exactly the same behavior for the Duet in bridged mode.

Now, shall I post a bug report, or would it merely be a duplicate ?

Mnyb
2008-10-02, 12:05
This is the rigth thing to do !
There is a bug for WOL that is closed, besides the obvius fact that WOL still does not work reliably.
I have a pretty simple and stright forward setup I can wol in most of the cases when it should work (but not all )
Wol in 7.2 beta was better than in the 7.3 beta.

WOL in adhoc conection mode should work to, thats very resonable thing to ask for.
So file bug for the reciever I think ? as there is some kind of wol working on controller ? it realy does not matter, as the person assigned to the bug can change this to something else if they want.

I think there is an bug for wol in adhoc mode ? but it's not easy to search bugzilla, so file a bug if it is a dupe somebody will fix that.

What realy amazes me is that this did not work from day one as the other SB products have WOL working quite good ?

epoch1970
2008-10-02, 15:58
Trouble ticket on its way.