docs(FAQ): document unsupported DHCP client identifiers #1009
Conversation
docs/faq.md
Outdated
| } | ||
| ``` | ||
|
|
||
| Because the macOS built-in DHCP server overwrites the `hw_address` with the `identifier`, it leaves no information about the VM's MAC address to the `tart ip`, which relies on this file to determine the IP address associated with the VM's MAC address. |
There was a problem hiding this comment.
It seems like tart ip depends on /var/db/dhcpd_leases, which cannot work for bridged network, since the builtin macOS dhcps server is not the the loop.
It would be nice to add a sentence making this more clear (tart looks up the vm ip address in /var/db/dhcpd_leases...), and add a section about bridged network.
And a more clearer explanation of what "tart ip" does.
nirs
left a comment
There was a problem hiding this comment.
Looks good, but it sounds like we have 2 solutions and users have to choose the right one for the vm. The system can be smarter and pick the right solution (or both) transparently.
| tart ip --resolver=arp <VM> | ||
| ``` | ||
|
|
||
| This causes the `tart ip` to consult the host's ARP table instead of the `/var/db/dhcpd_leases` file. |
There was a problem hiding this comment.
I have very little experience with querying arp, but in the last time I tried to use it the vm (not a tart vm) got an ip and was accessible, but arp did not report the vm ip.
There was a problem hiding this comment.
Probably related to #873 (comment).
I'll try to document this in this section too.
There was a problem hiding this comment.
This seems to the common case, see
#873 (comment)
docs/faq.md
Outdated
|
|
||
| This causes the `tart ip` to consult the host's ARP table instead of the `/var/db/dhcpd_leases` file. | ||
|
|
||
| Note that this method of resolving the IP heavily relies on the level of VM's talkativeness on the network. This is normally not an issue for macOS VMs, but on Linux VMs you might need to install Samba, which includes a [NetBIOS name server](https://www.samba.org/samba/docs/current/man-html/nmbd.8.html) that exhibits the same behavior as macOS and populates the ARP table of the host OS: |
There was a problem hiding this comment.
talkativeness sounds wrong to me, maybe it is better to describe the actual behavior (sending the special arp request that makes the host added to arp cache).
Resolves cirruslabs/softnet#75.