vboxnetX Acting Like Loopback Interface (Lion)

[Choom]

I've been running a setup using a NAT adapter and a Host-Only adapter on my VMs to prevent them from changing IP address all the time as I move from network to network. Everything was working fine until yesterday, when i decided to add a public IP alias to vboxnet0. Since then, and no matter how many times I remove and re-add vmnet0, restart VirtualBox, or restart the system, it's been acting like a loopback interface, forwarding my host connections to the host itself rather than the virtual machines.

The following was done without neither VirtualBox nor any of its VMs running:

Code: Select all

spark:~ jps$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
spark:~ jps$ VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet0' was successfully created
spark:~ jps$ VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.0.1
spark:~ jps$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.054 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.116 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.118 ms
^C
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.054/0.096/0.118/0.030 ms
spark:~ jps$ ifconfig vboxnet0
vboxnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 0a:00:27:00:00:00
        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
spark:~ jps$ VBoxManage hostonlyif remove vboxnet0
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
spark:~ jps$ ifconfig vboxnet0
ifconfig: interface vboxnet0 does not exist

Can anyone offer me some help restoring the original behavior?