An Experimental Study and Novel Approach for Detection and Suppression of Rogue Access Point in Wlan

Abstract

Research into wireless network communication is vast, and many wireless security companies and organisations have failed to achieve wireless airspace accuracy because of its narrow, limited, and restricted capacity to network teams. Information transmitted through a wireless network uses radio frequency. Antennas, routers, access points, Wi-Fi cards, and more must all be 802.11 compliant to make up a WLAN. Data transmission, encoding, and decoding are all taken care of by 802.11-compliant WLAN parts. Annual pen-testing for acceptability, especially for public Wi-Fi, will become unnecessary as the number of wireless attacks rises. Any computer or laptop with an integrated Wi-Fi network adapter and access to the internet is vulnerable to hackers while using a public Wi-Fi network. Infections spread rapidly through public WLANs. This study compares and contrasts the key characteristics and terminology of a rogue access point (a WLAN threat) with those of an Access Point, the dangers of a rogue AP for public Wi-Fi, the relationship between rogue APs and attacks, and the various ways in which a rogue AP could carry out malicious actions or launch attacks against a next-generation wireless network. The conventional approach centres on comparing several parameters taken from beacon frames. The MAC address and SSID of the access point are examined, among other things. A server-based technique involves installing RAP detection software on a centralised server, which then performs an operation over the entire network in search of RAP. By contrast, a client-based approach relies on the device itself to monitor the network and verify the authenticity of an access point (AP) before establishing a connection with it. To name just a few, recent studies make use of clock skew, wireless traffic monitoring, encryption, authorization, a timing-based technique, RSS analysis, bottleneck bandwidth analysis, and sequential hypothesis testing. Some issues with current methods include: reliance on a faulty clock skew solution assumption;