Have you used 192.168.60.200 (the subnet address) or 192.168.60.203 (the
broadcast address for the subnet) for a device? Those addresses are reserved in
your subnet and could cause errors in tcpdump engine. A /30 subnet only
supports 2 hosts.
Regards,
Ricardo
---- Robert Blair escribió ----
>I changed three IoT devices from DHCP to static addresses so I could trace all
>three of them.
>
>when I enter "net 192.168.60.201" in the capture filter I get all traffic to
>and from the ip.
>
>If I enter "net 192.168.60.200/30" I get all fraffic from the ip addresses but
>none going to the ip addresses. According to the documentation at
><https://wiki.wireshark.org/CaptureFilters> that syntax shoud capture all
>traffic going to and from the device.
>
>Any assistance on getting the trace to work will be appreciated.
>___________________________________________________________________________
>Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
>Archives: https://www.wireshark.org/lists/wireshark-users
>Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
