- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi!
I have just received the new NUC7i5DNHE, enabled AMT and started playing with MeshCommander. What I have quickly found is that on this platform it is not possible to add wireless profiles using MeshCommander (it fails silently), but it is possible to do so using default AMT web interface.
Since I have not found any other way of reporting the issue i am reporting it here.
Kind regards,
Chris
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Chris,
Thank you for the report of your issue and it has been forwarded to the Mesh Team for analysis. We will update you as soon as we can.
Joe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Have rechecked this with new edition of MeshCommander (0.5.8) and the problem still remains.
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Further re-checked with MeshCommander 0.5.9. The problem is still there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi. Interesting. I will take a look at it. If I can't find the same problem, I will update MeshCommander to display more feedback so to help debug this.
Ylian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ylian,
I know what is the problem!!
1. SSID - by standard the max length is 32 chars. MeshCommander allows only 31. Plain AMT web allows full 32
2. Password - max length allowed is 63 characters. MeshCommander allows only 62. Plain AMT web allows full 63.
My guess is that the problem is ASCIIZ termination. It should be easy to fix.
Kind regards,
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That is interesting! I just took a look and MeshCommander did not do any length validation on any of the WIFI profile fields. It just passed the strings as-is to Intel AMT. I just uploaded a new version of MeshCommander v0.5.9 that improves length validation. I did not bump up the version number, so you need to uninstall/download/install if you want to try it.
As for the 31/63 char issues. I don't see it on my computers. Try running MeshCommander like this:
nw.exe -debug -wsmantrace
You will see all of the Intel AMT traffic. Try adding WIFI profile with a dummy user/ssid/pass and cut & paste the WSMAN call that fails over. I will take a look. It's possible this is a AMT issue, but I can to confirm. If you can also provide the exact Intel AMT version you are using, that would be great.
Thanks,
Ylian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ylian,
This is what I have found. With the updated MeshCommander the problem is with SSID when it reaches 32 characters. Like below:
commander.htm:24 WSMAN-SEND(1960): POST /wsman HTTP/1.1
Authorization: Digest username="admin",realm="Digest:70300000000000000000000000000000",nonce="0U1XBs0BAAAAAAAAub/u2kHlkbYopM4K",uri="/wsman",qop="auth",response="057d1096009e9abb0b485967c9af4dde",nc="138",cnonce="l7j2vg0t3xr"
Host: 192.168.12.134:16992
Content-Length: 1659
<?xml version="1.0" encoding="utf-8"?><Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns="http://www.w3.org/2003/05/soap-envelope" ><Header><a:Action>http://intel.com/wbem/wscim/1/amt-schema/1/AMT_WiFiPortConfigurationService/AddWiFiSettings</a:Action><a:To>/wsman</a:To><w:ResourceURI>http://intel.com/wbem/wscim/1/amt-schema/1/AMT_WiFiPortConfigurationService</w:ResourceURI><a:MessageID>136</a:MessageID><a:ReplyTo><a:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address></a:ReplyTo><w:OperationTimeout>PT60S</w:OperationTimeout></Header><Body><r:AddWiFiSettings_INPUT xmlns:r="http://intel.com/wbem/wscim/1/amt-schema/1/AMT_WiFiPortConfigurationService"><r:WiFiEndpoint><a:Address>/wsman</a:Address><a:ReferenceParameters><w:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_WiFiEndpoint</w:ResourceURI><w:SelectorSet><w:Selector Name="Name">WiFi Endpoint 0</w:Selector></w:SelectorSet></a:ReferenceParameters></r:WiFiEndpoint><r:WiFiEndpointSettingsInput xmlns:q="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_WiFiEndpointSettings"><q:ElementName>P5</q:ElementName><q:InstanceID>Intel(r) AMT:WiFi Endpoint Settings P5</q:InstanceID><q:AuthenticationMethod>6</q:AuthenticationMethod><q:EncryptionMethod>4</q:EncryptionMethod><q:SSID>01234567890123456789012345678901</q:SSID><q:Priority>5</q:Priority><q:PSKPassPhrase>012345678901</q:PSKPassPhrase></r:WiFiEndpointSettingsInput></r:AddWiFiSettings_INPUT></Body></Envelope>
commander.htm:19 WSMAN-RECV(1463): HTTP/1.1 400 Bad Request
Date: Thu, 1 Feb 2018 14:44:17 GMT
Server: Intel(R) Active Management Technology 11.8.50.3425
X-Frame-Options: DENY
Content-Type: application/soap+xml; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wow, yes, looks like a firmware does not like 32 char long SSID's. Can you let me know the exact version of your Intel AMT? Also, if you have not done so already, try to update your BIOS/AMT to the latest version and try again.
Thanks,
Ylian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ylian,
My AMT greets me with following version: v11.80.50. Bit more was actually visible from the log sent previously where I could read: "Server: Intel(R) Active Management Technology 11.8.50.3425".
BIOS is DNKBLi5v.86A.0035.2018.0111.1737 from 1/11/2018. (this BIOS version was actually withdrawn from the Intel website due to microcode patch instability). But, this is the latest BIOS which was available for NUC7i5DNHE.
Ylian, what is interesting in addition is that when AMT is accessed via original web pages (http://A.B.C.D:16992/wlan.htm) then it is possible to add 32 character SSID.
Data as copied from MeshCommander:
|
Computer model |
NUC7i5DNHE |
|
Manufacturer |
Intel Corporation |
|
Version |
J71740-502 |
|
Serial number |
XXXXXXXXXXXXXX |
|
System ID |
XXXXXXXXXXXXXXXXXXXXXXXXXXXX |
|
|
|
Baseboard
|
|
|
|
Manufacturer |
Intel Corporation |
|
Product name |
NUC7i5DNB |
|
Version |
J57626-502 |
|
Serial number |
XXXXXXXXXXXXXXX |
|
Asset tag |
CIM_Card |
|
Replaceable? |
Yes |
|
|
|
BIOS
|
|
|
|
Vendor |
Intel Corp. |
|
Version |
DNKBLi5v.86A.0035.2018.0111.1737 |
|
Release date |
1/11/2018 |
|
|
|
Processor 1
|
|
|
|
Manufacturer |
Intel® Corporation |
|
Version |
Intel® Core™ i5-7300U CPU @ 2.60GHz |
|
Maximum socket speed |
8300 MHz |
|
Status |
Enabled |
|
|
|
Chris.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In addition I have re-checked with MeshCommander 0.6.0 - same issue with 32 character SSID.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page