My apologies all, I had the antenna plugged in to the first connector.
ath5k appears to only use the second. Plugging in to the second one
fixes most problems. I didn't get a chance to see if the ath5k way of
creating and joining an ibss works now, but we can now get full
throughput in adhoc mode.
On Tue, Jul 20, 2010 at 9:20 PM, Bob Copeland wrote:
>> Yes, I've checked the channel (36, 5180) allows beaconing. I've tried
>> the commands you mentioned, but no luck. If I monitor the interface
>> from another station, the ath5k drive never appears to beacon.
>
> What does "iw phy phy0 info" sh
Do you remember what version kernel this was fixed in? I can update
the nodes to at least this version and see if it helps...
On my setup, I am not seeing ANY probes from the ath5k nodes at all.
If I start a MadWifi node and the ath5k nodes join it, then bring down
the MadWifi node, the ath5k node
On Wed, Jul 21, 2010 at 10:11:14AM +1200, Derek Smithies wrote:
>> Then on the other machine (Vista) I just located 'myibss' (so beacons
>> are working) and selected it, then successfully pinged 192.168.10.1.
> Wrong.
> If the other machine located your node, then one of the four statements
> is
I am happy to provide such data. Tell me what config you want me to
put in place and I'll set up a capture.
Cheers,
--
Jonathan Guerin
On Wed, Jul 21, 2010 at 8:11 AM, Derek Smithies wrote:
> Hi,
> On Mon, 19 Jul 2010, Bob Copeland wrote:
>
>> On Mon, Jul 19, 2010 at 12:35 AM, Jonathan Guerin
Hi,
On Mon, 19 Jul 2010, Bob Copeland wrote:
> On Mon, Jul 19, 2010 at 12:35 AM, Jonathan Guerin
> wrote:
>> Hi,
>>
>> I'm trying to get my wireless nodes to associate in ad hoc mode.
[[[snipped]]]
> $ su
> # modprobe -r ath5k
> # modprobe ath5k
> # iw dev wlan0 set type ibss
> # ifconfig wlan0
> iw phy phy0 interface add wlan0 type adhoc
> iw wlan0 set channel 36
> iwconfig wlan0 channel 36
> iwconfig wlan0 essid txctest
I can't think of ANY reason why you do that. Use "iw", not "iwconfig".
All the last three commands should be replaced with one single "iw dev wlan0
ibss join myibss
I understand that it's not the way I'm supposed to do it. What I'm
saying is that it's not working, whereas the other way is! :(
I will play around some more with it tomorrow. It's still baffling as
to why the driver is not beaconing until there is another node tho...
--
Jonathan Guerin
On Tue
[please don't top post]
On Tue, Jul 20, 2010 at 04:39:29PM +1000, Jonathan Guerin wrote:
> Yes, I've checked the channel (36, 5180) allows beaconing. I've tried
> the commands you mentioned, but no luck. If I monitor the interface
> from another station, the ath5k drive never appears to beacon.
Wh
I've just tried associating with an existing MadWifi station, and the
'ibss join' command doesn't work - the ath5k station eventually gives
up and just creates it's own BSSID.
I used the above method:
# Create interfaces
iw phy phy0 interface add wlan0 type adhoc
iw wlan0 set channel 36
iwconfig w
Hi,
Thanks heaps for replying.
Yes, I've checked the channel (36, 5180) allows beaconing. I've tried
the commands you mentioned, but no luck. If I monitor the interface
from another station, the ath5k drive never appears to beacon.
What I've managed to get working, however, is to start one stati
On Mon, Jul 19, 2010 at 12:35 AM, Jonathan Guerin wrote:
> Hi,
>
> I'm trying to get my wireless nodes to associate in ad hoc mode.
[...]
> I've built and installed the compat package for this kernel version:
> compat-wireless-2.6.32.16
Ok, I'm not sure which mainline kernel this corresponds to,
Hi,
I'm trying to get my wireless nodes to associate in ad hoc mode. They
were able to work correctly with madwifi-ng, but with ath5k, they
simply will not associate. I've tried monitoring the interface for any
frames being sent out, but no beacons appear to be going out. I'm
currently running Ubu
13 matches
Mail list logo
