broetchenrackete36

Is there any information I could provide that could help solve the issue?

Changing nameserver to ipv6 didn't help unfortunately. Using Termux' ping inside proot actually works... :) ```bash ~ $ proot-distro login alpine -- /data/data/com.termux/files/usr/bin/ping google.com PING google.com (142.251.37.14) 56(84) bytes of...

```bash ~ $ strace -c ping -c 2 -n github.com PING github.com (140.82.121.4) 56(84) bytes of data. 64 bytes from 140.82.121.4: icmp_seq=1 ttl=57 time=24.1 ms 64 bytes from 140.82.121.4: icmp_seq=2...

```bash bluemond16:53~$ which ping /usr/bin/ping ```

This is not a problem with alpine. It's a problem with proot. Termux: ping works, pkg upgrade works, all fine. Proot-distro based: - archlinux: ping and pacman are not working,...

```bash ~ $ proot --bind=/dev/null:/dev/socket/fwmarkd curl 'http://1.1.1.1' WARNING: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt" 301 Moved Permanently 301 Moved Permanently cloudflare ~ $ proot curl 'http://1.1.1.1'...

@michalbednarski DNS traffic seems to be working, because running dig inside proot works fine. Other traffic works fine too.

@michalbednarski i manually installed dig (bind package) with it's dependancies and it's working fine, even with '--isolated'... ```bash ~ $ proot-distro login archlinux --isolated [root@localhost ~]# strace -c dig github.com...

So the ncsd.py script is indeed working, at least for ping and pacman. Here are the results of the two commands (without ncsd.py running): ```bash ~ $ proot-distro login alpine...

Oops, not sure if your script was running or not during the commands... Here is the output with the script not running for sure: ```bash ~ $ proot-distro login alpine...