ORBIT-USER: questions about atheros card

[Haris Kremo]

With regard to (1): this is working for a long time, perhaps you
should check the prototypes in your old scripts

  node.net.w0.mode = "managed"
  node.net.w0.type = 'b'
  node.net.w0.channel = 11

The patch for problem (2):

http://www.orbit-lab.org/wiki/HowTo/bssidFix

Hope it helps,

H.

On 5/12/07, Xiangpeng Jing <xjing at winlab.rutgers.edu> wrote:
> Hi all,
>
>   I started to run some of my old code using atheros cards but there
> are some problems. Could anyone give me an update? Sorry if I asked
> repeated questions. I am using image 1.0.9.
>
> (1) When I tried to set channel on atheros cards with master mode, it
> always give me error:
> Error for wireless request "Set Mode" (8B06) :
>     SET failed on device ath0 ; Invalid argument.
>
>   How to set a pair of master/managed nodes on a particular channel,
> as they have better association than ad-hoc mode?
>
> (2) How is the ad-hoc mode status for atheros card now? I managed to
> set up a couple of atheros nodes using ad-hoc mode, and finally their
> essid, channel, cell id are all same. But some nodes still can not
> communicate with others, e.g., node18-18 can not communicate with
> node10-11, but was able to communicate with other nodes.
>
> (3) Maybe Kishore can help me with this question: how long is the
> latency when I dynamically set up a channel for a pair of atheros
> nodes before they are able to communicate? I used system calls
> (iwconfig) in my program (I know it's a bad method) to change runtime
> channels but atheros nodes can not communicate in this way (before it
> worked great for intel cards). Is there a faster way to change atheros
> card channels runtime, e.g., some ioctls for the old aironet driver?
>
>
>   Thank you for any comments!
>
> Regards,
> Xiangpeng
>