From william.law at tesserent.com Fri Oct 19 06:14:32 2018 From: william.law at tesserent.com (William Law) Date: Fri, 19 Oct 2018 17:14:32 +1100 Subject: Polymon packet format Message-ID: <9778b09ab7bc267850965fadf50d271f@mail.gmail.com> Hi All (mainly Alex) I couldn't see anywhere that described the polymon udp (or tcp via udp2tcpd) packet format, and can't seem to get my head around the code in Polymon for decoding it. Is there a table that describes the data format so that we can make use of it in a custom portal? Thanks :) Kind Regards, William Law -- Tesserent Level 5, 990 Whitehorse Road, Box Hill, VIC 3128 E: william.law at tesserent.com P: +61 3 9880 5555 F: +61 3 9880 5556 W: www.tesserent.com W: www.cyberbiz.com.au From rousskov at measurement-factory.com Wed Oct 24 20:45:12 2018 From: rousskov at measurement-factory.com (Alex Rousskov) Date: Wed, 24 Oct 2018 14:45:12 -0600 Subject: Polymon packet format In-Reply-To: <9778b09ab7bc267850965fadf50d271f@mail.gmail.com> References: <9778b09ab7bc267850965fadf50d271f@mail.gmail.com> Message-ID: On 10/19/18 12:14 AM, William Law wrote: > I couldn't see anywhere that described the polymon udp (or tcp via > udp2tcpd) packet format, and can't seem to get my head around the code in > Polymon for decoding it. IIRC, we used the BEEP protocol[1] for polymon messages, but the field details were never published, are not a part of Polygraph interface, and are likely to change if somebody sponsors a refreshment of that old and rarely used feature. The source code remains the primary source of information about polymon packets. Back in the day, we restricted ourselves to text consoles, and we were concerned about processing and bandwidth overheads. The modern way to implement the same monitoring functionality would be based on something like WebSocket connections feeding JSON objects to a client-side Javascript/HTML5 app. Please ping me if you want Factory to work on this. Thank you, Alex. [1] https://en.wikipedia.org/wiki/BEEP