Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

networkml uses TCP/IP or UDP/IP only #479

Closed
anarkiwi opened this issue Dec 8, 2019 · 1 comment
Closed

networkml uses TCP/IP or UDP/IP only #479

anarkiwi opened this issue Dec 8, 2019 · 1 comment

Comments

@anarkiwi
Copy link
Member

anarkiwi commented Dec 8, 2019

networkml knows how to deal with only TCP or UDP.

It doesn't know about non-IP traffic - for example, it doesn't know about IPX/SPX (http://jetdirect.printerdepo.com/en/hp-jetdirect-print-servers/embedded-web-server-v-38-xx/networking-tab/network-settings/ipxspx/#en_ww-table4.5) typically used by printers to advertise services - a strong signal for recognizing a printer. Even if there is no "conversation" or client using the printer's IPX-based services, just their presence is a signal that the device is probably a printer.

It also doesn't know about other non TCP/UDP services - for example it doesn't know about icmp6 RA (router advertisements) or RSTP (spanning tree) or LLDP/CDP (https://wiki.wireshark.org/CDP). Those are strong signals helping in recognizing a switch/router/SIP phone versus a host or server.

@cglewis
Copy link
Member

cglewis commented Apr 27, 2020

This has been addressed in the rewrite.

@cglewis cglewis closed this as completed Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants