The question says it all. I am learning my way around all the network connections my phone wants to establish. System is official /e/os on a Fairphone 5. Running adb shell netstat -eltup I get Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program Name tcp 0 16 0.0.0.0:50057 0.0.0.0:* UNKNOWN radio 29453 1393/netmgrd tcp 0 16 0.0.0.0:50026 0.0.0.0:* UNKNOWN radio 30870 1393/netmgrd tcp 0 16 0.0.0.0:50058 0.0.0.0:* UNKNOWN radio 29468 1393/netmgrd tcp 0 16 0.0.0.0:50027 0.0.0.0:* UNKNOWN radio 30871 1393/netmgrd tcp 0 16 0.0.0.0:50059 0.0.0.0:* UNKNOWN radio 29469 1393/netmgrd tcp 0 16 0.0.0.0:50028 0.0.0.0:* UNKNOWN radio 30832 1393/netmgrd [...] udp 0 0 0.0.0.0:50043 0.0.0.0:* ESTABLISHED radio 29431 1393/netmgrd udp 0 0 0.0.0.0:50050 0.0.0.0:* ESTABLISHED radio 30838 1393/netmgrd udp 0 0 0.0.0.0:50051 0.0.0.0:* ESTABLISHED radio 30839 1393/netmgrd udp 0 0 0.0.0.0:50054 0.0.0.0:* ESTABLISHED radio 29454 1393/netmgrd udp 0 0 0.0.0.0:50055 0.0.0.0:* ESTABLISHED radio 29455 1393/netmgrd udp 0 0 0.0.0.0:50058 0.0.0.0:* ESTABLISHED radio 30880 1393/netmgrd udp 0 0 0.0.0.0:50059 0.0.0.0:* ESTABLISHED radio 30881 1393/netmgr` I just included a selection, the complete list is longer. Is this expected behavior?

am trying to disable webrtc on the root level Is there any guide to do that want to stop IP leaks while using a proxy it's easy in chrome but not for other apps..

I have a drone remote that has android in it. It has an internal telemetry server that is publishing data on localhost:14445 via UDP. When I open the hotspot from this device and connect to it with my computer I'm getting the usual 192.168.43.xx type of IP address. I can ping internal IP addresses of the remote (other than 192.168.43.xx form, for example, devices attached to eth0 interface with IPs like 192.168.144.xx) so I have some sort of access to internal IP's from the hotspot. But I cannot communicate with the internal UDP port I mentioned before. As Wireshark shows, something is blocking the UDP connection between hotspot and internal IPs. I tried port forwarding and it didn't work but I don't know if I did it correctly. I have busybox and root access, please help me. I can give further information upon request.

I have a Redmi Note 3 (unrooted) phone running MIUI Global 10.2 [Android version 6.0.1 MMB29M] I have installed AdGuard to monitor the traffic that my phone sends/receives. While checking the 'Filtering Log', I see few connections that the app "Android OS" makes to the remote address "118.189.138.5:123" (see screenshot). As you can see from the screenshot, the requested URL is having a "UDP" connection protocol. Now, when I do a search for this IP address, I see that it belongs to "M1 Connect Pte Ltd" in Singapore. https://www.speedguide.net/ip/118.189.138.5 I also noticed similar UDP connections to these IP addresses: 95.216.192.15 belongs to "D2 Internet Investment Ukraine ETTH broadband" in Ukraine 133.243.238.163 belongs to "National Institute of Information and Communicatio" in Japan and the strangest of all 202.12.97.45 belonging to "Ministry of University Affairs" in Thailand So my question is why would Android OS make connection to this IP addresses. What are these connections for? Am I missing something here or are these some legit connections used for some 'good' work? Is my phone connecting and leaking some information? Hoping that some expert on networking will answer this.

I am capturing audio from a radio device to my android using tcpdump. How can I take this cap file and replay the UDP stream within it? As I want to replay the audio I got from the radio.

There are multiple TCP/UDP based VPN apps which can provide free internet. I'm no expert in this field but according to what I understand is that these apps can work if you are able to browse at least one website without any internet plan. They pass all the normal internet traffic through that one website so that your operator thinks you are still browsing that one free website. Can someone throw some light on how this process exactly works and can I use it to make my internet work faster because when I exhaust my data limit still some websites work at full speed.

So I have been running an app on android (Samsung Note 4) with out trouble until the latest phones started coming out with android 7+ (Samsung S8, OnePlus3T). Now I find that UDP is blocked on the phone in the app. Is there a **new setting that blocks UDP broadcasts**? I used Evothings app to test that UDP is blocked. I noticed a change with the way WiFi works on android. If the WiFi connection doesn't have internet, the system seems to behave differently. Does WiFi work differently if there is no internet? Again, it still works with the older versions of android. If you have come across this problem please share.

I have the following setup: Android Galaxy S5 Mini. Android version 5.1.1. I have 2 network interfaces: 1. Interface1 with ip: **192.168.5.1** 2. Interface2 with ip: **192.168.5.10** I create a DatagramSocket using Android SDK and bind it to address: 192.168.5.10(Interface 2), port 2525. I put this socket in receive and wait for packets. I use another device to send the packets. Packets from ip address: **192.168.5.4** is received. Packets from ip address(different device): **192.168.5.1** (same as the device's Interface1 ip) is never received. It seams that the network stack rejects packets which have source ip address which exists in the device, regardless of the interface it was received in. If I modify the ip address for Interface1 to something other than 192.168.5.1 it works fine. Devices on which it **didn't** happen: 1. Samsung tablet T113 Android 4.4.4 (Stock rom) 2. LG G4 Android 6.0 (Stock rom) 3. LG Nexus 5X Android 7.1.2 (Stock rom) Devices on which it **did** happen: 1. Galaxy S5 Mini Android 5.1.1 (Stock rom) 2. Galaxy Note 3 Android 6.0.1 (CyanogenMod) 3. One+1 Android 6.0.1 (CyanogenMod) What is the mechanism which rejects the packet with source IP **192.168.5.1**(same as the device's Interface1 ip)?

What is an easy method for an Android device to tell whether a data connection (either WiFi or mobile data alone) has UDP traffic blocked? Many corporate and public access points restrict UDP access, and I am looking for a way to detect this manually. I am interested in this because real-time VOIP applications, for example, should not be expected to work with the same performance on TCP as on UDP. For the purposes of this question, I would assume that the data connection is either: 1. using hole-punching or 2. blocks all UDP traffic that is not DNS-related. Also, please assume the Android device is not rooted.

We've an android TV connected on a restricted WIFI network. Its IP adress is fixed. My problem only the web browser is working well. All other application can not go on the web or synchronize. We got this netstat: u0_a67@android:/ $ netstat Proto Recv-Q Send-Q Local Address Foreign Address State tcp6 0 0 ::ffff:10.212.127.251:38388 :::* LISTEN tcp6 0 1 ::ffff:10.212.127.251:39643 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:34495 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:46563 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:46332 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 0 ::ffff:10.212.127.251:53406 ::ffff:14.17.41.151:443 ESTABLISHED tcp6 0 1 ::ffff:10.212.127.251:57860 ::ffff:103.7.30.158:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:39039 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:36796 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:53894 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:53360 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:34809 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:50549 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:38316 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 1 ::ffff:10.212.127.251:43701 ::ffff:157.169.25.15:80 CLOSE_WAIT tcp6 0 0 ::ffff:10.212.127.251:38207 ::ffff:216.58.198.14:80 ESTABLISHED udp6 0 0 :::56331 :::* CLOSE udp6 0 0 :::56456 :::* CLOSE udp6 0 688 :::1900 :::* CLOSE udp6 0 0 :::1900 :::* CLOSE udp6 0 0 :::51117 :::* CLOSE u0_a67@android:/ $ Regarding on the web information, we opened the TCP port 5228 in OUTPUT mode and we opened the TCP port 38388 in INPUT mode as it's in listen status in the netstat. That doesn't solve the problem. Any idea about the list of TCP port need to be opened on the network for android working? Thanks for help.