![]() |
![]()
| ![]() |
![]()
NAMEipguard - tool designed to protect Ethernet LAN IP address space by ARP spoofing. SYNOPSISipguard [-h] [-ajgrxziovd] [-f ethers] [-l log] [-p pid] [-m mac] [-c filter] [-u seconds] [-k seconds] [-n fakes] [-t mseconds] [-b buf] [-s user] <iface> DESCRIPTIONipguard listens network for ARP packets. All permitted MAC-IP pairs listed in 'ethers' file. If it receives one with MAC-IP pair, which is not listed in 'ethers' file, it will send ARP reply with configured fake address. This will prevent not permitted host to work properly in local ethernet segment. OPTIONS
EXAMPLES
TIPSFirst MAC-IP pair in `ethers' always must be self MAC/IP addresses. Normally them automatically taken from listening interface. But if `-j' option specified then make sure that first pair is a source MAC/IP. If you want to start more than one ipguard on segment for redundancy, you must specify same fake MAC address for every ipguard and find method to synchronize `ethers' files. SIGNALSFILES
SEE ALSORFC 826, ethers(5), tcpdump(1), pcap(3), libnet BUGSDo not use wildcard IP 0.0.0.0 in `ethers' with -x option. Legal clients will be banned. Discovered by irix. Strange bug with libnet_get_hwaddr() isn't working on OpenBSD 4.0 discovered by irix. Use -j option. ipguard will not prevent changing MAC address along with IP by pirate. Signals HUP, USR1 or USR2 works only when received new ARP packet. It's not a bug, it's a feature. When using -s <user> option ipguard will drop root privileges after creating log and pid files. So it will not delete or reopen these files. Probably too many command line options. Another one or two and i'll put them all into /etc/ethers as comments. ipguard was written as simple small tool and i haven't any plans for support of external databases SQL/LDAP/Whatever. Use scripts. AUTHORSeaD <sead at deep.perm.ru>
|