Frequently Asked Questions

1. Install the driver.
2. Select the adapter.
3. Create the Ad-Hoc network prefixed "Daihinia" in the SSID (examples: "Daihinia", "Daihinia:joe's-network"). We recommend you to create the default "Daihinia" SSID as an open network with no encryption and the private network with whatever security parameters you want ("Daihinia" SSID is reserved for public locations with open access to anyone).
4. Make sure the security parameters of the SSID are the same on all computers in the network.

Named after Daihinia brevipes -- a species of crickets, also known as camel cricket. The way this software propagates information is somehow similar to how crickets chirp. And camels carry user loads. :)

See also: image on insectimages.org

Download the newer package and install it over the old one.

Then proceed as usual - Install Driver (it will update the old driver) and Select Adapter to work with.

There is no need to create the Ad-Hoc network again.

You have to install and configure the Daihinia driver in order to access the traffic in that network.

However, it might turn out that your meshing neighborhood is a local-only network and does not have access to the Internet at all. Please ask your neighbors for details.

You must have an account on the site to log in using OpenID.

First log in with your username and password, then attach one or more OpenID identities to your account. Then you can log in using any of those OpenID identities instead of a usual user+password.

1. Install the driver.
2. Select the adapter.
3. Create the Ad-Hoc network prefixed "Daihinia" in the SSID (examples: "Daihinia", "Daihinia:joe's-network"). We recommend you to create the default "Daihinia" SSID as an open network with no encryption and the private network with whatever security parameters you want ("Daihinia" SSID is reserved for public locations with open access to anyone).
4. Make sure the security parameters of the SSID are the same on all computers in the network.

It is sufficient to start the Control Application and press the Select Adapter button, then deselect your wifi adapter in the list.

Beginning with v1.0.1132, the driver activates the mesh network functionality only when connected to SSIDs prefixed "Daihinia", thus you don't need any manual action when connecting to a regular wifi network.

Same as you would normally do -- via the Internet Connection Sharing (ICS) feature of Windows.

Open the properties of the adapter that is connected to Internet, select the Advanced tab, then select the Allow other network users to connect through this computer's Internet connection check box. If there's a drop-down list near the check box, select your wireless connection.

Daihinia is a network layer based on the Ad-Hoc mode of WiFi operation, while the connection to an AP is the infrastructure mode. These are two WiFi modes that work completely different and cannot be mixed with one another. One given WiFi adapter cannot be connected to an Ad-Hoc and an Infrastructure network at the same time.

However, if you have two WiFi adapters on the same computer, you can set up traffic routing between them at the IP level, in this case one adapter should be connected to the AP and another one operates on the Daihinia-based mesh network.

With two adapters set up as said above, you can share the Internet connection provided by the AP to your local Daihinia-based mesh network in the same manner as you would share an usual wired connection (see the related question).

You have to install Daihinia driver on all stations of your daihinia network; without the driver computers will not have access to the traffic in the daihinia network.

No, it does not deal with power/sensitiity. It just repeats the packets that were sent by nearby stations so other stations could receive them. Thus, we can say it increases the range of packet destination, not the range of any given radio.

It's a known issue. On a HP-Compaq Notebook PC with preinstalled Windows Vista and HP software, you might get SPAPI_E_NO_DRIVER_SELECTED when trying to install Daihinia Driver.

If you try a manual installation of the driver (via adapter's property window), it will show the driver installed, but it will not work. This is because said HP software hooks to the INetCfg interface and related classes, preventing the driver to install in an official way via INetCfg (as documented and recommended by Microsoft).

Please remove the misbehaving software supplied by HP, then retry the driver installation normally via Daihinia Control App.

Feel free to contact HP on this issue, because it causes problems with any NDIS IM, not only Daihinia. This also means your antivirus or firewall might have no effect at all even if it looks like it is installed correctly.

---

Similar case with a Dell laptop and failing to install vmware bridge.

Daihinia is a network driver and cannot be installed without administrative privileges. Do not give such privileges to regular users and they won't violate your company's Security Policy.

The User's Guide provided in the package contains the step-by-step instructions on the ad-hoc network setup. Daihinia's driver activates itself when the SSID is prefixed "Daihinia" (with capital D, and without quote marks, of course).

Actually, it GOES away, but pops up again for each possible Binding Path (read: each adapter, including the virtual and disabled ones) that you have. Just answer "yes" as many times it asks.

If you experiment a lot with Daihinia, consider disabling the Unsigned Driver warning message.