[PATCH] tests: add a test for mesh gate forwarding
j at w1.fi
Sat Mar 5 11:38:25 PST 2016
On Sat, Mar 05, 2016 at 01:48:46PM -0500, Bob Copeland wrote:
> The non-crashing case sounds like a case of root announcement not being
> received by addr2 by the time it tries to send frames; IOW changing the
> original time.sleep(1) to something bigger may work.
I think I tried that without much success..
> Sure, find the whole dump here:
How does that work? Have you some other changes in timing here? The log
2016-03-05 18:18:25,744 DEBUG wlan2: CTRL: DATA_TEST_CONFIG 1
2016-03-05 18:18:25,776 DEBUG wlan2: CTRL: DATA_TEST_TX 02:11:22:33:44:55 02:00:00:00:02:00 0
2016-03-05 18:18:25,785 DEBUG wlan2: CTRL: DATA_TEST_CONFIG 0
2016-03-05 18:18:36,682 DEBUG wlan0(global): IFNAME=wlan0 <3>DATA-TEST-RX 02:00:00:00:00:00 02:00:00:00:02:00
2016-03-05 18:18:36,688 DEBUG wlan0(global): IFNAME=wlan0 <3>DATA-TEST-RX ff:ff:ff:ff:ff:ff 02:00:00:00:02:00
2016-03-05 18:18:36,692 DEBUG wlan0: CTRL: NOTE TEST-STOP wpas_mesh_gate_forwarding
How did it wait almost 11 seconds there between transmitting that test
frame and stopping the test case? Does it really take so long in your
setup to start tshark?
I was able to reproduce this type of pass by adding time.sleep(10)
between that test frame TX and the check_frame_at_gate() calls.. Without
that, the test script is supposed to check the hwsim0.pcapng file
immediately after the test frame has been sent to the wlan2 netdev..
> Root announcements are at #156 and 173, the proxied frames are 230 and 232.
> If it makes a difference, I was testing this one case by itself. I'll
> try a full run shortly.
I'm running this with just the single test case. The output looks very
similar to yours if I add that extra 10 second sleep.
Jouni Malinen PGP id EFC895FA
More information about the Hostap