[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Oh, all the original experiment was done using ad-hoc mode. The use of master mode was a last ditch attempt to get any kind of communication at all. This laptop has a Broadcom card which uses the bcm43xx driver - so not everything works. Others have reported success with it though. Google time again I suppose. BTW I have built version 29 of wireless-tools from source so now it is using the same version of wireless extensions as the driver. So the reporting tools seem to give a little bit more info now anyway. On Thu, 2008-01-03 at 22:16 +0000, Simon Waters wrote: > Alexis wrote: > > Humm, I've tried various permutations on the theme now, including > > setting up ip addresses on the two computers, re-creating the connection > > on the XP end, made sure both have the same essid, changed channel on > > this end (don't see how to do this in windows though) - still nothing. > > >> ESSID:"false-hackerz" <----------the XP laptop > >> Protocol:IEEE 802.11b > >> Mode:Ad-Hoc > >> should you box be also "false-hackers" ? > > You didn't mention placing the Linux box into ad-hoc mode. > > All machines on an ad-hoc network need to be in ad-hoc mode. > > Putting the Linux box in "master mode" probably needs additional > software or configuration to make it do something sensible. I have done > this before, and it isn't that hard to make a Linux box an access point, > but that would be a change of plan. > > iwconfig <interface> mode ad-hoc > -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html