Replies: 1 comment 1 reply
-
Ok, first of all, wsmantrace flag applies to node webkit version. If you want to trace Meshcentral WSMAN, look at webserver.js function handleRelayWebsocket. Have a look at the websocket data sent back and forth on that function. Alternatively, you can use browser debugging utility, look at websocket traffic at webrelay.ashx. You should see all WSMAN traffic there. You may not find the right HTTP authentication header in that traffic because it is being taken care of by interceptor.js at the server side. The same tracing method for Meshcentral also applies meshcommander webserver edition. If you want more detail, feel free to email me at joko dot sastriawan at intel.com. Additionally Open AMT Cloud Toolkit project team (sister project to this) may also able to help you. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to see all WSMan requests and responses to an AMT, either in MeshCentral or MeshCommander. I've looked at the debugging information on the website for MeshCentral, and turned on all the logging channels as listed there (are there others not mentioned? notable there's not a
wsman
channel). Messages are logged to the log file, but no wsman traffic.I've also running the webserver version of MeshCommander with the arguments
-wsmantrace -debug -logfile:/tmp/log.txt
. I see nolog.txt
being created, nor are there any messages in the developer console (using firefox). Do these options currently work?How can I see the WSMan traffic without resorting to packet sniffing?
Beta Was this translation helpful? Give feedback.
All reactions