No internet in waydroid #143

Etaash-mathamsetty · 2021-10-10T03:32:39Z

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

vega-d · 2021-10-17T08:11:44Z

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

Vormalzalek · 2021-10-22T14:48:50Z

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 · 2021-11-12T17:04:57Z

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 · 2021-11-20T04:16:55Z

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

Quackdoc · 2021-12-30T00:08:43Z

@Etaash-mathamsetty is this still an issue?

Etaash-mathamsetty · 2021-12-31T02:50:47Z

@Etaash-mathamsetty is this still an issue?

not anymore

meisme-dev · 2022-01-20T02:12:18Z

still happens for me

Etaash-mathamsetty · 2022-01-30T14:36:11Z

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 · 2022-05-30T19:46:22Z

None of the above did the trick for me.

meisme-dev · 2022-05-31T01:39:54Z

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 · 2022-05-31T02:15:33Z

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 · 2022-07-02T09:13:42Z

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 · 2022-08-22T11:00:43Z

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:

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.
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 · 2022-08-22T11:27:26Z

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

systemctl stop docker
systemctl restart iptables
ip link delete docker0
Restarted waydroid-container and started my waydroid session

Queatz · 2022-09-25T05:35:52Z

Running waydroid session stop and then launching it again does the trick for me. Hopefully the devs can get this resolved!

iinattr · 2022-09-29T11:48:50Z

I can ping a public IP in the waydroid shell but I still can't connect the internet in the full-ui of waydroid

tkkcc · 2022-11-10T10:13:27Z

jkcdarunday's solution works. But the key problem for me is iptables service is not started by waydroid.

Anikmoujegy · 2023-01-07T09:17:28Z

I have also have same issue on fedora I reinstalled fedora 5 times but facing the same issue

Geofferey · 2023-02-14T03:53:20Z

In my container I found that Android wasn't receiving an IP at all and the the Ethernet icon in status bar was missing. The culprit was lack of IPv6 due to kernel cmdline option to disable. I removed the option from my kernel cmdline and it started working after a reboot. Highly unlikely this will apply to many people but throwing it out there.

3laeddine-dh · 2023-02-28T08:27:07Z

@Geofferey can you show me the steps

Geofferey · 2023-02-28T09:51:56Z

@Geofferey can you show me the steps

What is the result of cat /proc/cmdline? Do you see something such as ipv6.disable=1? Are you receiving a link-local on your primary interface when running ifconfig like inet6 addr: fe80:: if you are getting that kind of address lack of IPv6 is not the issue.

guerlain242 · 2023-02-28T11:03:46Z

Follow this link to resolved it https://docs.waydro.id/debugging/networking-issues

guerlain242 · 2023-02-28T11:08:23Z

Networking Issues

Getting network info
Run the command below to get the information of various network interfaces.
ip addr show

Setting up your firewall

firewalld

firewall-cmd --zone=trusted --add-interface=waydroid0

UFW or GUFW

sudo ufw allow 53
sudo ufw allow 67
sudo ufw default allow FORWARD

notnotrachit · 2023-03-06T03:07:05Z

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

systemctl stop docker

systemctl restart iptables

ip link delete docker0

Restarted waydroid-container and started my waydroid session
sudo systemctl restart waydroid-container

@jkcdarunday Solution Worked for me
This works, but how can we make it permanent? or happen on every boot?

guerlain242 · 2023-03-12T10:21:42Z

Thank you, I got the solution on the internet ! Le lundi 6 mars 2023, Rachit Khurana ***@***.***> a écrit :

…

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 sudo systemctl restart waydroid-container @jkcdarunday <https://github.com/jkcdarunday> Solution Worked for me This works, but how can we make it permanent? or happen on every boot? — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6FUW4TF666LV26P2DUFNADW2VIGLANCNFSM5FV7R7CA> . You are receiving this because you commented.Message ID: ***@***.***>

