New answers tagged arp
Providing no MAC-aware security is in the network, there is no problem to move MAC from one system to another. The only condition - do not allow duplicated MACs simultaneously. As soon as a switch receives a frame with old MAC from new target It should rewrite MAC table and make the target accessible. You can test It separately in advance.
Oops! I finally found the working solution! I spent about 10+ hours spreaded on three days for this problem, but the solution is not clean, is closer to work-around. I need real solution or better work-around for this. please help. anyway, I found below information from vmware cummunity. (root cause of the problem is related to vmware.) ...
sysctl -w net.ipv4.conf.all.arp_ignore=1 1 - reply only if the target IP address is local address configured on the incoming interface sysctl -w net.ipv4.conf.all.arp_announce=2 2 - Always use the best local address for this target. In this mode we ignore the source address in the IP packet and try to select local address that we prefer for talks with ...
Is host2 trying to be helpful by routing for you? Have you tried with: echo 0 > /proc/sys/net/ipv4/ip_forward on host2?
Solved. The issue is with SCCM 2012 SP1, a service called: ConfigMrg Wake-Up Proxy. The 'feature' does not existing SCCM 2012 RTM. Within 4 hours of turning this off within the policy, we saw steady drops in CPU usage. By the time 4 hours was up, ARP usage was merely 1-2%! In summary, this service does MAC address spoofing! Cannot believe how much havoc ...
Top 50 recent answers are included