29 May
2017
29 May
'17
9:49 p.m.
Understood but if we started advising users to enable Avahi, MNDP, etc.
to UCSD's IP, you would start to see richer data. The question is.. can
these different protocols be configured to only send these
advertisements (broadcasts) to the UCSD IP vs. everyone.
--David
KI6ZHD
On 05/29/2017 06:25 PM, Brian Kantor wrote:
(Please trim inclusions from previous messages)
_______________________________________________
David,
Surveying the existing pcap files, the only UDP ports that are being
broadcast currently are 138, 5678, and 10001. These don't seem very
useful.
- 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
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net