-- MGGT-SERVICE

ghost · 2023-04-10T12:24:36Z

Follow this link to resolved it https://docs.waydro.id/debugging/networking-issues

$ firewall-cmd --zone=trusted --add-interface=waydroid0

Warning: ZONE_ALREADY_SET: 'waydroid0' already bound to 'trusted'

Fedora 37. No other related solutions on the page at the time of writing.

Installed Packages
Name         : waydroid
Version      : 1.4.0
Release      : 1.fc37
Architecture : noarch
Size         : 625 k
Source       : waydroid-1.4.0-1.fc37.src.rpm
Repository   : @System
From repo    : updates

NotPhantomX · 2023-04-15T20:30:30Z

Follow this link to resolved it docs.waydro.id/debugging/networking-issues

$ firewall-cmd --zone=trusted --add-interface=waydroid0

Warning: ZONE_ALREADY_SET: 'waydroid0' already bound to 'trusted'

Fedora 37. No other related solutions on the page at the time of writing.

Installed Packages
Name         : waydroid
Version      : 1.4.0
Release      : 1.fc37
Architecture : noarch
Size         : 625 k
Source       : waydroid-1.4.0-1.fc37.src.rpm
Repository   : @System
From repo    : updates

I managed to get it working by doing the following

sudo dnf install ufw
sudo ufw enable
sudo ufw allow 53
sudo ufw allow 67
sudo ufw default allow FORWARD

rustyx · 2023-04-24T21:34:17Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)
iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:

sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

RAFET-DILSIZ · 2023-05-29T09:37:31Z

My solution steps
1-) I opened terminal and I run nmtui command
2-)I choosed 2nd link enable a link
3-)I saw bridge link waydroid it is bottom in page I made it active

Mr-MyDooM · 2023-05-29T23:20:03Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Thanks
this worked for me on Ubuntu 22.04

blackinitial · 2023-06-01T07:05:01Z

my device using Ubuntu 22.04.2 LTS

i was add firewall with command on https://docs.waydro.id/debugging/networking-issues

➜ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
53                         ALLOW       Anywhere
67                         ALLOW       Anywhere
53 (v6)                    ALLOW       Anywhere (v6)
67 (v6)                    ALLOW       Anywhere (v6)

ip is show on ip addr show

➜ ip addr show
...
11: waydroid0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:16:3e:00:00:01 brd ff:ff:ff:ff:ff:ff
    inet 192.168.240.1/24 brd 192.168.240.255 scope global waydroid0
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fe00:1/64 scope link
       valid_lft forever preferred_lft forever
...

i was try

sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

but still cant connect internet.

try on terminal sudo waydroid shell i got connect: Network is unreachable

any step i miss? how to fix this?

webdevsuperfast · 2023-06-03T12:08:39Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Worked on Fedora 38

Grief · 2023-06-03T12:49:06Z

Thanks @webdevsuperfast, your solution helped me to get the network connection on the most recent KDE neon 5.27/kubuntu lunar

abuturabofficial · 2023-07-08T12:48:04Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Thanks, worked for Fedora38. They should update their official fix too.

pramodhrachuri · 2023-08-20T04:05:49Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Worked like a charm on Ubuntu 22.04.3

lgwacker · 2023-10-04T22:49:04Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Worked for me too! Thanks a lot @rustyx

NovoG93 · 2023-10-10T14:13:32Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Worked like a charm on Fedora 37!
Thanks a lot @rustyx

attarchi · 2023-10-22T01:08:13Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Thank you very much. It worked for me. Ubuntu 22.04.3

stsquad · 2023-10-31T11:20:13Z

I can't find why this issue was closed but the fix to waydroid-net.sh worked for me as well (Debian Bookworm with Docker) and given the number of other network related bugs (#105, #782, #656) makes me wonder if there should be a single tracking bug for these docker/nftables/iptables issues?

ipaqmaster · 2024-01-18T01:29:38Z

