Why did my ad hoc network get a DHCP address, and not an autoconfig address?
In our current implementation of VirtualWiFi, all packets arriving at a wireless card are forwarded to the currently active virtual adapter. As soon as you start VirtualWiFi over an ad hoc network, the virtual adapter starts a DHCP request. In the non-VirtualWiFi scenario the card will get an autoconfig address after the DHCP request fails. If you started another network before the DHCP request timed out, it is possible for the card to receive a DHCP reply from another network and forward it to the incorrect virtual adapter. We suggest that the user wait for an ad hoc network to get a valid autoconfig address before it adds another network.
Related Questions
- You describe Wave Relay™ as being a Mobile Ad hoc Network; can it provide the same capabilities as the Mesh Networks that municipalities are currently deploying?
- How do I register my Ethernet card or wireless adapter address for access to the UNC Network (DHCP)?
- Why did my ad hoc network get a DHCP address, and not an autoconfig address?
