Ping 169.254.19.105 works in wsl 2 but no DepthAI device found when I run demo app OAK D Pro W POE. [Getting started with OAK PoE devices — DepthAI Hardware Documentation 1.0.0 documentation (luxonis.com)](https://docs.luxonis.com/projects/hardware/en/latest/pages/guides/getting-started-with-poe/#manually-specify-device-ip) Ive tried setting manual ip but when I run it, it says 'Cannot find any device with given deviceInfo' When I tried to run example file using: python3 ColorCamera/rgb_preview.py Output: No Available devices found My connection to the [upl-image-preview url=https://discuss.luxonis.com/assets/files/2024-03-27/1711576142-701035-image-20240319-1502553254471055538724320.jpg] [upl-image-preview url=https://discuss.luxonis.com/assets/files/2024-03-27/1711576497-194036-image-20240319-15033088952162560873962.jpg] The above image shows the orange wire connector to the docker which in turn is connected to my computer through a usb. I was wondering how I can check if both are connected in the same LAN network?

Hi @"SarveshRathi"#2382 Check your network card for the IP with `ifconfig` (mac/linux) or `ipconfig` (win). Make sure they are in the same subnet range. Alternatively, you can pass the IP of the device in the script. ``` with dai.Device(pipeline, deviceInfo=dai.DeviceInfo("169.254.19.105"), maxUsbSpeed=dai.UsbSpeed.SUPER) as device: ``` Should work I think since it skips local broadcast call. Thanks, Jaka

My local machine is windows and associated subnet mask is 255.255.0.0. Im using linux using wsl and associated subnet mask is eth0: 255.255.240.0 Note: Any way to identify if it is associated to eth0 or lo? If this is not correct, how to change the subnet mask and what value i should set it to? To your alternate solution, which script should I pass the ip to? If youre referring 'script to manually assigning ip', Ive already done that, but when I run it, it says 'Cannot find any device with given deviceInfo'

Networking under WSL is solid but has a few quirks, I'd recommend confirming you can connect via Windows proper first of all, and only then troubleshoot from within WSL. As Jaka mentioned, run `ipconfig` in a Windows command line/Powershell/Terminal, the command works in all of them, which will tell you the IP address Windows is assigning to the wired ethernet adapter. If you then run `ifconfig` I'll bet you get a different set of IP addresses. By default WSL runs in NAT mode and you don't actually get full access to the network. This most commonly hits when you're trying to access services hosted within WSL from different computers, but I suspect something similar is going on here too. Other things to confirm, but I suspect you're running WSL2, what version of WSL are you using? `wsl --version` in Windows Terminal will give that. WSL1 worked differently and gave more open network access by default, WSL2 however has NAT mode as standard. Make sure you read through it and understand the caveats, but I suspect that enabling Mirrored Network Mode may help. It'll give your WSL instances access to the same network adapters that Windows has. It's not exactly user friendly to configure, but should just be a couple of commands. More info here: https://learn.microsoft.com/en-us/windows/wsl/networking

@"kneave"#p18904 The IP on windows is 169.254.19.105 and subnet mask is 255.255.0.0 When I call ipconfig, it also shares ethernet adapter vEthernet(WSL(Hyper-V Firewall)) : 172.26.208.1, subnet mask 255.255.240.0 ip route show | grep -i default | awk '{ print $3}' - 172.26.208.1 I am running WSL2.

Yup, it's in NAT mode. Have a look at changing to mirror mode.

@"kneave"#p18970 Thanks for quick follow ups on my queries. Appreciate your time. I have made .wslconfig file like suggested and added mirrored setting. Note: .wslconfig.txt is what i made in the directory suggested. Is that fine? When I call sudo wget -qO- https://docs.luxonis.com/install_depthai.sh | bash and I open demo viewer , it still didnt find any depth ai devices. Note: 1. Im still able to ping the sensor with the same ip in windows and linux(wsl2). 2. I also reopened wsl and then run sudo wget -qO- https://docs.luxonis.com/install_depthai.sh | bash. But it still doesnt work Any suggestions?

I just checked my laptop and it's `.wslconfig` without a file extension so it's worth being exact. If you see the same IP addresses and still can't connect though then I'll have to leave that to the experts at Luxonis. I've never used a POE device, I just jumped in as I have experience with WSL networking.

@"kneave"#p19013 I made a wslconfig file without the extension but still doesnt show any Depth ai devices. @"jakaskerl"#p18881 Any suggestions?

Did you create `wslconfig` or `.wslconfig` as the . at the front makes a big difference. Please share the contents of the file and the new ip/if config outputs too, if you can confirm you've rebooted too please as WSL will need to restart I think.

@"kneave"#p19015 Ive used .wslconfig the contents are: [wsl2] networkingMode=mirrored [upl-image-preview url=https://discuss.luxonis.com/assets/files/2024-04-02/1712093996-757252-image.png] [upl-image-preview url=https://discuss.luxonis.com/assets/files/2024-04-02/1712094178-905965-image.png] I did close the terminal and reopened wsl. That reboots wsl right?

No depth ai devices found - wsl2 - ping works

SarveshRathi

kneave Thanks for your feedback! Will take care from next time to help you debug.

I have done a reset to the network settings. Based on this article suggestion, I should change ethernet 3, ethernet adapter wsl and eth0 inet ips right?

kneave

No, only the IP address of the interface you're connecting the POE device to

SarveshRathi

kneave

When I use 169.254.1.222 in imu_version.py,

RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

kneave

What have you set the address of the ethernet port to that it connects to?

SarveshRathi

kneave

Based on ifconfig (wsl)

eth0 inet ip is 172.26.220.210/20

Based on ipconfig (windows)

192.168.56.1 255.255.255.0

After adding 169.254.1.10/16 in eth0, it says no device found. without it its saying RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

kneave

WSL is still in NAT mode in that case.

The xlink error sounds like it's actually connecting to the camera at least.

SarveshRathi

kneave what mode should I change it to?

kneave

This is from the first post I made on this topic...
https://discuss.luxonis.com/d/3754-no-depth-ai-devices-found-wsl2-ping-works/4

SarveshRathi

kneave I already have a .wslconfig file with networkingMode=mirrored.

All 3 ips for ethernet 3, Luxonis and Hyper-V manager as defined in windows are responding to the ping inside wsl. Even static ip ping is working. This does mean that there is no bridge issue right?

running imu_version still outputs:

RuntimeError: Failed to find device after booting, error message: X_LINK_DEVICE_NOT_FOUND

kneave

'xlink device not found' suggests you've connected to be honest, maybe the IMU just doesn't work.

I'd suggest making a script on windows that you know works and then trying it again in WSL. If you have something working you know the camera works at least and the code is transferable as long as you've the libraries installed

SarveshRathi

kneave I have the ros environment installed and running in wsl.

Can you recommend another script and a suggestion for changing the line where I should make the static ip change ? Maybe something that does not use imu. Lets say for example rgb_video.py?

@Jackmarks In the case imu is not working, will it be possible to send a replacement for the device?

kneave

You've been told how to change the scripts and there are plenty of examples available. I'm sorry but if you can't spend the time to figure that out and experiment with scripts yourself you'll never learn how to use these cameras.

SarveshRathi

kneave Thanks for your time. Ill try a couple of things. Hopefully its not a hardware issue is what im hoping.

« Previous Page