I experienced this myself today. While the interface gets created and an IP assigned to the android device, firewall rules do not get modified. I resolved this by manually adding firewall rules on my PC to allow the forwarding of traffic from the android device through my network. Plus a rule on my network interface to NAT the traffic from it as my PC's own LAN IP.

hostRoute=$(ip route show default | head | cut -d' ' -f5)
sudo iptables -I FORWARD -i waydroid0 -o ${hostRoute} -j ACCEPT
sudo iptables -I FORWARD -i ${hostRoute} -o waydroid0 -j ACCEPT
sudo iptables -t nat -A POSTROUTING -o ${hostRoute} -j MASQUERADE

For some installations it may also be necessary to enable forwarding: sudo sysctl -w net.ipv4.ip_forward=1 though I didn't need to, which makes me think the waydroid0 interface may already be taking care of some form of NAT - in which case it's possible the MASQUERADE rule is all that was needed.

comradedakota · 2024-01-22T02:07:39Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Thank you so much! This worked for me on Arch Linux. 👍

SX-9 · 2024-02-05T01:45:08Z

my solution was to turn off both tailscale vpn and cloudflare warp vpn and internet worked again

OS: Manjaro
Waydroid: GAPPS

xTrayambak · 2024-02-19T15:10:51Z

The following entries pop up when I run ip addr show:

7: waydroid0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether <address> brd ff:ff:ff:ff:ff:ff
    inet <address>/24 brd <address> scope global waydroid0
       valid_lft forever preferred_lft forever
    inet6 <address>/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
8: vethSH3eI7@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master waydroid0 state UP group default qlen 1000
    link/ether <address> brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 <address>/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever

Here's an error I spotted when running systemctl status waydroid-container.service

Feb 19 20:31:36 victus dnsmasq-dhcp[2272]: Error sending DHCP packet to <address>: Operation not permitted

I'm on Fedora 39 with the waydroid package that's provided by Fedora.

Owen-kasule · 2024-03-22T02:02:35Z

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

This has fixed my issue as well however I had to re-register my container's Google Services Framework Android ID at https://www.google.com/android/uncertified/ and I used this command to get it sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = 'android_id';"
inside the WayDroid shell.

s0u7a · 2024-04-05T12:56:03Z

I can't seem to use the internet on waydroid when connected to a VPN using Wireguard!

brunofin · 2024-04-18T09:30:27Z

For those still running into the Docker conflict, I managed to solve my issue by uninstalling Docker and moving to Podman. Podman supports docker container and docker-composer with no changes in your workflow whatsover, and it has an official nice looking GUI app in flathub (Podman Desktop) to help you manage it . I recommend it, and now Waydroid is working as expected.

alfandevt · 2024-05-19T10:25:33Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

Yooo, this solution worked for me!! Thank You!! (manjaro | xfce)

Th3Rom3 · 2024-05-21T09:40:48Z

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

+1
This worked for me running Waydroid on Fedora 40.

Rory-Lambert · 2024-06-06T09:41:19Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

This worked for me! Thanks! Should this issue not remain open until it's implemented in Waydroid? Or maybe its detailed in another issue? Would be a shame for this knowledge to live only on a closed issue thread that requires a bit of searching to arrive at!

ethanaobrien · 2024-06-18T04:25:38Z

Just wanted to leave a note, the docker issue is not, at all, an issue with waydroid.

After banging my head for hours over a not working virtual network in virt-manager, it lead back to docker. Restarting iptables (as @jkcdarunday mentioned) was the only working solution I managed to get working.

The issue I had, and this issue are the exact same. Appears to be connected, but no network going through, restarted iptables, both started working instantly.

I did try other mentioned solutions, none of which worked for me.

This is an issue that should be opened with docker, since its not happening just across waydroid. It happens seemingly across virtual networks in general when the docker iptables rules are present. Docker is a pain sometimes

