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
On 05/29/2017 02:22 PM, Brian Kantor wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Mon, May 29, 2017 at 02:13:50PM -0700, David Ranch wrote:
Is the goal here to identify and get these packets stopped or is the group softening their stance of accepting the receipt/response of MNDP (Miktotik), Avahi (Linux)/Bonjour(Apple), LLDP (standard routing link advertisements), CDP, etc? --David KI6ZHD
Well, my point of view up to now has been that broadcast packets of any kind don't belong being sent off the local network, particularly not to amprgw. Fact is, some people are doing so, in my opinion because their gateway is misconfigured. That's why I log them as errors.
Rob seems to think there's some value in tabulating the data contained in those packets at amprgw and presenting it in some form for troubleshooters and the curious. I'm not yet convinced.
- Brian
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net