Skip to main content
Android Enthusiasts

Return to Answer

deleted 4 characters in body
Source Link
ce4
ce4
  • 14.5k
  • 10
  • 61
  • 106

You can't monitor your the Wi-Fi network using tethering even if Android supports promiscuous mode for the Wi-Fi chipset.

Reason:
Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure Wi-Fi traffic this way.

What you can do:
Have a custom firmware installed (e.g. CyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)

You can't monitor your the Wi-Fi network using tethering even if Android supports promiscuous mode for the Wi-Fi chipset.

Reason:
Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure Wi-Fi traffic this way.

What you can do:
Have a custom firmware installed (e.g. CyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)

You can't monitor your Wi-Fi network using tethering even if Android supports promiscuous mode for the Wi-Fi chipset.

Reason:
Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure Wi-Fi traffic this way.

What you can do:
Have a custom firmware installed (e.g. CyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)

Improved readability and added link to CyanogenMod web-site.
Source Link
Zuul
Zuul
  • 8.7k
  • 3
  • 33
  • 68

You can't monitor your the WiFiWi-Fi network using tethering even if Android supports promisciouspromiscuous mode for the wifiWi-Fi chipset.

Reason: Tethering
Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure WiFiWi-Fi traffic this way.

What you can do: Have
Have a custom firmware installed (e.g. CyanogenModCyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)

You can't monitor your the WiFi network using tethering even if Android supports promiscious mode for the wifi chipset.

Reason: Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure WiFi traffic this way.

What you can do: Have a custom firmware installed (e.g. CyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)

You can't monitor your the Wi-Fi network using tethering even if Android supports promiscuous mode for the Wi-Fi chipset.

Reason:
Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure Wi-Fi traffic this way.

What you can do:
Have a custom firmware installed (e.g. CyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)

Source Link
ce4
ce4
  • 14.5k
  • 10
  • 61
  • 106

You can't monitor your the WiFi network using tethering even if Android supports promiscious mode for the wifi chipset.

Reason: Tethering does NAT internally and assigns you an IP in a 192.168.* private range via a DHCP daemon running on your phone. There's no way you can see pure WiFi traffic this way.

What you can do: Have a custom firmware installed (e.g. CyanogenMod) and do a tcpdump on your phone itself (if it supports both PROMISC mode and tcpdump)