Skip to main content

troubleshooting FAQ

How to solve problems that may arise in some cases.

What could WiFi chip manufacturers do in order to improve performance with Daihinia mesh?

Given that chip manufacturers visit our site quite frequently, this is our advice.

First of all, it would be nice if WiFi chips would decrease the beaconing rate the more neighboring nodes they have associated with (in IBSS mode); many neighbors -> beacon rarely. They could consider the default beaconing rate for 1 neighbor, increase the interval to 2 times the default if there are 2 neighbors, to 3 times the default if there are 3 neighbors, and so on.

When the adapter is in Ad-Hoc mode, it already knows how many associated neighbors it has (either the adapter knows or its driver knows, depending on the architecture of the chip/adapter). Just adjust the beaconing rate at the points of association/disassociation procedures.

It seems that multihop does not work, what to do?

Mesh capabilities are turned on only when you are connected to a network prefixed Daihinia. Use the Control App to correctly create such networks, on the Ad-Hoc tab.

Also please make sure that the driver is installed and bound to the WiFi adapter. Use the Driver tab, press Select adapter button to check the bindings.

How to solve instability issues?

Generally, it's sufficient to update your adapter's driver. If your driver was released before 2008, chances are that it should be updated, although some old adapters perform very well even with old drivers.

Also please pay attention to the power load of the USB port (if your adapter is USB), especially if you notice instabilities only when your mesh is loaded heavier than usual. Try to re-plug the adapter into a port that supports heavier power loads, that port is usually marked physically with a different color than the others.

Clients are not getting IP parameters from a Windows 2008 Server DHCP, what to do?

This is because your wireless adapter driver reports the interface "up" state only when it's factually connected to a network, which usually happens later than the DHCP server is started.

To solve this issue, connect the network first, then do an explicit binding of DHCP to that interface:

How to get WiFi working on Windows Server 2008?

By default, Server 2008 installs itself without the WLAN Service. To add and enable it, please follow these steps:

  1. Go to Server Manager
  2. Add features
  3. Select to add the Wireless LAN Service
  4. Click Next and finish the installation.
  5. Install your WiFi drivers if not automatically detected.
  6. Install Daihinia and configure the mesh

The "Windows Logo" warning doesn't seem to go away after I answer. What can I do?

Actually, it goes away, but Windows XP pops up again for each adapter, including the virtual and disabled ones that your system has. Just answer Continue Anyway as many times it asks.

Syndicate content
Please Register