Hi Marcos,
Pasted below the output.
Thank you. Regards,
Martín
internal_name: {C3C1A65B-A775-4604-A187-C1FDC48EC211}
flags: AF_INET6 up running multicast
address: fe80::c4a3:827f:bd3c:141%16
friendly_name: Ethernet
internal_name: {C3C1A65B-A775-4604-A187-C1FDC48EC211}
flags: AF_INET up broadcast running multicast
address: 192.168.56.1
friendly_name: Ethernet
internal_name: {8F915CBF-9C68-4DFA-9AE1-FF3207DA0CC9}
flags: AF_INET6 up multicast
address: fe80::f84e:e8e9:b2e7:7f23%9
friendly_name: Local Area Connection* 1
internal_name: {8F915CBF-9C68-4DFA-9AE1-FF3207DA0CC9}
flags: AF_INET up broadcast multicast
address: 169.254.127.35
friendly_name: Local Area Connection* 1
internal_name: {9C9C1DB9-1E8B-4893-A83F-C881060ED6DF}
flags: AF_INET6 up multicast
address: fe80::3c7c:e0b3:af76:3a0%11
friendly_name: Local Area Connection* 2
internal_name: {9C9C1DB9-1E8B-4893-A83F-C881060ED6DF}
flags: AF_INET up broadcast multicast
address: 169.254.3.160
friendly_name: Local Area Connection* 2
internal_name: {A6301D34-A586-4439-B7A7-69FA905CA167}
flags: AF_INET6 up running multicast
address: fe80::e5c6:c83:8653:3cd8%14
friendly_name: VMware Network Adapter VMnet1
internal_name: {A6301D34-A586-4439-B7A7-69FA905CA167}
flags: AF_INET up broadcast running multicast
address: 192.168.148.1
friendly_name: VMware Network Adapter VMnet1
internal_name: {B259A286-0A90-429D-97A1-D4CEAA97EA42}
flags: AF_INET6 up running multicast
address: fe80::555d:6f18:486e:376e%15
friendly_name: VMware Network Adapter VMnet8
internal_name: {B259A286-0A90-429D-97A1-D4CEAA97EA42}
flags: AF_INET up broadcast running multicast
address: 192.168.200.1
friendly_name: VMware Network Adapter VMnet8
internal_name: {1BA832E1-BEA7-4E7B-8FFA-9BBDCBA170A6}
flags: AF_INET6 up running multicast
address: fe80::8038:114f:63e0:81a3%5
friendly_name: Wi-Fi
internal_name: {1BA832E1-BEA7-4E7B-8FFA-9BBDCBA170A6}
flags: AF_INET up broadcast running multicast
address: 192.168.100.45
friendly_name: Wi-Fi
internal_name: {144D1ED1-0EE5-47E1-82A7-7E4ABB8DB2D8}
flags: AF_INET6 up multicast
address: fe80::c4f8:6145:cc59:4c4b%3
friendly_name: Bluetooth Network Connection
internal_name: {144D1ED1-0EE5-47E1-82A7-7E4ABB8DB2D8}
flags: AF_INET up broadcast multicast
address: 169.254.76.75
friendly_name: Bluetooth Network Connection
internal_name: {EB43FC56-BCC2-11EA-A07A-806E6F6E6963}
flags: AF_INET6 up loopback running multicast
address: ::1
friendly_name: Loopback Pseudo-Interface 1
internal_name: {EB43FC56-BCC2-11EA-A07A-806E6F6E6963}
flags: AF_INET up loopback running multicast
address: 127.0.0.1
friendly_name: Loopback Pseudo-Interface 1
internal_name: {A04CB0D8-879C-418C-8BB7-209EEADBDCD0}
flags: AF_INET up broadcast multicast
address: 0.0.0.0
friendly_name: Ethernet (Kernel Debugger)
internal_name: {D9635C22-48DE-4359-99BA-057A3850FA03}
flags: AF_INET up broadcast multicast
address: 192.168.56.1
friendly_name: VirtualBox Host-Only Network
From: Marco Atzeri via users<mailto:users@lists.open-mpi.org>
Sent: viernes, 5 de febrero de 2021 13:37
To: users@lists.open-mpi.org<mailto:users@lists.open-mpi.org>
Cc: Marco Atzeri<mailto:marco.atz...@gmail.com>
Subject: Re: [OMPI users] OMPI 4.1 in Cygwin packages?
On 05.02.2021 16:18, Martín Morales via users wrote:
> Hi Gilles,
>
> I tried but it hangs indefinitely and without any output.
>
> Regards,
>
> Martín
>
Hi Martin,
can you run get-interface available on
http://matzeri.altervista.org/works/interface/
so we can see how Cygwin identify all your network interface ?
Regards
Marco
