testing Wifi host

[cblog16]

Sorry again for disturbing here in the community, just want to ask if someone can point me to a direction on how to test a WiFi host.

Basically I need to test multiple Wifi Host, the wifi host is a linux machine.

thank you very much for your time.

[Lars_L]

Hey cblog16,

Could you give us some more information as to what you are trying to test? What type of WIFI host are you referring to? What about the host are you interested in testing?

Lars

[cblog16]

hello Lars,

thank you for replying, what I need is to test a multiple wifi host based on linux, I have multiple arm based device under test that has a linux distro loaded, and also has a wifi that served as a host, 

1. Is it possible to just have a single wifi client to test this multiple AP device

2. The test basically can just be a simple ping and file transfer. A single device under test(AP) and a single client just works fine, but the the the problems lies when multiple DUT is up, so single client can only connect to one.

3. On #2, can you advise a way to overcome this scenario

The client is installed on windows and my DUT uses linux.

[markus kossmann]

Just to be sure : your DUT has multiple radio units which should work at the same time ? Then add enough WIFI adapters to your testclient and configure every adapter and the counterpart at your DUT to use its own network. I.e. connection 1 uses 192.168.1.x ( netmask 255.255.255.0) , connection 2 uses 192.168.2.x etc.

[cblog16]

Hello markus,

thank you for taking the time to respond, and you gave me an idea on different network configuration.

1. The DUT has only one Wifi and thus serve as a host. And is default to have an IP of 192.168.1.1 , the client has an IP of 192.168.1.3, netmask 255.255.255.0, 

so it does not have multiple radio but rather multiple DUT(with one wifi host each) that is up and running (basically same principle I believe as what you have mentioned).

Suppose I have 24 DUT up and running that means I have to secure 24 clients based on your suggestions. 

[cblog16]

it seems doesn't work if you change the network connection to other IP range.

here is what I have done,

2 Wi Fi clients and 2 wifi DUT (host) is up,

1 client1 is set to have static IP of 192.168.2.102 netmask 255.255.255.0

1 client2 is set to have static IP of 192.168.1.102 netmask 255.255.255.0

2 DUT is up now at root@ubuntu:

1 DUT1 was set at 192.168.2.1 

1 DUT2 was set at 192.168.1.1

have the Wifi (HOST) of DUT2  down,

after the Wifi of DUT was down,  client 1 is connected to DUT1 which is ok, but then client2 even if set to 192.168.1.102 is also associated to DUT1 though DUT1 cannot ping the client2 due to different IP.

Now, have the DUT2 set to up, this yields to not detecting client 2 because it is already associated to DUT1.

[markus kossmann]

Are you using the same channel for both DUTs ? I think, you have to use different fixed channels to avoid that the testclient associates with the the wrong  DUT. Mightbe enabling a MAC filter on the DUT ( if there exists one) will also help to avoid associations with the wrong testclient