Skip to content
Snippets Groups Projects
New look: Off

Investigate why there is no networking with Anbox on Pinephone.

    • Closed Imported Issue created by Administrator @root

    The interface is created properly. Adding it manually (or using the deprecated anbox-networkmanager package) doesn't help.

    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator added category::device type::bug + 1 deleted label · Imported

      added category::device type::bug + 1 deleted label

    • Administrator mentioned in issue #495 (closed) · Imported

      mentioned in issue #495 (closed)

      By Antoine Fontaine on 2020-03-18T08:47:07

      • Administrator
        Administrator @root · Imported
        Author Owner

        I found a workaround! 🥳

        1. ping 8.8.8.8 (aww it didn't work)
        2. Access the Anbox shell from the special script (/usr/share/anbox/anbox-shell.sh), not from adb shell. That way you can get root.
        3. Switch to root su
        4. ip route add default via 192.168.250.1
        5. ping 8.8.8.8 (wow it works now!)

        I'm not sure exactly why this is necessary but... Maybe tweak the rootfs overlay to fix it?

        By Nikhil Jha on 2020-04-05T16:47:07

        Edited by Ghost User
      • Administrator
        Administrator @root · Imported
        Author Owner

        Hi. I've tried included the fix in the image, but I appear to have hardware issues unrelated to Anbox, so I can't test it. Could you give a shot to the last commit here?

        https://gitlab.com/afontain/pmaports/-/commits/anbox-fix-pinephone-network

        By Antoine Fontaine on 2020-04-05T16:47:27

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        Does starting the container manager manually with --container-network-gateway=192.168.250.1 works for you? (There is also --container-network-address and --container-network-dns-servers)

        rc-service anbox-container-manager stop
sudo anbox container-manager --daemon --privileged --data-path=/var/lib/anbox  --android-image=/usr/share/anbox/android.img --container-network-gateway=192.168.250.1

        By Antoine Fontaine on 2020-04-08T22:43:25

      • Administrator
        Administrator @root · Imported
        Author Owner

        I'll try to test this soon; I'm currently fixing some Fedora-related things before getting back to Anbox.

        By Nikhil Jha on 2020-04-08T23:00:40

      • Administrator
        Administrator @root · Imported
        Author Owner

        I tried the modifying the init script as above; it did not work.

        By Antoine Fontaine on 2020-04-24T13:49:46

      • Administrator
        Administrator @root · Imported
        Author Owner

        to try: --container-network-gateway=192.168.250.1 --container-network-address=192.168.250.2

        By Antoine Fontaine on 2020-08-17T08:45:33

      • Please register or sign in to reply
    • Administrator changed milestone to %Anbox · Imported

      changed milestone to %Anbox

      By Oliver Smith on 2020-03-22T02:11:04

    • Administrator mentioned in issue #508 (closed) · Imported

      mentioned in issue #508 (closed)

      By Nikhil Jha on 2020-03-22T02:47:47

    • Administrator changed the description · Imported

      changed the description

      By Antoine Fontaine on 2020-04-08T22:44:32

    • Administrator marked this issue as related to #508 (closed) · Imported

      marked this issue as related to #508 (closed)

      By Antoine Fontaine on 2020-04-26T17:06:19

    • Administrator mentioned in merge request !1222 (merged) · Imported

      mentioned in merge request !1222 (merged)

      By Antoine Fontaine on 2020-05-11T17:05:24

    • Administrator mentioned in merge request !1230 (merged) · Imported

      mentioned in merge request !1230 (merged)

      By Antoine Fontaine on 2020-05-12T15:51:05

    • Administrator assigned to @afontain · Imported

      assigned to @afontain

      By Antoine Fontaine on 2020-05-12T15:53:03

    • Administrator closed via merge request !1230 (merged) · Imported

      closed via merge request !1230 (merged)

      By Alexey Min on 2020-05-13T13:09:41

    • Administrator mentioned in commit d4a99bc4 · Imported

      mentioned in commit d4a99bc4

      By Antoine Fontaine on 2020-05-17T12:41:10

    • Administrator mentioned in merge request !1337 (closed) · Imported

      mentioned in merge request !1337 (closed)

      By Antoine Fontaine on 2020-06-18T11:14:18

    • Administrator mentioned in issue #648 (closed) · Imported

      mentioned in issue #648 (closed)

      By Antoine Fontaine on 2020-06-26T20:20:46

    • Administrator reopened · Imported

      reopened

      • Administrator
        Administrator @root · Imported
        Author Owner

        Here's the new state-of-the-art workaround:

        sudo apk add lxc
sudo /usr/share/anbox/anbox-shell.sh
ip route add default dev eth0 via 192.168.250.1
ip rule add pref 32766 table main
ip rule add pref 32767 table local

        Reopening the issue as the problem isn't quite solved.

        By Antoine Fontaine on 2020-09-03T18:56:12

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        @afontain When I try and do the ip rule add commands I get the error RTNETLINK answers: Operation not supported on transport endpoint. Do you know why this may be happening?

        By Kay Thomas on 2020-09-03T18:56:12

      • Administrator
        Administrator @root · Imported
        Author Owner

        I have the same problem. It looks like it's a kernel config issue.

        According to https://superuser.com/questions/232807/iproute2-not-functioning-rtnetlink-answers-operation-not-supported we need the following in the Kconfig:

        CONFIG_NETFILTER_NETLINK=y 
CONFIG_NETFILTER_NETLINK_QUEUE=y 
CONFIG_NETFILTER_NETLINK_LOG=y 
CONFIG_NF_CT_NETLINK=y 
CONFIG_SCSI_NETLINK=y 
CONFIG_IP_ADVANCED_ROUTER=y 
CONFIG_NET_SCH_INGRESS=y 
CONFIG_NET_SCHED=y 
CONFIG_IP_MULTIPLE_TABLES=y 
CONFIG_NETFILTER_XT_TARGET_MARK=y

        For the PinePhone at least that doesn't seem to be the case: https://gitlab.postmarketos.org/postmarketos/pmaports/-/blob/master/main/linux-postmarketos-allwinner/config-postmarketos-allwinner.aarch64#L917

        By Alistair Francis on 2020-09-10T05:11:53

      • Administrator
        Administrator @root · Imported
        Author Owner

        I have made some of the config changes and I can now run all of the commands. I can ping IP addresses and resolve domain names, but F Droid still doesn't get a connection. I'm enabling all of the configs and I'll see if that helps.

        If anyone has an idea of logs to check that would be great. I'm not really sure how to debug F Droid not getting a connection.

        By Alistair Francis on 2020-09-12T06:05:52

      • Administrator
        Administrator @root · Imported
        Author Owner

        This might be a bit late and somebody might have already figured it out. I resolved my F Droid issue by reinstalling it.

        wget https://f-droid.org/F-Droid.apk
adb shell cmd package uninstall -k --user 0 org.fdroid.fdroid
adb install -r --user 0 F-Droid.apk

        By Josue Martinez on 2020-11-28T15:55:28

      • Administrator
        Administrator @root · Imported
        Author Owner

        On PMOS-Plasma, this workaround didn't work for me. When I issued ip rule add pref 32766 table main I got RTNETLINK answers: Address family not supported by protocol

        I also tried to clear f-droid cache and then remove/install, but none of them worked either.

        I have checked the kernel config on the device and got:

        • zcat /proc/config.gz | grep CONFIG_NETFILTER_NETLINK -> CONFIG_NETFILTER_NETLINK=m
        • zcat /proc/config.gz | grep CONFIG_NETFILTER_NETLINK_QUEUE -> # CONFIG_NETFILTER_NETLINK_QUEUE is not set
        • zcat /proc/config.gz | grep CONFIG_NETFILTER_NETLINK_LOG -> # CONFIG_NETFILTER_NETLINK_LOG is not set
        • zcat /proc/config.gz | grep CONFIG_NF_CT_NETLINK -> # CONFIG_NF_CT_NETLINK is not set
        • zcat /proc/config.gz | grep CONFIG_SCSI_NETLINK -> nothing returned
        • zcat /proc/config.gz | grep CONFIG_IP_ADVANCED_ROUTER -> # CONFIG_IP_ADVANCED_ROUTER is not set
        • zcat /proc/config.gz | grep CONFIG_NET_SCH_INGRESS -> nothing returned
        • zcat /proc/config.gz | grep CONFIG_NET_SCHED -> # CONFIG_NET_SCHED is not set
        • zcat /proc/config.gz | grep CONFIG_IP_MULTIPLE_TABLES -> nothing returned
        • zcat /proc/config.gz | grep CONFIG_NETFILTER_XT_TARGET_MARK -> # CONFIG_NETFILTER_XT_TARGET_MARK is not set

        By edp17 on 2020-12-04T09:04:07

        Edited by Administrator
      • Please register or sign in to reply
    • Administrator
      Administrator @root · Imported
      Author Owner

      The easiest but probably only a temp solution. That you will have to repeat a lot, seems to me is just cleaning the app data and cache in the android settings.

      By Nils Idc on 2020-09-21T16:17:23

    • Administrator
      Administrator @root · Imported
      Author Owner

      I think it was a mistake to close #508 (closed) @afontain given such issue seems to be crossplatform, not so common but also happends in android based systems not just anbox. So all indicates for it to be a upstream bug, by that I mean the f-droid client codebase.

      By . |3vast.org on 2020-11-01T22:05:00

    • Administrator
      Administrator @root · Imported
      Author Owner

      @Nils: have you done that successfully for an app that wasn't FDroid?

      By Antoine Fontaine on 2020-12-04T10:32:08

    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    • Loading
    Please register or sign in to reply