You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
libpcap is supposed to have a filtering feature that only requests for specific mac address ranges are returned. Since this is performed on a low kernel level, the filtering should be more efficient than filtering in pimatic-dash-button.
The text was updated successfully, but these errors were encountered:
Here is an example of such a filter "arp && (eth.src[0:3] == 1C:5A:3E || eth.src[0:3] == BC:05:43)". The vendor ids used in this example are for Samsung and Avm. Just replace them with Amazon vendor ids and extend the expression as needed. You can easily test the expression with a libpcap based sniffer like Wireshark (or tcpdump if you prefer a command line tool). See also https://www.wireshark.org
Sorry, I completely forgot abot the fact that wireshark uses its own filter syntax for display filters which is not compatible with libpcap filters. So, the filter syntax needs to be along the lines of the stackoverflow article you mentioned in the forum post: http://stackoverflow.com/questions/13086766/how-to-filter-mac-addresses-using-tcpdump. The filter would be something like "arp and ((ether[6:2] == 0x7475 and ether[8:1] == 0x48) or (ether[6:2] == 0xF0D2 and ether[8:1] == 0xF1))". You can trial it with tcpdump, like sudo tcpdump "arp and (( ..." or with Wireshark by setting a capture filter.
libpcap is supposed to have a filtering feature that only requests for specific mac address ranges are returned. Since this is performed on a low kernel level, the filtering should be more efficient than filtering in pimatic-dash-button.
The text was updated successfully, but these errors were encountered: