- #HOW TO STOP A DEVICE FROM CONNECTING TO NETWORK MAC ADDRESS PC#
- #HOW TO STOP A DEVICE FROM CONNECTING TO NETWORK MAC ADDRESS WINDOWS#
But for your purpose can be used common adapter type I think. The Wi-Fi adapters for sniffing must support special "monitor" mode. Search for a Wireless traffic sniffing to get detail information. It is not recommended for wireless analysis.)
#HOW TO STOP A DEVICE FROM CONNECTING TO NETWORK MAC ADDRESS WINDOWS#
(The Windows OS has very limited wireless capture capability excluding special Wi-Fi cards.
#HOW TO STOP A DEVICE FROM CONNECTING TO NETWORK MAC ADDRESS PC#
You will need a Linux PC as an analyzer and a Wi-Fi card/adapter. The test procedure is similar like in Ethernet case, but instead of switch a wireless environment is used. If you want to speed up the sending of the first packets, manually set the IP addresses of both devices and start ping from the analyzer towards PC1 before connecting PC1. The test done by this way will show you MAC addresses of PC1 early after cable connecting to PC. No other devices are connected excluding switch which has no MAC (if it is unmanaged switch). The remaining visible frames in Wireshark contain either PC1 original MAC or PC1 fake address. Right click to displayed MAC, in context menu select select "Apply as filter" -> "Not Selected".) Any frames having this source MAC address will be hidden. You can filter out the analyzer MAC address (and any other eventually) in Wireshark window very easy. The second MAC is from analyzer interface. Probably at least two MAC's will be visible.It can be found at the L2 (Ethernet) part of output. All these frames/packets have visible source MAC addresses of sending device. Any PC excluding very special cases will start sending some network requests like a DHCP discovery, ARP broadcasts etc. Connect the PC1 to the switch and watch Ethernet frames displayed in Wireshark.Start Wireshark application on analyzer, select the Ethernet interface for capturing and start capturing process.It is not necessary, only the L2 is important now. No problem if analyzer has no IP address for first test. Connect analyzer to switch and ensure its Ethernet interface is up.I suppose the first device name is "PC1".
You will need a second device (PC or server, let its name is "analyzer") with installed Wireshark application and a small network switch too. I recommend to verify your MAC visibility by real test. If you wish to hide your MAC in a local network (LAN, inside the broadcast domain), it is harder. Any network router is the OSI layer 3 (元) device and removes any layer 2 information including the MAC in normal circumstances. It means the MAC cannot go through router to other network segments. The MAC addresses visibility is limited to the broadcast domain only.