vedalken254
New Member
No. Eth0 happens to be receiving the traffic I admit, however the IP was assigned to eth0:0 which typically means a virtual MAC address on the node. He claims he removed the eth0:0 interface and that's when this traffic flood started. If the VMAC is gone, why is the main physical MAC receiving the old VMAC's data? ARP caching wouldn't explain that.He hasn't disabled eth0 (and wouldn't do it of course), and that's where the packet is coming from and going to. He has just removed some ip alias, i.e. removed the ip from the box. Which means now it's routed, instead of handled locally.
@KuJoe 162.211.66.0/24 (or whetever the maks) is probably not your main subnet, right? It's an additional subnet added to your VLAN and eth0 is not from this subnet?
You should do
ip route add 162.211.66.0/24 dev eth0
Again adjust the subnet mask accordingly.
EDIT: it seems that as of CentOS 6, they re-worked the ethx:y system. This is something I was unaware of. My apologies.
@KuJoe , Answer something for me: have you assigned the IP to a VPS on that node with the VPS having a different MAC address than the host (which should be always the case last I checked)? If so, this ARP cache crap wouldn't be the cause as the MAC address would be different and shouldn't go to the host node regardless.
Last edited by a moderator: