Write the code, we'll be happy to include it. The code handling ICMP is a model - it too is an Ethernet but not TCP/IP protocol.
Remember that the mission of ntop is to pull information of interest to network admins out of the data streams. Let that drive what you I would suggest creating a header tab like "IP Traffic" for "Other Protocols". Then have left menu pages for specific protocols. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pierotti, Phil Sent: Tuesday, July 30, 2002 5:21 PM To: [EMAIL PROTECTED] Subject: [Ntop] New "feature" for NTOP I was wondering if anyone has looked into providing more complete support for IPSEC VPN traffic in NTOP? ISAKMP is standard TCP/UDP port, but the rest of IPSEC is different IP protocol numbers (ie functionally at the same level as UDP and TCP) [esp = protocol 50, ah = protocol 51] It would be nice if NTOP could also track and display counters for this on the "all protocols" page. Others that come to mind at this level include GRE (protocol 47) , TLSP (56), IPIP (94) , L2TP (115). http://www.iana.org/assignments/protocol-numbers Just a thought. Thanks, Phil P ---------------------------------------------------------------------------- -- [EMAIL PROTECTED] ---------------------------------------------------------------------------- -- Phil Pierotti Ph: 408 376 5820 Senior Network Engineer Cell: 408 410 1818 eBay, Inc. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
