Waydroid: no internet inside

[sven]

I tried Waydroid on a VollaPhone22 (Focal) after some years, so please be patient. How can I get Internet connectivity inside Waydroid (probably sharing the one from Ubuntu)?

[Ken1971]

@sven hi, I believe it is the Ubuntu touch element that provides wife and mobile provider internet. I don't touch any settings within waydroid itself.

I'm running Ubuntu Touch 24.04 version 280. Waydroid runs excellently......

[readyblue]

@sven +1, same issue

checking from sudo waydroid shell, ip is added correctly, also it can reach outside world, still apps inside does not have internet connectivity

checking waydroid log, no issue found there

[sven]

Thanks for your feedback. Maybe it is this issue? https://github.com/waydroid/waydroid/issues/1958

[sven]

The issue has been fixed and after a new installation I have internet inside waydroid.

[malditobastardo]

For those experiencing this issue and running out of ideas, I was able to solve it by disabling rp_filter.

[Moem]

@malditobastardo That's great. How does one do that, please?

[malditobastardo]

@Moem in my case there were two things I had to adjust to fix this permanently. You will need to use adb/ssh to access your device. Run waydroid (either by cli or by opening waydroid).

1. captive portal issue

inside the container first check if you can at least ping :

sudo waydroid shell
ping 8.8.8.8
ping google.com

If this works but you still don't have access to internet inside the apps, run the following command:

dumpsys connectivity | grep "VALIDATED"

In case the output shows nothing, then it's an issue with android captive portal.

2. rp_filter dropping packages

sudo waydroid shell
cat /proc/sys/net/ipv4/conf/eth0/rp_filter
cat /proc/sys/net/ipv4/conf/all/rp_filter

if the output is not 0, then you can try applying the following:

echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter
echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter

test if this fixed the issue:

ping 8.8.8.8
ping google.com

These are just temporary changes that would help to see if you are experiencing the same issues as me, so don't worry about running these commands because they will not persist after re-launching the app again. In case we identify one (or both) as potential issues. We can try to apply the fixes permanently.

[Moem]

@malditobastardo Thank you! I'll look into this. I appreciate your time and effort!

[malditobastardo]

@Moem You are welcome, hopefully this can help with your issue