-
-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No internet in waydroid #143
Comments
Just updated waydroid from sep 11 build. Internet connection for container doesn't work now, would like to know what went wrong too. |
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? |
In my case using Fedora 35 with XanMod Kernel, I had the same issue, and all I did was restart the waydroid-container service : |
Yes |
@Etaash-mathamsetty is this still an issue? |
not anymore |
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 |
None of the above did the trick for me. |
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) |
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? |
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:
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. |
Finally got it to work, looks like there's a conflict with docker's iptables rules.
|
Running |
I can ping a public IP in the waydroid shell but I still can't connect the internet in the full-ui of waydroid |
jkcdarunday's solution works. But the key problem for me is |
I have also have same issue on fedora I reinstalled fedora 5 times but facing the same issue |
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. |
@Geofferey can you show me the steps |
What is the result of |
Follow this link to resolved it https://docs.waydro.id/debugging/networking-issues |
Networking Issues Getting network info Setting up your firewall
firewall-cmd --zone=trusted --add-interface=waydroid0
sudo ufw allow 53 |
@jkcdarunday Solution Worked for me |
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
|
Fedora 37. No other related solutions on the page at the time of writing.
|
I managed to get it working by doing the following
|
No worky in Ubuntu 22.04. The script There are 2 problems with that logic:
So the script has no chance of ever working. With the following patch that disables
|
My solution steps |
Thanks |
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
...
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
but still cant connect internet. try on terminal any step i miss? how to fix this? |
Worked on Fedora 38 |
Thanks @webdevsuperfast, your solution helped me to get the network connection on the most recent KDE neon 5.27/kubuntu lunar |
Thanks, worked for Fedora38. They should update their official fix too. |
Worked like a charm on Ubuntu 22.04.3 |
Worked for me too! Thanks a lot @rustyx |
Worked like a charm on Fedora 37! |
Thank you very much. It worked for me. Ubuntu 22.04.3 |
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.
For some installations it may also be necessary to enable forwarding: |
Thank you so much! This worked for me on Arch Linux. 👍 |
my solution was to turn off both tailscale vpn and cloudflare warp vpn and internet worked again OS: Manjaro |
The following entries pop up when I run
Here's an error I spotted when running
I'm on Fedora 39 with the |
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';" |
I can't seem to use the internet on waydroid when connected to a VPN using Wireguard! |
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. |
Yooo, this solution worked for me!! Thank You!! (manjaro | xfce) |
+1 |
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! |
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.
TLDR: docker iptables rules break other virtual networks |
does not work for me maybe because I'm on debian |
Waydroid has no internet when Surfshark VPN is on, Debian 12 Issue: Solution: Steps Taken:
After applying these routing rules, Waydroid could access the internet through the Surfshark VPN successfully. |
you're a genius |
Holy shit this was the exact weird random issue I was running into and it fixed it for me. Thanks! |
I don't have any internet inside waydroid, i feel like I missed some configuration step, can anyone help?
The text was updated successfully, but these errors were encountered: