From: notramo <notramo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Waydroid shipped broken
Date: Wed, 04 Jan 2023 02:15:30 +0100 [thread overview]
Message-ID: <20230104011530.TkIK8WVjTFdkUNvyjm6yFykDsyeK70ENjtljoq-OP3E@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: 2053 bytes --]
New comment by notramo on void-packages repository
https://github.com/void-linux/void-packages/issues/41363#issuecomment-1370385454
Comment:
I tried flushing nftables, no success. Also tried it with Docker stopped.
`ip route` inside the container gives no output.
`ip addr show` output inside the container:
```
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0@if71: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:16:3e:f9:d3:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::a758:6767:86f8:7586/64 scope link stable-privacy
valid_lft forever preferred_lft forever
```
It seems it got an IPv6 address only, but the host system has only an IPv4 gateway.
`ip addr show` on the host system shows these 2 interfaces that are created by Waydroid:
```70: 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
inet 169.254.106.76/16 brd 169.254.255.255 scope global noprefixroute waydroid0
valid_lft forever preferred_lft forever
inet6 fe80::ba14:a2bc:d8:3e6e/64 scope link
valid_lft forever preferred_lft forever
71: vethvPyc2L@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master waydroid0 state UP group default qlen 1000
link/ether fe:98:50:59:58:6a brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 169.254.59.163/16 brd 169.254.255.255 scope global noprefixroute vethvPyc2L
valid_lft forever preferred_lft forever
inet6 fe80::6625:f411:d258:7207/64 scope link
valid_lft forever preferred_lft forever
```
next prev parent reply other threads:[~2023-01-04 1:15 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 [this message]
2023-01-04 1:18 ` notramo
2023-01-04 2:12 ` JamiKettunen
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=20230104011530.TkIK8WVjTFdkUNvyjm6yFykDsyeK70ENjtljoq-OP3E@z \
--to=notramo@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).