Assuming that all of these advertisements present themselves as broadcast packets, it would be possible to simply analyze the existing pcap files, perhaps once a day at the end of the day, and prepare a report of what was found. All the necessary data is already contained in the pcap files.
That way I don't have to make any significant changes to the router nor write a new daemon. All I'd have to do to the router is stop reporting them as errors. It's an idea.
There's a few things we probably DON'T want to report; for example, one gateway is currently advertising that its SMB services are available. I regard that one as asking for trouble. - Brian
On Mon, May 29, 2017 at 02:56:27PM -0700, David Ranch wrote:
I've always viewed that these advertisement packets could help users fine services that are available on the AMPR system on a dynamic fashion vs. a static listing on the AMPR Wiki. The analogy here would be the static encaps.txt route file vs using RIP44. Having something ingest these packets on the UCSD system and update some login-required HTML or txt file could be pretty slick.
--David KI6ZHD