Arping is a util to find out if a specific IP address on the LAN is 'taken' and what MAC address owns it. Sure, you *could* just use 'ping' to find out if it's taken and even if the computer blocks ping (and everything else) you still get an entry in your ARP cache. But what if you aren't on a routable net? Or the host blocks ping (all ICMP even)? Then you're screwed. Or you use arping. Why it's not stupid: Say you have a block of N real IANA-assigned IP-addresses. You want to debug the net and
NetDB can inventarize and historize MAC address allocation on network switches and ARP tables on routers. It stores those using MySQL. It supports extensive switch, VLAN and vendor code reports, or tracks static IP addresses, and record neighbor discover. It provides a CLI interface and a web interface, or generate CSV lists.
ArpON is a daemon that handles and inspects ARP (address resolution protcol) requests and thusly can prevent MITM attacks, ARP sppofing, cache or route poisoning. It also blocks related network attacks like ARP sniffing, hijacking, or injection, or higher-level DNS and HTTP request/session spoofing, or SSL/TLS circumvention. It also protects networks with proactive (network interface or system shutdown) and dynamic ARP traffic inspections in complexer setups.
|