[PATCH] tests: add a test for mesh gate forwarding

Jouni Malinen j at w1.fi
Sat Mar 5 13:05:54 PST 2016

On Sat, Mar 05, 2016 at 03:38:33PM -0500, Bob Copeland wrote:
> It would seem my tshark will actually tail the file:
> 2016-03-05 20:26:49.967094 making gates
> 2016-03-05 20:26:50.051072 sleeping
> 2016-03-05 20:26:51.053181 sending frame
> 2016-03-05 20:26:51.137571 check frame starting tshark
> 2016-03-05 20:26:57.349248 check frame got response [Frame 228: 1566
> byte...]

Probably it is just painfully slow.. I've seen that couple of times, but
never really figured out why that happens. It has disappeared from my
current setup, though.

> ... TShark 1.12.7 (Git Rev Unknown from unknown)

TShark 1.10.6 (v1.10.6 from master-1.10)

> Anyway, I take it this would probably not be desirable to rely upon.
> Should I just wait for the RX event first?

I was thinking of running a loop doing the check_frame_at_gate() calls
for the first address pair until the frame is seen or some maximum time
(10 seconds?) each reached (and a small sleep between calls). Obviously
that is not going to do much if running tshark is as slow as it is in
your case, but it should allow this to exit pretty quickly in case the
tshark step works properly.
Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list