From: Jing S. <gar...@gm...> - 2006-12-11 21:28:06
|
Hello Mirco, I'll try my best to answer your questions, embedded below: > Moreover, I often need to disable and enable the network connections > when I restart Haggle in order to obtain a normal behaviour. In fact, > sometimes, it happens that the "switching" between ad hoc and > infrastructure modes does not start at all. Restarting the connections > seems the only solution in these cases. This is necessary as a limitation in how we are operating the cards when in adhoc mode. When in adhoc, we assign a static IP to the interface as a calculated hash of the card's MAC address. Unfortunately, this staticIP must be released via a Handle that Windows returns to us. If Haggle is killed it is unable to release this Handle, and thus "repairing" the interface is the only way to get rid of the staticIP and thus regain normal behaviour of the card. We are looking into ways to fix this in a more robust way. > 2006-12-11_09:24:47 (7) WiFi changetoadhoc configurenetmode failed @ > haggle.connectivity.wifi.WiFiConnectivity.changeToAdhoc(WiFiConnectivity.java:441) This is the root of all your problems because if Haggle cannot reliably set the adhoc mode it cannot operate correctly to exchange information in p2p mode. This seems to be a recurring problem on many devices that we have not yet been able to figure out. Apparently this is an issue for some of the IPW2100 cards as well. I am sorry that I currently do not have a fix for this yet. On some cards, if you copy line 435 and paste it just before line 441, the setting of the mode AFTER setting the SSID might work. This seems to go against the official driver spec for what should happen, but it might work. I'll try to figure out what else I can do to remedy this. In the mean-time, please let me know what else you've tried that does or does not work. -Jing |