To test wifi connections (or others too:) I like to send a lot
of pings. fping.exe is nice for this if you have windows.
fping 10.8.37.129 -s 1300 -t 0 -n 1000
add -i if you have any weird problems/error messages
You can use >1 instance if required.
If there is anything dodgy about the link you will see it
Be aware that this application can send a lot of traffic and
could affect network/system performance.
To use wireshark on wifi you need linux, or windows with
the wireless pcap shim. The latter is commercial software
and is not free (airpcap?). Alternatively you can use the free
Windows Network Monitor from Microsoft. You may be able
to save the files in wireshark format or wireshark may be
able to read it's files. I may be a bit out of date on this, it is
possible that someone has written a free shim now.
To capture traffic other than your own you will need a
wireless card *and* driver that can be put in monitor mode.
Unless there is a bug in the router I would have thought that
wifi<->wifi traffic should be no different to wifi<->lan. Of course
there are two wireless hops in the former case and BOTH
would need to be working correctly.
The later IOS software can I seem to recall do packet
capture to flash/network (12.4.twentysomething). On an
87x router however I would think that the performance
would soon become CPU limited. You would not I
would think see ethernet<->ethernet traffic either unless
routing between vlans or maybe bridging between vlans.
It would work on BVI10 I guess. Check memory requirements
before upgrading. Stated flash requirements now include the
Web GUI thingy which of course is not essential. If the image
fits the flash then you have enough flash:) For testing/
development purposes you could always boot over the
network if you did not have enough flash. Not so wise