Thanks for the tip (and the help).
> On 19 Aug 2019, at 17:47, Giles Coochey wrote:
>
> Forgot to mention, outside Cisco the feature is called "port mirroring", and
> even some low-end TP-Link devices support this:
___
Sen
On 19/08/2019 16:34, Giles Coochey wrote:
On 19/08/2019 15:57, Richard Perlman wrote:
Got it. Makes sense. While my APs are in “bridge” mode, I do have
switches deployed in several locations, notably between the Mac I am
running Wireshark on and the rest of the network. I am not exactly
On 19/08/2019 15:57, Richard Perlman wrote:
Got it. Makes sense. While my APs are in “bridge” mode, I do have
switches deployed in several locations, notably between the Mac I am
running Wireshark on and the rest of the network. I am not exactly
sure how, or with the equipment I have - if,
Got it. Makes sense. While my APs are in “bridge” mode, I do have switches
deployed in several locations, notably between the Mac I am running Wireshark
on and the rest of the network. I am not exactly sure how, or with the
equipment I have - if, I can set up a span session. All the informati
On 19/08/2019 13:25, Richard Perlman wrote:
Note: on the local lan, 192.168.5.0/24, all segments, Wi-Fi and wired) are
bridged. So, I would expect to see all traffic to/from the plug on en0.
A bridge is a switch, i.e. it does MAC address learning and doesn't
flood all packets to all interfaces
Wireshark 3.0.3 on MacOS 10.14.6
I am trying to capture traffic to and from a local device (a Wi-Fi power plug).
If I connect the plug (via Wi-Fi) to a shared Internet connection on my Mac, I
see local lan exchanges as well as packets sent from the plug to a remote
server. The packets to the re
