DragonFly’s tap(4)/tun(4) devices have been historically precreated – tap0, tap1, tap2, tap3.  They are now auto-cloned, which might surprise any software counting on the prior behavior.  I don’t know of any specific packages that are affected by this, though.  DragonFly version 5.6 is unaffected by this; it’s in -current only.