NetworkManager ignores virtual tap0 device

[Yclept Nemo <orbisvicis gmail com>]

The tap0 device is created by openvpn but not pushed any network details - openvpn expects a dhcp client to lease an IP.

When NetworkManager sees the device:
Sep  9 11:41:09 cinnabar nm-system-settings: Added default wired connection 'Auto tap0' for /org/freedesktop/Hal/devices/net_de_c1_d5_98_e6_52

According to nm-connection-editor, aside from MAC addresses 'Auto tap0' is exactly like 'Auto eth0'

However when restarting NetworkManager, it attempts to start up the disconnected eth0 and then deactivates it, but doesn't touch tap0.
With one failed assertion?
Sep  9 12:08:13 cinnabar NetworkManager: <info>  Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan
Sep  9 12:08:13 cinnabar NetworkManager: nm_device_ethernet_new: assertion `driver != NULL' failed
Sep  9 12:08:13 cinnabar NetworkManager: <info>  (eth0): new Ethernet device (driver: 'b44')

And nm-tool lists only eth0 and wlan0. I also haven't found any HAL or PolicyKit policies that are preventing NetworkManager from managing the tap0 device.

Some details about the tap0 device:
net.originating_device = '/org/freedesktop/Hal/devices/computer'  (string)
net.interface = 'tap0'  (string)
linux.sysfs_path = '/sys/devices/virtual/net/tap0'  (string)
info.parent = '/org/freedesktop/Hal/devices/computer'  (string)


The convenience of NetworkManager managing the tap0 device is that it properly updates /etc/resolv.conf and doesn't mangle my routes (and also doesnt require sudo)

thanks