ApolloX in WSL cannot see connected SoM

Technical Support
, , ,
6

Hi @lucas_a.tx
I don’t think this is the case, because now that I connected the Verdin to my company LAN, the IP is assigned through DHCP.
I read one more time the explanation of @matheus.tx in this other topic related to issues of ApolloX in a Virtual Machine.

If I change the 192.168.0.0./24 by the IP range of my physical network interface (10.3.1.0/24), I can see the Verdin.

Is it possible that the “default network interface” is not the best approach in WSL?
If I run route, I get

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         my_pc_name      0.0.0.0         UG    0      0        0 eth0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.26.128.0    0.0.0.0         255.255.240.0   U     0      0        0 eth0

And cat /etc/resolv.conf returns

# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver 172.26.128.1

where 172.26.128.1 is the ip of vEthernet (WSL) adapter in my Windows machine.

I suspect that ApolloX scanning feature in WSL needs some additional configuration to work (if possible).
What do you think @lucas_a.tx and @matheus.tx?