You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Azure, local MAC address to IP mappings have no meaning because all VMs run in VLANs. Thus, we can fill the destination MAC address in outgoing ethernet packets with anything that we want. However, occasionally, it needs to be a specific address for the packets to flow. For example, Windows expects 12-34-56-78-9a-bc
Context
On Azure, local MAC address to IP mappings have no meaning because all VMs run in VLANs. Thus, we can fill the destination MAC address in outgoing ethernet packets with anything that we want. However, occasionally, it needs to be a specific address for the packets to flow. For example, Windows expects 12-34-56-78-9a-bc
Proposed Solution
We should make this constant configurable:
DUMMY_MAC_ADDRESS
The text was updated successfully, but these errors were encountered: