No internet in waydroid

[Etaash-mathamsetty]

I don't have any internet inside waydroid, i feel like I missed some configuration step, can anyone help?

[vega-d]

Just updated waydroid from sep 11 build. Internet connection for container doesn't work now, would like to know what went wrong too.

[Vormalzalek]

Hello all, first of all congratulations. Amazing achievement.

Now, no internet in waydroid after first reboot from a fresh install (browser and F-droid say no connection) on Manjaro Phosh in the Pinephone. Main OS has internet connection.

Is there a way of troubleshooting the connection status, from the command line or something?

[whyc3]

In my case using Fedora 35 with XanMod Kernel, I had the same issue, and all I did was restart the waydroid-container service :
sudo systemctl waydroid-container restart

[Aman9das]

Yes waydroid session stop and then waydroid session stop fixed it for me

[Quackdoc]

@Etaash-mathamsetty is this still an issue?

[Etaash-mathamsetty]

@Etaash-mathamsetty is this still an issue?

not anymore

[meisme-dev]

still happens for me

[Etaash-mathamsetty]

still happens for me

you might have to modify some config files related to dnsmasq, which is what I did to get it working. you also might have to disable systemd-resolved

[azul]

None of the above did the trick for me.

[meisme-dev]

It works for me on Fedora but not Arch for some reason, and I tried all the above steps. Does Arch do anything differently in terms of networking? Both my installs use network-manager and systemd-resolved (I did try dnsmasq on Arch and that also did not work).

[Etaash-mathamsetty]

It works for me on Fedora but not Arch for some reason, and I tried all the above steps. Does Arch do anything differently in terms of networking? Both my installs use network-manager and systemd-resolved (I did try dnsmasq on Arch and that also did not work).

I used to use ubuntu back then, but now I use arch, and it's way better than ubuntu (for waydroid at least)
systemd-resolved won't work, you have to use dnsmasq, here is how you fix it
systemctl disable systemd-resolved
systemctl enable dnsmasq
you can also go ahead and systemctl disable systemd-networkd cuz its useless lol (with network manager at least)
sudo nano /etc/dnsmasq.conf
find #bind-interfaces (or somthing like that)
uncomment it, save
systemctl restart dnsmasq.service
then you should be good to go
you would also need to follow these steps if you are using virtual machine manager

[DFF-fred]

On Fedora 36 here, and I'm having the same 'no internet' problem. I'm running Waydroid from the copr repository. What should I do from there to troubleshoot and eventually fix the issue?
Thank you.

[jkcdarunday]

No internet on Arch as well. Tried out running dnsmasq by itself and also making NetworkManager run its own dnsmasq, both did not work.

From what I've investigated so far, it looks like the issue is not related to DNS or DHCP:

1. Ran ifconfig in the waydroid shell and checked if the ip is in the subnet of the host machine, it is so it looks like DHCP works.
2. I tried pinging/curling an IP address directly which should work even if DNS does not, this didn't work pointing me to a routing issue.

Right now I think the issue that I'm having could be related to the iptables NAT forwarding setup in /usr/lib/waydroid/data/scripts/waydroid-net.sh.

[jkcdarunday]

Finally got it to work, looks like there's a conflict with docker's iptables rules.
Ran the ff. as root on Arch:

1. systemctl stop docker
2. systemctl restart iptables
3. ip link delete docker0
4. Restarted waydroid-container and started my waydroid session