I wrote this systemd service that resets iptables after docker starts up. It does not appear to break docker in any way, everything seems to work properly.

[Unit]
Description=Fix docker
After=docker.service
BindsTo=docker.service
ReloadPropagatedFrom=docker.service

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl restart iptables

[Install]
WantedBy=multi-user.target

TLDR: docker iptables rules break other virtual networks

poptart-linux-person · 2024-07-18T05:48:27Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:
* `nftables` doesn't work in combination with `iptables` rules (which I have on due to Docker)

* `iptables-legacy` doesn't work at all
So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

does not work for me maybe because I'm on debian

wyktron · 2024-07-22T07:55:46Z

Waydroid has no internet when Surfshark VPN is on, Debian 12

Issue:
When using Waydroid on Debian 12 with Surfshark VPN enabled, Waydroid was unable to access the internet. Checking the network setup revealed that the Waydroid interface (waydroid0) and Surfshark VPN interface (surfshark_wg) had their configurations correct; however, the traffic from Waydroid was not routed properly through the VPN.

Solution:
The issue was fixed by adding custom routing rules to ensure traffic from Waydroid (192.168.240.0/24) was routed through the Surfshark VPN interface (10.14.0.2).

Steps Taken:

Check the Waydroid Network Interface:
```
ip a show waydroid0
```
Ensure that the waydroid0 interface is up and has the correct IP configuration. This means:
- The interface is in the "UP" state, indicating it is active.
- It has an IPv4 address assigned (e.g., 192.168.240.1/24).
- It has an appropriate IPv6 address (e.g., fe80::216:3eff:fe00:1/64, usually generated automatically for local link).
Add Custom Routing Rules:
```
sudo ip route add default via 192.168.240.1 dev waydroid0 table waydroid
sudo ip rule add from 192.168.240.0/24 table waydroid
sudo ip route add 192.168.240.0/24 dev waydroid0 table waydroid
sudo ip rule add from all to 192.168.240.0/24 table waydroid
sudo ip route flush cache
```
These commands create a custom routing table named waydroid and ensure that traffic from the 192.168.240.0/24 subnet is routed through:
- The waydroid0 interface.
- The Surfshark VPN interface, ensuring all traffic is encrypted.
This setup ensures that the Waydroid network has proper routes to access the internet through the Surfshark VPN.

After applying these routing rules, Waydroid could access the internet through the Surfshark VPN successfully.

gcgbarbosa · 2024-08-04T15:45:00Z

No worky in Ubuntu 22.04.

The script /usr/lib/waydroid/data/scripts/waydroid-net.sh prefers nft, iptables-legacy, iptables, in that order.

There are 2 problems with that logic:

nftables doesn't work in combination with iptables rules (which I have on due to Docker)

iptables-legacy doesn't work at all

So the script has no chance of ever working.

With the following patch that disables nft and iptables-legacy I was able to get Internet working:
sudo sed -i~ -E 's/=.\$\(command -v (nft|ip6?tables-legacy).*/=/g' \
     /usr/lib/waydroid/data/scripts/waydroid-net.sh

you're a genius

itscooldani · 2024-08-22T04:38:02Z

In my container I found that Android wasn't receiving an IP at all and the the Ethernet icon in status bar was missing. The culprit was lack of IPv6 due to kernel cmdline option to disable. I removed the option from my kernel cmdline and it started working after a reboot. Highly unlikely this will apply to many people but throwing it out there.

Holy shit this was the exact weird random issue I was running into and it fixed it for me. Thanks!

Etaash-mathamsetty closed this as completed Dec 31, 2021

mityax mentioned this issue Mar 18, 2023

Network not working on fedora37 (Using surface-linux kernel) #809

Closed

stsquad mentioned this issue Oct 31, 2023

Remove network changes made by waydroid #790

Open

s0u7a mentioned this issue Mar 19, 2024

