wireless

Background: I'm teaching myself about packet sniffing. I run a very simple server in one shell, telnet to it from another, then try different methods to sniff on traffic. When I use raw sockets (IPPROTO_TCP), I capture what I send fine. I capture merely what I send, nothing else from the internet. libcap's behavior confuses me as follows: (1) First, to check it out, I capture all devices with pcap_findalldevs (see (2) below as well). I find wlan0 fine. If I connect to 'all traffic' (per the man page) using if ( !( pcap_handle = pcap_open_live(NULL, 4096, 1, 0, errbuf) ) ) I capture what I send

I'm using the Managed WiFi API and the example code: string profileName = "Cheesecake"; // this is also the SSID string mac = "52544131303235572D454137443638"; string key = "hello"; string profileXml = string.Format("<?xml version=\"1.0\"?><WLANProfile xmlns=\"http://www.microsoft.com/networking/WLAN/profile/v1\"><name>{0}</name><SSIDConfig><SSID><hex>{1}</hex><name>{0}</name></SSID></SSIDConfig><connectionType>ESS</connectionType><MSM><security><authEncryption><authentication>open</authentication><encryption>WEP</encryption><useOneX>false</useOneX></authEncryption><sharedKey><keyType

参考：源文档 < https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx > 安装b43 在光盘上： cd /cdrom/pool/main/b/b43-fwcutter/ sudo dpkg -i b43-fwcutter* 下载驱动： b43legacy - http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o b43 (10.04 Lucid Lynx) - http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 b43 (12.04 Precise Pangolin) - http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.3_mipsel.tar.bz2 b43legacy sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o b43 (10.04 Lucid Lynx) tar xfvj broadcom-wl-4.150.10.5.tar.bz2 sudo b43-fwcutter -w /lib/firmware broadcom-wl-4.150

I was wondering if there was anybody which have any information regarding alternatives on Wireless Accessory Configuration on the Android platform. I know TI has a solution called simpleconfig, but I was wondering if there was any "generic" method which is not linked to a specific chip manufacture? Is the Android platform limited to having a long and difficult configuration sequence when getting wifi accessories on the network? Regards 来源： https://stackoverflow.com/questions/27402488/wireless-accessory-configuration-alternative-on-android-platform

I have seen several projects now which derive novel spatial information from radio data collected from a typical wireless router: http://wisee.cs.washington.edu/ http://www.extremetech.com/extreme/133936-using-wifi-to-see-through-walls The idea of using a wireless router as a sort of passive radar is fantastic. I am very interested in experimenting with data collected from a wireless router myself, but there is little information on how to go about actually interfacing with a wireless router and getting a raw stream of information collected by the device. Similar questions have been asked on

When connecting a device (like LG G2) with ADB Wireless, the device shows up as unauthorized. Why does this happen? From Android 4.2, every ADB device needs to be authorized for a computer to connect. This is done for security. So when a USB is connected a prompt comes asking to authorize the device when USB debugging is set. But does not happen for WIFI ADB. So the workaround is to connect the device by USB, accepting the machine always. Then when the Wireless ADB is tried, it should work. Solution 1 Connect device(over USB) to computer. 2 Authorize adb device, so it can communicate(handshake

I'm using the reachability API to detect my current connection, but I can only distinguish between WIFI and 3G. I get the following flags: LTE: kSCNetworkReachabilityFlagsIsLocalAddress|kSCNetworkReachabilityFlagsIsWWAN|kSCNetworkReachabilityFlagsTransientConnection|kSCNetworkReachabilityFlagsReachable WIFI: kSCNetworkReachabilityFlagsIsDirect|kSCNetworkReachabilityFlagsReachable The problem is that LTE returns the same flags as a 3G connection. Is there any way to determine whether the user currently has LTE or 3G? As of iOS 7, you can find this out using the currentRadioAccessTechnology