I was able to see that I'm getting responses back from my Linux development machine from Wireshark on my Windows Machine as shown below using the text format instead of hex. So it looks like I should be able to continue to the next steps to get the gui talking to Machinekit which will take some time. I will need to address the security problem with public network access sometime in the future but it is a big problem for myself since the running system is not connected to outside access right now, but certainly something to keep in mind. equipment at .
This is the text version of the response my Windows computer received from Machinekit using Wireshark on its 10.10.20.1 interface. 10.10.20.2 224.0.0.251 MDNS 829 Standard query response 0x0000 PTR HAL Group service on cnc1.local pid 2217._machinekit._tcp.local PTR HAL Rcommand service on cnc1.local pid 2217._machinekit._tcp.local SRV, cache flush 0 0 6202 cnc1.local A, cache flush 10.10.20.2 TXT, cache flush PTR HAL Rcommand service on cnc1.local pid 2217._machinekit._tcp.local PTR HAL Rcomp service on cnc1.local pid 2217._machinekit._tcp.local SRV, cache flush 0 0 6201 cnc1.local TXT, cache flush PTR HAL Rcomp service on cnc1.local pid 2217._machinekit._tcp.local PTR HAL Group service on cnc1.local pid 2217._machinekit._tcp.local SRV, cache flush 0 0 6200 cnc1.local TXT, cache flush -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/414b8df2-52f9-4b89-a547-d57bd02ccd78%40googlegroups.com.
