MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
I have tried to connect to Intel AMT via IPv6. When I add a computer in MeshCommander and type the IPv6 address into the Hostname field, then save the computer entry and attempt to connect, I only get a Connection timeout. I have tried the two following formats with the same result:
2001:db8:1:2:3:4:5:6
[2001:db8:1:2:3:4:5:6]
When I create a DNS hostname with only the AAAA resource record pointing to the same IPv6 address, MeshCommander can connect to the node with no issues. (IOW the connectivity works fine, the app works fine when using hostname.)
I'm happy to collect more data if needed, however I'm currently not sure what/where to check. I have only checked in Wireshark that the application does not attempt to send any packets to the destination, therefore my assumption is that the application does not correctly recognise the hostname as a pure IPv6 address.
Hello,
I have tried to connect to Intel AMT via IPv6. When I add a computer in MeshCommander and type the IPv6 address into the Hostname field, then save the computer entry and attempt to connect, I only get a Connection timeout. I have tried the two following formats with the same result:
2001:db8:1:2:3:4:5:6
[2001:db8:1:2:3:4:5:6]
When I create a DNS hostname with only the
AAAA
resource record pointing to the same IPv6 address, MeshCommander can connect to the node with no issues. (IOW the connectivity works fine, the app works fine when using hostname.)I'm happy to collect more data if needed, however I'm currently not sure what/where to check. I have only checked in Wireshark that the application does not attempt to send any packets to the destination, therefore my assumption is that the application does not correctly recognise the hostname as a pure IPv6 address.