Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

/Net/ReversePathFwdCheckPromisc Behaviour

$
0
0

Hi Smart People! Long time stalker

 

Can someone please explain the criteria for a packet to be dropped when using /Net/ReversePathFwdCheckPromisc = 1 /// Net.ReversePathFwdCheckPromisc = 1

 

I see behaviour on 6.0 and 6.5 where broadcast traffic originating from a forged MAC (non-vNIC MAC on the VM guest) is returning on a redundant pNIC even though this is set to 1. My understanding of this setting was that multicast or broadcast traffic originating from one pNIC in a team would be dropped when returning in a redundant or standby pNIC. Many of my hosts cannot use pNIC teaming or switch LAG/LACP/Teaming because they are homed to non-stacked switches.

 

My understanding of the behaviour must be incorrect as my guest with one vNIC still sees broadcasts originating from itself, coming in from the other pNIC in the team. I had hoped there would be a setting for broadcast listener port on a vSS or vDS. Purportedly if the MAC is of the vNIC on the guest this setting does allow he host to drop the packet, but not if it's forged as well as the vSwitch in promiscuous mode.

 

Anyway, I hope someone smart can answer the question

 

Lots of thanks in advance

David Grocke

South Australian VMware Addict


Viewing all articles
Browse latest Browse all 8132

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>