I cannot think of a case where we would *want* to run dhclient on a tap interface from the host. If nobody comments here this week, I'll approve it.

Aehm and why not? There are gazillions of other usages, e.g. with VPNs where you might exactly want this. It think it's a hard call on these virtual interfaces, where it's not black or white but gray.

This dhclient script invocation is no-op unless if ifconfig_tap0="DHCP" is defined. I agree that dhclient for tap(4) interface is useless in some cases, but is this script invocation harmful in practice?

While I'm not against the change, but well,
tap is general L2 tunneling mechanism, so it is widely used in various VPN configurations.
Openvpn can be good example: http://www.freebsdwiki.net/index.php/Openvpn_and_dhcp_client (this is server side, but still)

I second on bz, hrs, melifaro. The tap(4) isn't a hypervisor only interface.

Allan:

It appears that this is a non-starter. Want to close/abandon this?