Then type '/sbin/arp -a' and you will see your IP address to MAC address associations. While you have an active connection, ping any active host. So the BSSID is the MAC address of the wireless access point. Note: When using with Linux you will need to add sudo to get a full scan. All the access points Ive seen have the MAC address printed on the outside label.

You can also use the command-line tool as: $ WIFI=wlan0 wifiscan You can use it in your Go code as: wifis, err := wifiscan.Scan() Other systems are not supported at the moment (although, as long as they are Linux-based I believe you can install iwlist). For Linux this is iwlist, for Windows it is netsh.exe and for OS X it is airport.

Wifiscan works by calling the OS-specific Wifi scan utility and parsing the output. It should work on most Linux installations as well as Windows and OS X. This would mean that IP address you learned in previous steps was completely useless to you in terms of knowing actual network infrastructure.A platform-independent WiFi scanning library for getting BSSID + RSSI from nearby access points.

After passing captive portal, it is possible (but not common) that access point automatically re-associates and gives you completely different IP address (and access point also has different IP address now, from completely different subnet).

If access point implements captive portal, then your network access may be restricted until you open up web browser and (depending on wireless provider) either accept usage terms, provide some credentials or pay with credit card. However, even at that point, full network connectivity cannot be assumed.

After getting IP address, client can talk to access point and finally knows its IP address (it was served as default router in DHCP ack) - and that would be the answer to your question (yes, that late in the game!).

After getting successful DHCP ack with new IP address, client can proceed to next step. To proceed further, your client sends DHCP request, which is served by access point. Technically, you can use sniffer at this stage to scan the network and find out IP addressed used, but most sniffers don't like to work with 0.0.0.0 address.

After association, your client (which is typically configured to use DHCP) has no IP address assigned (its IP address is 0.0.0.0).

If access point is using WPA/WPA2 and you don't know the password, then you cannot proceed to further steps, and certainly cannot know anything about IP address of target access point. Getting WiFi to work involves following steps: You can't do that if target access point is protected with WPA/WPA2.

How to find bssid linux