I think I can live with executing OpenMPI on Termux. As it is, fixing this
issue will not be a priority.

On Fri, 26 Feb 2021, 13:09 Gilles Gouaillardet via users, <
users@lists.open-mpi.org> wrote:

> yes, you need to (re)build Open MPI from source in order to try this trick.
>
> On 2/26/2021 3:55 PM, LINUS FERNANDES via users wrote:
> > No change.
> > What do you mean by running configure?
> > Are you expecting me to build OpenMPI from source?
> >
> > On Fri, 26 Feb 2021, 11:16 Gilles Gouaillardet via users,
> > <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote:
> >
> >     Before running configure, try to
> >     export ac_cv_type_struct_ifreq=no
> >     and see how it goes
> >
> >     On Fri, Feb 26, 2021 at 8:18 AM LINUS FERNANDES via users
> >     <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote:
> >     >
> >     > https://github.com/SDRausty/termux-archlinux/issues/78
> >     <https://github.com/SDRausty/termux-archlinux/issues/78>
> >     > On Fri, 26 Feb 2021, 04:28 LINUS FERNANDES,
> >     <linus.fernan...@gmail.com <mailto:linus.fernan...@gmail.com>>
> wrote:
> >     >>
> >     >> ifconfig on Termux
> >     >>
> >     >> dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
> >     >>         inet6 fe80::488e:42ff:fe43:b843  prefixlen 64  scopeid
> >     0x20<link>
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 0 (UNSPEC)
> >     >>         RX packets 0  bytes 0 (0.0 B)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 3  bytes 210 (210.0 B)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
> >     >>         inet 127.0.0.1  netmask 255.0.0.0
> >     >>         inet6 ::1  prefixlen 128  scopeid 0x10<host>
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 0 (UNSPEC)
> >     >>         RX packets 12  bytes 1285 (1.2 KiB)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 12  bytes 1285 (1.2 KiB)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >> p2p0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 1000  (UNSPEC)
> >     >>         RX packets 0  bytes 0 (0.0 B)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 0  bytes 0 (0.0 B)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >> rmnet_data0: flags=65<UP,RUNNING>  mtu 1500
> >     >>         inet 10.132.157.153  netmask 255.255.255.252
> >     >>         inet6 fe80::fbbc:50e0:b07d:6380  prefixlen 64  scopeid
> >     0x20<link>
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 1000  (UNSPEC)
> >     >>         RX packets 3041  bytes 1828676 (1.7 MiB)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 3079  bytes 794069 (775.4 KiB)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >> rmnet_data7: flags=65<UP,RUNNING>  mtu 2000
> >     >>         inet6 fe80::e516:d4c5:e5f7:e54e  prefixlen 64  scopeid
> >     0x20<link>
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 1000  (UNSPEC)
> >     >>         RX packets 8  bytes 620 (620.0 B)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 10  bytes 752 (752.0 B)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >> rmnet_ipa0: flags=65<UP,RUNNING>  mtu 2000
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 1000  (UNSPEC)
> >     >>         RX packets 1926  bytes 1865884 (1.7 MiB)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 3089  bytes 794821 (776.1 KiB)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >> wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> >     >>         unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     txqueuelen 1000  (UNSPEC)
> >     >>         RX packets 0  bytes 0 (0.0 B)
> >     >>         RX errors 0  dropped 0  overruns 0  frame 0
> >     >>         TX packets 0  bytes 0 (0.0 B)
> >     >>         TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0
> >     >>
> >     >>
> >     >> ipaddr on Termux:
> >     >>
> >     >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
> >     UNKNOWN group default
> >     >>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     >>     inet 127.0.0.1/8 <http://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: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue
> >     state UNKNOWN group default
> >     >>     link/ether 4a:8e:42:43:b8:43 brd ff:ff:ff:ff:ff:ff
> >     >>     inet6 fe80::488e:42ff:fe43:b843/64 scope link
> >     >>        valid_lft forever preferred_lft forever
> >     >> 3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group
> default
> >     >>     link/sit 0.0.0.0 brd 0.0.0.0
> >     >> 4: rmnet_ipa0: <UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state
> >     UNKNOWN group default qlen 1000
> >     >>     link/[530]
> >     >> 5: rmnet_data0: <UP,LOWER_UP> mtu 1500 qdisc htb state UNKNOWN
> >     group default qlen 1000
> >     >>     link/[530]
> >     >>     inet 10.132.157.153/30 <http://10.132.157.153/30> scope
> >     global rmnet_data0
> >     >>        valid_lft forever preferred_lft forever
> >     >>     inet6 fe80::fbbc:50e0:b07d:6380/64 scope link
> >     >>        valid_lft forever preferred_lft forever
> >     >> 6: rmnet_data1: <> mtu 1500 qdisc noop state DOWN group default
> >     qlen 1000
> >     >>     link/[530]
> >     >> 7: rmnet_data2: <> mtu 1500 qdisc noop state DOWN group default
> >     qlen 1000
> >     >>     link/[530]
> >     >> 8: rmnet_data3: <> mtu 1500 qdisc noop state DOWN group default
> >     qlen 1000
> >     >>     link/[530]
> >     >> 9: rmnet_data4: <> mtu 1500 qdisc noop state DOWN group default
> >     qlen 1000
> >     >>     link/[530]
> >     >> 10: rmnet_data5: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 11: rmnet_data6: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 12: rmnet_data7: <UP,LOWER_UP> mtu 2000 qdisc htb state UNKNOWN
> >     group default qlen 1000
> >     >>     link/[530]
> >     >>     inet6 fe80::e516:d4c5:e5f7:e54e/64 scope link
> >     >>        valid_lft forever preferred_lft forever
> >     >> 13: r_rmnet_data0: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 14: r_rmnet_data1: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 15: r_rmnet_data2: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 16: r_rmnet_data3: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 17: r_rmnet_data4: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 18: r_rmnet_data5: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 19: r_rmnet_data6: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 20: r_rmnet_data7: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 21: r_rmnet_data8: <> mtu 1500 qdisc noop state DOWN group
> >     default qlen 1000
> >     >>     link/[530]
> >     >> 22: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> >     mq state DOWN group default qlen 1000
> >     >>     link/ether 04:d1:3a:07:70:4b brd ff:ff:ff:ff:ff:ff
> >     >> 23: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
> >     state DOWN group default qlen 1000
> >     >>     link/ether 06:d1:3a:07:70:4b brd ff:ff:ff:ff:ff:ff
> >     >>
> >     >>
> >     >>
> >     >> The above is the output of ifconfig and ip addr on Termux.
> >     OpenMPI works as expected on a single node, which is what I desire.
> >     >>
> >     >> I'm sure I can get OpenMPI to work on a PC or laptop running
> >     Windows or Linux.
> >     >>
> >     >> That's not my question, however.
> >     >>
> >     >>
> >     >> On Thu, 25 Feb 2021, 23:49 Jeff Squyres (jsquyres),
> >     <jsquy...@cisco.com <mailto:jsquy...@cisco.com>> wrote:
> >     >>>
> >     >>> You asked several questions:
> >     >>>
> >     >>> > But I'm able to get Apache working on a different port 8080.
> >     Is that useful?
> >     >>>
> >     >>> That's fine, but Apache has different requirements than Open MPI.
> >     >>>
> >     >>> > Do you think executing mpirun as a normal user will work?
> >     >>>
> >     >>> If it didn't work as root, it most likely won't work as a
> >     normal user.
> >     >>>
> >     >>> > Yes, it's self-learning.
> >     >>> > I have no applications to run.
> >     >>>
> >     >>> Do you have any other MacOS / Linux environment in which to
> >     run Open MPI?  That might end up being simpler.
> >     >>>
> >     >>> > I'd imagine the builders of Arch Linux on Termux would want
> >     to know why OpenMPI is not functioning as expected.
> >     >>>
> >     >>> Possibly.  Open MPI needs the MAC address of Linux interfaces;
> >     that doesn't seem to be working in Arch Linux on Termux.
> >     >>>
> >     >>>
> >     >>>
> >     >>> On Feb 25, 2021, at 12:32 PM, LINUS FERNANDES
> >     <linus.fernan...@gmail.com <mailto:linus.fernan...@gmail.com>>
> wrote:
> >     >>>
> >     >>> I'd imagine the builders of Arch Linux on Termux would want to
> >     know why OpenMPI is not functioning as expected.
> >     >>>
> >     >>> On Thu, 25 Feb 2021, 20:17 Jeff Squyres (jsquyres),
> >     <jsquy...@cisco.com <mailto:jsquy...@cisco.com>> wrote:
> >     >>>>
> >     >>>> I don't know how many people on this list will be familiar
> >     with Termux or Arch Linux.  From a quick Google, it looks like
> >     Termux is an Android emulator (that runs on Android?  That doesn't
> >     make sense to me, but I'm wholly unfamiliar with that ecosystem,
> >     so I don't have the background / grok the context) and provides
> >     some kind of Linux environment.  And on top of that, you're
> >     installing Arch Linux.  Is that correct?
> >     >>>>
> >     >>>> If that's anywhere close to correct, it sounds like there
> >     could be multiple layers of virtualization there, and that could
> >     lead to wonkiness in the emulation of the IP stack.
> >     >>>>
> >     >>>> I do note that the only interface it looks like Open MPI
> >     could use is rmnet_data0, but that's in an UNKNOWN state:
> >     >>>>
> >     >>>> 5: rmnet_data0: <UP,LOWER_UP> mtu 1500 qdisc htb state
> >     UNKNOWN group default qlen 1000
> >     >>>>     link/[530]
> >     >>>>     inet 10.140.58.138/30 <http://10.140.58.138/30> scope
> >     global rmnet_data0
> >     >>>>        valid_lft forever preferred_lft forever
> >     >>>>     inet6 fe80::93a5:ad99:4660:adc4/64 scope link
> >     >>>>        valid_lft forever preferred_lft forever
> >     >>>>
> >     >>>> Errno==13 is EACCESS, which generically translates to
> >     "permission denied".  Since you're running as root, this suggests
> >     that something outside of your local environment (e.g., outside of
> >     that immediate layer of virtualization) is preventing Open MPI
> >     from making that ioctl(SIOCGIFHWADDR) call (all that call is
> >     trying to do is discover the MAC address of that interface).
> >     >>>>
> >     >>>> Indeed, it looks like rmnet_data0 somehow doesn't have a MAC
> >     address...?
> >     >>>>
> >     >>>> rmnet_data0: flags=65<UP,RUNNING> mtu 1500
> >     >>>>         inet 10.140.58.138 netmask 255.255.255.252
> >     >>>>         inet6 fe80::93a5:ad99:4660:adc4 prefixlen 64 scopeid
> >     0x20<link>
> >     >>>>         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000
> >     (UNSPEC)
> >     >>>>         RX packets 416796 bytes 376287723 (358.8 MiB)
> >     >>>>         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>         TX packets 318293 bytes 69933666 (66.6 MiB)
> >     >>>>         TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >     >>>>
> >     >>>> That's... weird.  I don't know the details of this network
> >     stack; it's somewhat outside the bounds of "normal" IP-based
> >     networking if there's no MAC address.  As such, it doesn't
> >     surprise me that -- given that one of Open MPI's core assumptions
> >     fails -- Open MPI fails / refuses to run.
> >     >>>>
> >     >>>> I don't know if anyone has tried to run Open MPI in such a
> >     virtualized environment before.
> >     >>>>
> >     >>>>
> >     >>>>
> >     >>>>
> >     >>>> On Feb 25, 2021, at 6:04 AM, LINUS FERNANDES via users
> >     <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote:
> >     >>>>
> >     >>>> So the OpenMPI version on Arch Linux can't be made operational?
> >     >>>>
> >     >>>> On Thu, 25 Feb 2021, 15:43 LINUS FERNANDES,
> >     <linus.fernan...@gmail.com <mailto:linus.fernan...@gmail.com>>
> wrote:
> >     >>>>>
> >     >>>>> Nope. None of the commands exist. So no, I'd say.
> >     >>>>>
> >     >>>>> On Thu, 25 Feb 2021, 15:11 Gilles Gouaillardet via users,
> >     <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote:
> >     >>>>>>
> >     >>>>>>
> >
> https://www.letmegooglethat.com/?q=how+to+check+if+selinux+is+enabled&l=1
> >     <
> https://www.letmegooglethat.com/?q=how+to+check+if+selinux+is+enabled&l=1>
> >     >>>>>>
> >     >>>>>> On Thu, Feb 25, 2021 at 6:15 PM LINUS FERNANDES via users
> >     >>>>>> <users@lists.open-mpi.org
> >     <mailto:users@lists.open-mpi.org>> wrote:
> >     >>>>>> >
> >     >>>>>> > How do I know that? I'm not a Linux expert. I simply want
> >     to get OpenMPI running on Arch Linux so that I can test out their
> >     Java wrappers which I obviously can't on Termux since it doesn't
> >     support OpenJDK.
> >     >>>>>> >
> >     >>>>>> > On Thu, 25 Feb 2021, 13:37 Gilles Gouaillardet via users,
> >     <users@lists.open-mpi.org <mailto:users@lists.open-mpi.org>> wrote:
> >     >>>>>> >>
> >     >>>>>> >> Is SELinux running on ArchLinux under Termux?
> >     >>>>>> >>
> >     >>>>>> >> On 2/25/2021 4:36 PM, LINUS FERNANDES via users wrote:
> >     >>>>>> >> > Yes, I did not receive this in my inbox since I set to
> >     receive digest.
> >     >>>>>> >> >
> >     >>>>>> >> > --------
> >     >>>>>> >> > ifconfig output:
> >     >>>>>> >> >
> >     >>>>>> >> > dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
> >     >>>>>> >> >         inet6 fe80::38a0:1bff:fe81:d4f5 prefixlen 64
> >     scopeid 0x20<link>
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 0 (UNSPEC)
> >     >>>>>> >> >         RX packets 0 bytes 0 (0.0 B)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 3 bytes 210 (210.0 B)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> >     >>>>>> >> >         inet 127.0.0.1 netmask 255.0.0.0
> >     >>>>>> >> >         inet6 ::1 prefixlen 128 scopeid 0x10<host>
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 0 (UNSPEC)
> >     >>>>>> >> >         RX packets 17247 bytes 2062939 (1.9 MiB)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 17247 bytes 2062939 (1.9 MiB)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> > p2p0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 1000 (UNSPEC)
> >     >>>>>> >> >         RX packets 0 bytes 0 (0.0 B)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 0 bytes 0 (0.0 B)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> > rmnet_data0: flags=65<UP,RUNNING> mtu 1500
> >     >>>>>> >> >         inet 10.140.58.138 netmask 255.255.255.252
> >     >>>>>> >> >         inet6 fe80::93a5:ad99:4660:adc4 prefixlen 64
> >     scopeid 0x20<link>
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 1000 (UNSPEC)
> >     >>>>>> >> >         RX packets 416796 bytes 376287723 (358.8 MiB)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 318293 bytes 69933666 (66.6 MiB)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> > rmnet_data7: flags=65<UP,RUNNING> mtu 2000
> >     >>>>>> >> >         inet6 fe80::a6b7:c914:44de:639 prefixlen 64
> >     scopeid 0x20<link>
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 1000 (UNSPEC)
> >     >>>>>> >> >         RX packets 8 bytes 620 (620.0 B)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 10 bytes 752 (752.0 B)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> > rmnet_ipa0: flags=65<UP,RUNNING> mtu 2000
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 1000 (UNSPEC)
> >     >>>>>> >> >         RX packets 222785 bytes 381290027 (363.6 MiB)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 318303 bytes 69934418 (66.6 MiB)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> > wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> >     >>>>>> >> >         unspec
> >     00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> >     >>>>>> >> > txqueuelen 1000 (UNSPEC)
> >     >>>>>> >> >         RX packets 650238 bytes 739939859 (705.6 MiB)
> >     >>>>>> >> >         RX errors 0 dropped 0 overruns 0 frame 0
> >     >>>>>> >> >         TX packets 408284 bytes 63728624 (60.7 MiB)
> >     >>>>>> >> >         TX errors 0 dropped 0 overruns 0 carrier 0
> >     collisions 0
> >     >>>>>> >> >
> >     >>>>>> >> >
> >     >>>>>> >> > -----
> >     >>>>>> >> > ip addr output:
> >     >>>>>> >> >
> >     >>>>>> >> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue
> >     state UNKNOWN
> >     >>>>>> >> > group default
> >     >>>>>> >> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     >>>>>> >> >     inet 127.0.0.1/8 <http://127.0.0.1/8>
> >     <http://127.0.0.1/8 <http://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: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500
> >     qdisc noqueue state
> >     >>>>>> >> > UNKNOWN group default
> >     >>>>>> >> >     link/ether 3a:a0:1b:81:d4:f5 brd ff:ff:ff:ff:ff:ff
> >     >>>>>> >> >     inet6 fe80::38a0:1bff:fe81:d4f5/64 scope link
> >     >>>>>> >> >        valid_lft forever preferred_lft forever
> >     >>>>>> >> > 3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> >     link/sit 0.0.0.0 brd 0.0.0.0
> >     >>>>>> >> > 4: rmnet_ipa0: <UP,LOWER_UP> mtu 2000 qdisc pfifo_fast
> >     state UNKNOWN
> >     >>>>>> >> > group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 5: rmnet_data0: <UP,LOWER_UP> mtu 1500 qdisc htb state
> >     UNKNOWN group
> >     >>>>>> >> > default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> >     inet 10.140.58.138/30 <http://10.140.58.138/30>
> >     <http://10.140.58.138/30 <http://10.140.58.138/30>> scope global
> >     >>>>>> >> > rmnet_data0
> >     >>>>>> >> >        valid_lft forever preferred_lft forever
> >     >>>>>> >> >     inet6 fe80::93a5:ad99:4660:adc4/64 scope link
> >     >>>>>> >> >        valid_lft forever preferred_lft forever
> >     >>>>>> >> > 6: rmnet_data1: <> mtu 1500 qdisc noop state DOWN
> >     group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 7: rmnet_data2: <> mtu 1500 qdisc noop state DOWN
> >     group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 8: rmnet_data3: <> mtu 1500 qdisc noop state DOWN
> >     group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 9: rmnet_data4: <> mtu 1500 qdisc noop state DOWN
> >     group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 10: rmnet_data5: <> mtu 1500 qdisc noop state DOWN
> >     group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 11: rmnet_data6: <> mtu 1500 qdisc noop state DOWN
> >     group default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 12: rmnet_data7: <UP,LOWER_UP> mtu 2000 qdisc htb
> >     state UNKNOWN group
> >     >>>>>> >> > default qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> >     inet6 fe80::a6b7:c914:44de:639/64 scope link
> >     >>>>>> >> >        valid_lft forever preferred_lft forever
> >     >>>>>> >> > 13: r_rmnet_data0: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 14: r_rmnet_data1: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 15: r_rmnet_data2: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 16: r_rmnet_data3: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 17: r_rmnet_data4: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 18: r_rmnet_data5: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 19: r_rmnet_data6: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 20: r_rmnet_data7: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 21: r_rmnet_data8: <> mtu 1500 qdisc noop state DOWN
> >     group default
> >     >>>>>> >> > qlen 1000
> >     >>>>>> >> >     link/[530]
> >     >>>>>> >> > 22: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu
> >     1500 qdisc mq state
> >     >>>>>> >> > DOWN group default qlen 1000
> >     >>>>>> >> >     link/ether 04:d1:3a:07:70:4b brd ff:ff:ff:ff:ff:ff
> >     >>>>>> >> > 23: p2p0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
> >     qdisc mq state
> >     >>>>>> >> > DOWN group default qlen 1000
> >     >>>>>> >> >     link/ether 06:d1:3a:07:70:4b brd ff:ff:ff:ff:ff:ff
> >     >>>>>> >> >
> >     >>>>>> >> >
> >     >>>>>> >> > This is on Arch Linux on Termux.
> >     >>>>>> >> >
> >     >>>>>> >> > Similar output on Termux available.
> >     >>>>>> >> >
> >     >>>>>> >> >
> >     >>>>
> >     >>>>
> >     >>>>
> >     >>>> --
> >     >>>> Jeff Squyres
> >     >>>> jsquy...@cisco.com <mailto:jsquy...@cisco.com>
> >     >>>>
> >     >>>
> >     >>>
> >     >>> --
> >     >>> Jeff Squyres
> >     >>> jsquy...@cisco.com <mailto:jsquy...@cisco.com>
> >     >>>
> >
>

Reply via email to