Solved How to know ip address guest system?

Interesting question. I suppose you mean from FreeBSD host.
I searched once how to do that (the hypervisor was bhyve) and came to the conclusion it's not possible, but...
 
Does the guest do DHCP? Maybe check the leases on the DHCP server?

Or use the console (serial?) of the VM, login and use the ip a command as is common on Linux.
 
SirDice said:
Does the guest do DHCP? Maybe check the leases on the DHCP server?

Or use the console (serial?) of the VM, login and use the ip a command as is common on Linux.
Click to expand...
Yes, if I could in... But I don't know address and response time is big. But may be guest system is down - I don' know. Good idea dhcp time, thank you.
 
Did you use sysutils/vm-bhyve? You can get to the console of a VM using vm console <guestname>

Code: 
     console name [com1|com2]
             Connect to the console of the named virtual machine.  Without
             network access, this is the primary way of connecting to the
             guest once it is running.

             By default this will connect to the first com port specified in
             the client configuration, which is usually com1.  Alternatively
             you can specify the com port to connect to.

             This looks for the nmdm(4) device associated with the virtual
             machine, and connects to it with cu(1).  Use ~+Ctrl-D to exit the
             console and return to the host.
vm(8)
 
jeltoesolnce said:
Host - FreeBSD 14.1, Guest - CentOS 7, how to know ip-address guest from console?
Click to expand...
Have the guest ping the FreeBSD host. Look at the packet that you receive on the FreeBSD host.
(and any other similar network service that the FreeBSD host allows and is supported in the guest; e.g., talk(1))
 
It's fairly usual to side-step the issue, and set up the DHCP server to provide a specific IP address to your VM client on the basis of its MAC address.
 
Depending on the size of your LAN, you could always do something like nmap -sn 192.168.1.0/24 (if you are on a LAN of 192.168.1.0/24) It will give back the IPs of the hosts on the network, so if you already know that your server is 192.168.1.15 and there's only one or two VMS on the LAN you can see what isn't 192.168.1.15.
 
A thing I wanted to do for a while, but have not implemented yet, is putting all OS installations, physical or virtual, on the VPN. No exceptions. Then you don't have to worry about most of this.
 
My though too. Is that too simple? You need to know interface name for this one.

ifconfig em0 | grep 'inet' | awk -F ' ' '{ print $2 }'

Feels dirty.
ifconfig | grep 'inet' | awk -F ' ' '{ print $2 }'|head -n1

Maybe cleaner:
cat /var/log/messages | grep "New IP Address" |tail -n1
 
I am pretty sure vbox uses a consistent network interface name so it should be easy.

ifconfig vtb0 | grep 'inet' | awk -F ' ' '{ print $2 }'
I am not positive on that exact interface name.
 
All these are cool, but there is no solution to get the ip address of a guest (from the host) without installing something in it. You can't know the mac address of the inner side of the guest. So, even if it uses DHCP, you still have nothing. And if it is a fixed ip address, not less, but of course, not more.

Just to make things clear.
 
Emrion said:
All these are cool, but there is no solution to get the ip address of a guest (from the host) without installing something in it. You can't know the mac address of the inner side of the guest. So, even if it uses DHCP, you still have nothing. And if it is a fixed ip address, not less, but of course, not more.
Click to expand...
The MAC address of the guest virtual NIC is a static thing, allocated when the guest is created, and stored in a configuration file on the virtualisation server. Given that you (can) know the MAC address, and want to use DHCP to provide an IP address (along with default route, etc.), you can:
  1. either configure the DHCP server to provide the same static IP address (matched to the MAC address) every time the client boots; or
  2. allow the DHCP server to allocate the IP address dynamically.
Regardless, you can then use nmap(1) from any other host on the subnet to match the known MAC address to its current IP address.
 
gpw928 said:
The MAC address of the guest virtual NIC is a static thing, allocated when the guest is created. Given that you know the MAC address, and want to use DHCP to provide an IP address (along with default route, etc.), you can:
  1. either configure the DHCP server to provide the same static IP address (matched to the MAC address) every time the client boots; or
  2. allow the DHCP server to allocate the IP address dynamically.
Regardless, you can then use nmap(1) from any other host on the subnet to match the known MAC address to its current IP address.
Click to expand...
Well... An all working solution isn't there. You cannot suppose you know where is the DHCP server and even if it will be used. And even more, you still don't know the MAC address of the VM, furthermore it can be changed.
 
You must log in or register to reply here.
Back
Top