bird wrote:@wbedard: I'm a bit confused as to the exact network/USB setup here. Would be helpful it you would attach the VBox.log file for a VM having trouble (the corresponding VBoxStartup.log would be nice too).
No problem! I realized that I was a bit thin on the details since I was mainly trying to find the most appropriate thread to start the discussion. As to your request, please see attached the VBoxStartup and VBox logs for the pfsense VM in question under the latest 4.3.17 test build.
To clarify things a bit more here in the post though, let me provide a bit more detail on what goes into my VM's network configuration. In VBox Manager -> pfSense VM -> Settings -> Network, Adapter 1 is a Bridged Adapter and Adapter 2 is a Host-Only Adapter. Under the USB Settings, I have a USB Device Filter configured to match my Alfa USB WiFi adapter. These are all the configured devices that will eventually become the actual network interfaces in pfSense once the VM boots. During the VM boot process, the pfSense kernel detects Network Adapter 1 as "/dev/em0", Network Adapter 2 as "/dev/em1" and the USB WiFi adapter as "/dev/run0". Later in the boot process, pfSense configures these network devices as network interfaces typical for a network router. In my case, the VM Bridged adapter (em0) becomes the WAN interface where all Internet-bound traffic is directed. Since pfSense provides a GUI for configuration, the VM Host-Only adapter (em1) becomes a LAN interface (192.168.56.2/24) which allows me to access this GUI from a web browser running on the VBox host. Since the primary purpose of this router is to test pfSense device support for my USB WiFi adapter, that device (run0) becomes a second LAN interface (10.0.1.1/24) for the actual wireless devices I have to connect to.
I hope this clarifies my setup a bit and that the attached files fill in further additional details. Again, if you determine that you need any add'l info, feel free to ask! Thanks again for all your time and effort to assist me in this.