From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Waydroid shipped broken
Date: Wed, 04 Jan 2023 03:12:33 +0100 [thread overview]
Message-ID: <20230104021233.KJJYs0WSRzaPOVF0VGpcytaDW4NV-tf1IYj80bGrg2k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41363@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/issues/41363#issuecomment-1370411878
Comment:
You mentioned you had `dnscrypt-proxy` running on port 53 and I found https://github.com/waydroid/waydroid/issues/117#issuecomment-950303832 as well as https://github.com/waydroid/waydroid/issues/588 which could be relevant.
Since you said you had docker running, if restarting `waydroid-container` service didn't help solve networking issue you maybe `reboot`ing would? I previously filed https://github.com/waydroid/waydroid/issues/509 for the nftables + docker setup causing networking issues.
If you end up getting it working and have ideas on implementing the Waydroid network setup better do please contribute or file an issue upstream!
next prev parent reply other threads:[~2023-01-04 2:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 16:27 [ISSUE] " notramo
2022-12-30 16:43 ` paper42
2022-12-31 19:08 ` JamiKettunen
2023-01-03 21:33 ` notramo
2023-01-03 21:41 ` notramo
2023-01-03 21:55 ` notramo
2023-01-03 21:57 ` notramo
2023-01-03 21:58 ` notramo
2023-01-04 0:43 ` JamiKettunen
2023-01-04 0:47 ` JamiKettunen
2023-01-04 1:15 ` notramo
2023-01-04 1:18 ` notramo
2023-01-04 2:12 ` JamiKettunen [this message]
2023-01-16 21:36 ` CameronNemo
2023-01-16 22:07 ` JamiKettunen
2023-01-17 1:33 ` CameronNemo
2023-01-17 2:20 ` CameronNemo
2023-04-09 4:03 ` HadetTheUndying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230104021233.KJJYs0WSRzaPOVF0VGpcytaDW4NV-tf1IYj80bGrg2k@z \
--to=jamikettunen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).