Hi there,
is nv2 vulnerable to de-auth attack? Do i need managment-protection settings (as i know nv2 is NOT using the security-profile) so i think it will not have any effect?
Regards,
Joerg
Hi there,
is nv2 vulnerable to de-auth attack? Do i need managment-protection settings (as i know nv2 is NOT using the security-profile) so i think it will not have any effect?
Regards,
Joerg
NV2 is MicroTik’s own protocol. Therefore, by itself offers some sort of protection. Further, it does implement a security mechanism. Do refer to wiki page: http://wiki.mikrotik.com/wiki/Manual:Nv2#Security_in_Nv2_network
So if configured correctly, I’d say you have a pretty good level of protection from deauth.
Set AP side, protocol NV2 only and there you go. Additionally, use security preshared key.
Good luck!
deauth attack is based on something that triggers a disconnect, so that the attacker connects in the disconnected client’s place.
but … nv2 is mikrotik only protocol. how will the attacker connect to it?
also, we made “management frame protection” for regular 802.11:
http://wiki.mikrotik.com/wiki/Manual:Interface/Wireless#Management_frame_protection
the same technology is included in nv2
You say that the same management frame protection is included in the Nv2 technology. However on the Nv2 manual page (http://wiki.mikrotik.com/wiki/Manual:Nv2#Security_in_Nv2_network) it states, “Interface using Nv2 protocol ignores security-profile setting.” The security-profile is where management frame protection is configured.
Looking from clarification and updates to the manual from MikroTik staff. Thanks!