IP MAC Device Hostname x.x.x.1 00:E0:18:E4:F5:16 eth0 SERVER x.x.x.2 00:04:75:ED:59:5B eth1 SERVER
SET A
shell> arping x.x.x.1 ARPING x.x.x.1 from x.x.x.69 eth0 Unicast reply from x.x.x.1 [00:E0:18:E4:F5:16] 1.000ms Unicast reply from x.x.x.1 [00:04:75:ED:59:5B] 2.457ms Unicast reply from x.x.x.1 [00:04:75:ED:59:5B] 0.807ms ...
SET B
shell> arping x.x.x.2 ARPING x.x.x.2 from x.x.x.69 eth0 Unicast reply from x.x.x.2 [00:04:75:ED:59:5B] 1.028ms Unicast reply from x.x.x.2 [00:E0:18:E4:F5:16] 202.336ms Unicast reply from x.x.x.2 [00:E0:18:E4:F5:16] 17.779ms Unicast reply from x.x.x.2 [00:E0:18:E4:F5:16] 0.817ms ...
-- Ariz C. Jacinto Systems Administrator Systems Operations Group SPI Publisher Services
ian sison (mailing list) wrote:
FYI, "ARP Flux" i looked it up in Google:
ARP flux occurs when there are multiple ethernet adaptors (often on a single machine) which are willing to respond to an ARP query. Other machines on the segment may have ARP cache entries for either of these link layer addresses, and in fact the link layer address may be address A sometimes, and address B other times. There is nothing intrinsically wrong with ARP flux, however if you need greater control over the flow of traffic through your network you will want to avoid it. [1]
-- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