Fix Networking issue #1330

Open

kodingkoning mentioned this issue Apr 2, 2024

[BUG] No Network Connection #1346

Open

RokeJulianLockhart mentioned this issue Aug 26, 2024

[BUG] No Network Connection #1349

Closed

No internet in waydroid #143

No internet in waydroid #143

Comments

Etaash-mathamsetty commented Oct 10, 2021

vega-d commented Oct 17, 2021

Vormalzalek commented Oct 22, 2021

whyc3 commented Nov 12, 2021 • edited Loading

Aman9das commented Nov 20, 2021

Quackdoc commented Dec 30, 2021

Etaash-mathamsetty commented Dec 31, 2021 • edited Loading

meisme-dev commented Jan 20, 2022

Etaash-mathamsetty commented Jan 30, 2022 • edited Loading

azul commented May 30, 2022

meisme-dev commented May 31, 2022

Etaash-mathamsetty commented May 31, 2022 • edited Loading

DFF-fred commented Jul 2, 2022

jkcdarunday commented Aug 22, 2022

jkcdarunday commented Aug 22, 2022

Queatz commented Sep 25, 2022

iinattr commented Sep 29, 2022

tkkcc commented Nov 10, 2022 • edited Loading

Anikmoujegy commented Jan 7, 2023

Geofferey commented Feb 14, 2023

3laeddine-dh commented Feb 28, 2023

Geofferey commented Feb 28, 2023 • edited Loading

guerlain242 commented Feb 28, 2023

guerlain242 commented Feb 28, 2023

notnotrachit commented Mar 6, 2023 • edited Loading

guerlain242 commented Mar 12, 2023 via email

ghost commented Apr 10, 2023 • edited by ghost Loading

NotPhantomX commented Apr 15, 2023

rustyx commented Apr 24, 2023

RAFET-DILSIZ commented May 29, 2023

Mr-MyDooM commented May 29, 2023

blackinitial commented Jun 1, 2023

webdevsuperfast commented Jun 3, 2023

Grief commented Jun 3, 2023

abuturabofficial commented Jul 8, 2023

pramodhrachuri commented Aug 20, 2023

lgwacker commented Oct 4, 2023

NovoG93 commented Oct 10, 2023

attarchi commented Oct 22, 2023

stsquad commented Oct 31, 2023

ipaqmaster commented Jan 18, 2024

comradedakota commented Jan 22, 2024

SX-9 commented Feb 5, 2024

xTrayambak commented Feb 19, 2024 • edited Loading

Owen-kasule commented Mar 22, 2024

s0u7a commented Apr 5, 2024

brunofin commented Apr 18, 2024 • edited Loading

alfandevt commented May 19, 2024

Th3Rom3 commented May 21, 2024

Rory-Lambert commented Jun 6, 2024

ethanaobrien commented Jun 18, 2024

poptart-linux-person commented Jul 18, 2024 • edited Loading

wyktron commented Jul 22, 2024 • edited Loading

gcgbarbosa commented Aug 4, 2024

itscooldani commented Aug 22, 2024

whyc3 commented Nov 12, 2021 •

edited

Loading

Etaash-mathamsetty commented Dec 31, 2021 •

edited

Loading

Etaash-mathamsetty commented Jan 30, 2022 •

edited

Loading

Etaash-mathamsetty commented May 31, 2022 •

edited

Loading

tkkcc commented Nov 10, 2022 •

edited

Loading

Geofferey commented Feb 28, 2023 •

edited

Loading

notnotrachit commented Mar 6, 2023 •

edited

Loading

ghost commented Apr 10, 2023 •

edited by ghost

Loading

xTrayambak commented Feb 19, 2024 •

edited

Loading

brunofin commented Apr 18, 2024 •

edited

Loading

poptart-linux-person commented Jul 18, 2024 •

edited

Loading

wyktron commented Jul 22, 2024 •

edited

Loading