Frequently Asked Questions

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 do carry user loads. :)

See also: image on insectimages.org

Download the newer package and install it over the old one. Then start the Control Application, choose Uninstall Driver (it will uninstall the old one), then choose Install Driver (it will install the new one). Then, press Select Adapter and choose the adapter to work with.

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.

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

Since v1.0.1132, the driver activates the mesh network functionality only when connected to "Daihinia" SSID, meaning 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.

Instead of being self-healing, Daihinia does not have any parts that can get sick. :)

However, the underlying layer (WiFi in Ad-Hoc mode) may experience getting out of sync. More about this problem can be found in these documents. As soon as the network adapter resynchronises with its neighbors, Daihinia is immediately ready to work.

Considering the above said, it's probably a good question to ask your WiFi hardware vendor concerning the scalability of the clock synchronisation algorithm that their products use in Ad-Hoc mode.

In other words put, the delays due to resynchronization are not on behalf of Daihinia. They're from the layer below (the WiFi adapter in Ad-Hoc mode).

It depends on the WiFi adapter and its driver. Windows 2000 does not have Wireless Zero Configurator, the WiFi network parameters are set via adapter driver properties (or a special setup program supplied with the adapter). If these means allow to set up an open unencrypted network in Ad-Hoc mode, then the answer is yes. Daihinia also requires NDIS 5.x to run. At the moment of testing, the Online Windows Update for Windows 2000 did successfully update for NDIS 5.x support.

You need one more adapter to connect to the AP. One given WiFi adapter cannot be connected to an Ad-Hoc and an Infrastructure network at the same time. You need a second WiFi adapter to make the bridging between the networks of two different types, and make sure Daihinia driver is NOT bound to the adapter that connects to the AP.

You have to install Daihinia driver on ALL stations of your Daihinia network.

It uses a tagging mechanism to ensure that:

• duplicates are discarded (in the event that two or more stations repeated the same initial packet within some station's range);
• no looping of a packet over the mesh network occurs.

Tags are added upon initial send, removed at the final destination, and used by intermediary nodes to ensure the above said.

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 HP software preinstalled, 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.

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 all the step-by-step instructions on the setup process.

Actually, it GOES away, but pops up again for each possible Binding Path you have. Just answer "yes" as many times it asks. If you experiment a lot with Daihinia, consider disabling the Unsigned Driver warning message.

Background:
Contrarily to how it is documented, Windows tries to bind the driver to ALL possible Binding Paths ("adapters") right away upon installing an Intermediate Driver. And there can be MORE Binding Paths than Adapters as seen in the Network Connections folder. Just from curiosity, open up the Network Adapters section in the Device Manager when booted in Safe Mode. Those are the Binding Paths. Even on a vanilla installation of Windows there's quite a number of them. And Windows tries to bind the poor driver to almost each one.

The Control Application takes care of this situation and unbinds the driver from all adapters after installing. Then binds again to the particular adapter when you select the one you want Daihinia to work with.