![](https://seccdn.libravatar.org/avatar/150bb68600b6f4527c14c79e81e90f53.jpg?s=120&d=mm&r=g)
On Tue, 28 Sep 2021 18:19:10 +0200 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
On Tue, 28 Sep 2021 13:42:14 +0200 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
I suspect I have a more fundamental problem now. I don't see any traffic from the device I'm trying to inspect. I suspect that is because it is connected via a mesh repeater and there's nothing else on that repeater's wifi network. They're all on the main router's mesh master wifi. So whilst everything can talk to one another happily via the router, I suspect tcpdump can't see the packets?
You have two wifi access points, one has only your Raspi, the other has all the other wireless devices?
I have a Fritz!Box router that has all my wireless devices connected to it including the pi, but NOT the device I'm trying to monitor. That has connected itself via a Fritz!Repeater that's meshed to the router. But the device can talk to an app on a phone on the router's network. They all have addresses in 192.168.179.*
If you are connected to the Raspi via the wlan interface, a tcpdump on wlan0 will show the port 22 traffic at the very least.
I'm connected to the pi by its Ethernet connection (192.168.1.24) and its acting as a bridge to the wireless network (192.168.179.*). I can see lots of traffic on the wireless network, just not the device connected via the repeater.
You're running something like this: ?
tcpdump -s0 -w/tmp/something.pcap -i wlan0
Yes exactly that apart from the filename :)