Hi Lin and all, May I bother you once again with this?
Well, after I found out how to do it right, I was amazed that snv_103 features a version of ath (1.4/0.10.5.6) that supports my hardware out of the box for infrastructure and wpa networks. It works great. However, I found out that this driver is again not working with the adhoc wep network. I tried the nwam way and it simply freezes the gnome panel for around a minute. I also tried the dladm way (dladm connect-wifi -e hspa-ah-d3atiq -b ibss -s wep -k nwam-hspa-ah-d3atiq), but it times out without further information. One interesting thing I saw is the output of dladm scan-wifi: LINK ESSID BSSID/IBSSID SEC STRENGTH MODE SPEED ath0 hspa-ah-d3atiq 42:95:f:20:ca:b8 wep excellent b 54Mb Notice that even though it recognizes the correct speed and signal strength (the phone is side by side with the computer), it still thinks this is a 802.11b network. Could the net80211 module need an update to work with this ath version? BTW, this behaviour persists with snv_104. Cheers, Douglas > Mea culpa :-) > > I'm now writing this from my SXCE laptop connected to > the Internet through my Nokia phone. > > Indeed the problem was that I was using the wrong > net80211 module(s). So now I have learned that ath > 0.7.3 and the stock ath shipped with SXCE are > different in that the former supports adhoc and the > latter doesn't and they depend on functionality from > net80211 that is implemented only within the one > installed with ath 0.7.3. > > Sorry for bothering you with this and thanks for your > help. > > -- Douglas > > > You should install the net80211 in this package > > because different with > > the module shipped with SXCE, it's specially > modified > > for adhoc mode > > support. -- This message posted from opensolaris.org
