Implementation of timeout on new MAC discovery

Mirekmal
Member, Beta Tester Posts: 68
✭✭✭




Since many virtualization platform assign random MAC address to virtual machins on startup, it creates lots of false alarms due to these MACs being detected on LAN and then immediatelly vanishing from network. It is the case even if machines are configured with static MAC addresses. I experienced this in ESXi and even running Windows in Bootcamp on Mac. Other users reported similar case in MS SCVMM also.
Would it be possible to implement configurable timeout after which newly discovered MAC address raises alarm, if still present on network? This way MAC addresses that are in range for less that a ~minute could be discareded and only these that are 'more permanent' would trigger alarm. Obviously such MACs should be by default blocked for security.
Would it be possible to implement configurable timeout after which newly discovered MAC address raises alarm, if still present on network? This way MAC addresses that are in range for less that a ~minute could be discareded and only these that are 'more permanent' would trigger alarm. Obviously such MACs should be by default blocked for security.
Tagged:
0
Comments
-
Just turning this one into an ideas thread so others can vote. Cast your vote if you'd like to see implemented too.
Community Manager at Fing
0
Categories
- 5.6K All Categories
- 2.8K Ask about Connected Technology
- How To...
- 1K Devices & Security
- 1.5K Network Troubleshooting & Connectivity
- 112 General Discussion, Weird & Wonderful
- 42 Network Infrastructure
- 5K Ask about Fing
- 502 Fing Account Change Request
- 1.1K Fing Desktop
- 1.3K Fing App
- 1.6K Fingbox
- 485 Announcements, Beta Testing & Release Notes
- 157 Community Updates
- 24 Getting started
- 13 Community User Guides