arpalert uses ARP address monitoring to help prevent unauthorized connections on the local network. If an illegal connection is detected, a program or script is launched, which could be used to send an alert message, for example.
| Tags | Security Logging Networking Monitoring |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX Solaris Linux BSD FreeBSD OpenBSD NetBSD |
| Implementation | C |
| Translations | English |
Recent releases


Release Notes: A bug in lease file reading has been fixed. There is a new script in contribs that sends a Zenity alert on Ubuntu.


Release Notes: An error message was fixed. The script API documentation was updated. New API functions were added.


Release Notes: A minor OpenBSD bugfix. Very minor code optimization. This release checks the string representation of MAC address memory size, allocates static memory for many buffers, and has OpenBSD Makefile compatibility.


Release Notes: Default config file syntax corrections and comments were added. The list of MAC vendors is loaded only in debug mode. A vim syntax file was added.


Release Notes: A bugfix in ARP self-test detection. A bugfix in the scheduler. Code cleanup.
Recent comments
12 Oct 2006 09:31
Re: Fails to run
> The package configures & compiles.
> At runtime, "arpalert -d" produces:
> Aborted
> and the /var/log/messages shows:
> Oct 6 09:09:53 beast2 arpalert:
> [loadmodule.c 37] stat[2]: No such file
> or directory ()
>
> Ideas?
> Thanks!
> Tom
>
>
hello,
the version 1.1.2 fix this bug.
Thierry
06 Oct 2006 06:10
Fails to run
The package configures & compiles.
At runtime, "arpalert -d" produces:
Aborted
and the /var/log/messages shows:
Oct 6 09:09:53 beast2 arpalert: [loadmodule.c 37] stat[2]: No such file or directory ()
Ideas?
Thanks!
Tom
18 Dec 2004 18:57
Project development branch
The new branch add a function to get invalid mac adress information on manageable switch.
I tested this functionality only with 3COM Superstack switch. I search if this run with other switchs.
Thanks for help.
This new version send a alert mail without external script.
11 Nov 2004 07:26
Project status
At this time, the daemon arpalert run from 1 week on my job's server.
There are no problems.
I'm no found a bugs