Finding Server IMM IP by IPv6 Multicast Address

2020-07-16 315 words 2 minutes

Contents

Sometimes you may have a situation that IMM does not have a L3 connection that you need to go to Data-center and connect from your laptop to server IMM interface via Ethernet cable. Imagine a situation that your organization infrastructure was not documented very well that you do not know the IPv4 address of IMM interface to login.

If server IMM interface enabled with IPv6, then you are lucky – By using below methods you can easily figure out the IPv6 address of IMM interface and use it to connect to login IMM.

In this method by pinging IPv6 Link Local Scope multicast address(ff02::1), we are listing all the clients that joined to multicast group. According to Figure above ping will list only two multicast addresses that are your laptop and Server. Once we find server IPv6 Link local address on IMM interface, you can try to use login web browser by typing IPv6 Link local address which is fe80::5667:51ff:feb9:4ade%eth0 in that case. If it does not work, you can then use SSH Local Port Forwarding like below.

# ssh  -L 9090:[fe80::5667:51ff:feb9:4ade%eth0]:443 127.0.0.1

Open up the web browser and type https://127.0.0.1:9090

On windows; first find the interface ID with the below command. For this lab it is going to be used Wi-Fi (13)

netsh int ipv4 show interfaces

Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          75  4294967295  connected     Loopback Pseudo-Interface 1
 13          55        1500  connected     Wi-Fi
 11          25        1500  connected     Ethernet
 12           5        1500  disconnected  Ethernet 2
 10          35        1500  connected     VMware Network Adapter VMnet1
  4          25        1500  disconnected  Local Area Connection* 4
 17          35        1500  connected     VMware Network Adapter VMnet8

ping -6 ff02::1%13

Note: You may get “Request time out.” when you try to ping multicast address on specified interface on Windows. But when you capture package via Wireshark, it still shows all the neighbor devices that joined multicast group.