I'm trying to test the WiFi Protected Setup (WPS) conformance of the DIR-655 with the latest firmware (1.20B07) and Windows Vista.
Well... actually, I'm kind of more interested in testing the behaviour between Windows Vista and several network devices in the Windows Connect Now (WCN) context. (WCN is no more than Microsoft's way of calling their WPS implementation).
I have setup two scenarios for my tests:
Here I have a Windows Vista computer directly connected to a DIR-655 ethernet port.
Everything seems to work ok here:
1. DIR-655 sends "UPnP:Discovery:Advertisement" messages as soon as it is switched on.
2. Vista queries the modem with standard "UPnP:Description:GetDeviceDescription" and
3. Vista subscribes to the Enrollee's UPnP events.
4. Finally, Vista sends a "UPnP:Control:Action:Invoke:GetDeviceInfo" to obtain WPS specific
information and draws a new icon (representing an unconfigured node) on the
At that point the user can double-click on the unconfigured node (on Windows Vista Network Explorer), select a network name and enter DIR-655 WPS PIN number. The process then continues like this:
5. Vista sends a new "UPnP:Control:Action:Invoke:GetDeviceInfo" message to DIR-655's IP
6. DIR-655 replies with an HTTP OK packet containing the first message of WPS's Registration Protocol (M1)
7. Vista now sends a "UPnP:Control:Action:Invoke:PutMessage" message containing M2
8. DIR-655 relpies with an HTTP OK packet containing M3
A more "graphical" representation of this can be found in the attached file "DIR655_as_Enrollee.txt"
This time I am interested in testing DIR-655 capabilities as a "Proxy" node. I.e. A new WiFi node will be added to the existing network (the one that has already been configured in scenario #1) and DIR-655 should then convert WiFi messages from the new node into UPnP event messages that get forwarded to the Windows Vista PC (where the external Registrar is located).
Once the new node is added to the network, it should start sending "Probe Request" messages to DIR-655 (acting as an AccesPoint/Proxy). Dir-655 should, for every of these messages received, generate a "UPnP:Event:Notify" message containing the TLV (Type-Length-Value) sets originally transmitted in the "Probe Request" packet, and forward this UPnP message to Vista, where a new icon (showing a new unconfigured node) should appear in the Network Explorer.
The "expected" behaviour can be better observed in the attached file "DIR655_as_Proxy.txt"
However this is NOT happening: I can't see any UPnP "event" message comming out from the DIR-655 proxy.
The "new WiFi node" I'm trying this with is *another* DIR-655 reset to factory defaults. Maybe DIR-655 is not prepared to act as an Enrollee in a "proxy'ed" set up? (It could be so... because even trying to use the *internal* registrar that seems to be implemented in the DIR-655 -from the "add a new WPS device" wizard in the embedded webserver- fails, no matter what option I choose: PIN or "push button").
Anyway... could you help me understand how does Vista find new devices on the network where a DIR-655 is acting as a WPS Proxy?
Even if the new device showed up in the Network Explorer, what should happen once I double-click on it an enter the new device's PIN? I guess Vista would then send a "UPnP:Control:Action:Invoke:SetSelectedRegistrar" message to the DIR-655 Proxy, who would then start including the SetSelectedRegistrar flag on its "beacon" frames (so that the new wifi device knows when it can send the EAPOL-Start message). Am I right? Is this functionality implemented?
I know this is a long (and boring) post, but any help would be greatly appreciated.
NOTE: It looks like I cannot attach any file, so I put them on rapidshare: