![]() ![]() There might be some tool which does that for you, but I don't know any, so you'll have to script it. Yes, it's that difficult, and if you want to do it properly, you can't take shortcuts. Every device that is connected via WLAN will see the 'wrong' MAC address of every device that is connected via LAN, and vice. Windows will also find the 'wrong' MAC address if the Windows PC is connected via LAN, while the target phone is connected via WLAN. The only command line tool I can think of for this is arping, but there's probably a better way.įor each of the IPs, do a DNS reverse lookup to uour home router, e.g. If this guess is correct, it's purely a router issue, not an issue of Linux vs. arp-scan is also less reliable, because it will try to get ARP responses over WLAN, but the hotspot already knows exactly which machines are connected.įor each of those MACs, find the corresponding IP address. That's more reliable than the arp cache, because the arp cache may not include all connected machines, and it may also include other machines on other LANs etc. Get MACs of connected stations using iw wlan0 station dump, where wlan0 is the IF of your hotspot. Typically, your home router runs a DNS server, where you either can enter which name belongs to which MAC address, or it automatically uses names if they are provided by DHCP. The ARP protocol tells you which MAC address belongs to which IP address (OSI level 3). Quick reminder of the layers involved: LAN and WLAN communicate using MAC addresses (OSI level 2). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |