In a wayland session, waydroid works perfectly…except it can’t access the network…ArchWiki says there can be network problems if a firewall blocks it but even systemctl stop firewalld doesn’t work…has anybody else managed to make it work?
1 Like
But on the page you linked is the following section:
For firewalld, you can use those commands:
DNS:
# firewall-cmd --zone=trusted --add-port=67/udp
# firewall-cmd --zone=trusted --add-port=53/udp
Packet forwarding:
# firewall-cmd --zone=trusted --add-forward
Note: We assume that interface waydroid0 created by waydroid should be in the firewalld zone trusted automatically. If not so, please adjust those commands above or move interface waydroid0 to trusted. You may also need run
# firewall-cmd --runtime-to-permanent
to make your changes exist after a restart.
Does that not accomplish what you need?
1 Like
Yeah sorry I later figured out firewall-cmd controlled firewalld…and firewalld doesn’t seem to be the roadblock as it doesn’t work even after systemctl stop firewalld
I edited the post