Azure multi-NIC routing - Phantom Static Routes (bug?)
Today we found specific IPs in a 3 NIC Azure Marketplace install listed in the routing table going out of the wrong interface. We cannot figure out how these static routes got entered, why they exist or how to remove. (See screen shot). The "gateway IP" shows a MAC address (which is very very odd). Has anyone seen this on an Azure pfSense VM? This issue creates a problem, because those IP won't be routable any longer since they are static out the wrong interface. We got it resolved today, temporarily, by reordering the interfaces to make the routes "valid" putting those IPs on the interface the routes are for - but, this is hardly a solution.