# Waterlinked DVL only found when tether attached **URL:** \ **Category:** Third Party Products\ **Created:** [October 8, 2024, 12:36pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225 "2024-10-08T12:36:57Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![cmarq](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@cmarq](https://discuss.bluerobotics.com/u/cmarq)\ **Post date:** [October 8, 2024, 12:36pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/1 "2024-10-08T12:36:57Z")
Hi all, My current setup is a blueROV2 with the blueOS/Navigator retrofit and a waterlinked DVL A50. Additionally, we are converting the vehicle to an AUV, so I have installed a removeable tether that connects to a tp-link nano router as discussed in this link [https://www.ardusub.com/developers/wireless-topside.html](https://www.ardusub.com/developers/wireless-topside.html) This setup is working for me. But I have one thing that is causing issues. It seems the Waterlinked DVL extension cannot find the DVL unless the tether is attached with the router turned on. In the case the tether is attached, it says that it is searching on [192.168.2._, 192.168.3._] and finds it rather quickly. But, if the tether is not attached, then it tries searching on [192.168.3.\*] and returns the possible DVL’s as . My current workaround is to start the vehicle with tether attached, wait until it is found, then detach the tether and run tests. This tends to work for around 1-2 hours then the DVL disconnects from the extension and I’m in the same boat of having to restart with tether attached again Any thoughts on how to get around this? ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [October 8, 2024, 8:32pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/2 "2024-10-08T20:32:31Z")
Hi @cmarq, Maybe it is relying on the tp-link nano router for the dhcp server? what ip is it usually found at? ---
**Author:** ![cmarq](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@cmarq](https://discuss.bluerobotics.com/u/cmarq)\ **Post date:** [October 9, 2024, 12:09pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/3 "2024-10-09T12:09:01Z")
![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/8/881305f841f11020f901d2eded4642d7c374b1f2.png) Could this step be causing the issue there? ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [October 9, 2024, 11:58pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/4 "2024-10-09T23:58:39Z")
@cmarq Those instructions are outdated, but that should do no harm. Try [enabling the dhcp server in Blueos](https://blueos.cloud/docs/blueos/1.2/advanced-usage/#wired-network-management-ethernet-usb-otg) and restart (by power-cylcing, so the dvl restarts too) the whole system. ---
**Author:** ![cmarq](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@cmarq](https://discuss.bluerobotics.com/u/cmarq)\ **Post date:** [October 10, 2024, 7:00pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/5 "2024-10-10T19:00:55Z")
That button to enable the dhcp server is greyed out for me. I cannot click it ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/13297_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [October 10, 2024, 8:17pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/6 "2024-10-10T20:17:35Z")
Hi @cmarq - Does it look like this? ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/2/2748d4e58e521f8169c92131020a0b99818d7d4f.png) You should be able to click Enable DHCP Server despite the different color of the button… you’ll need to select the gateway option when it opens the pop-up- there should only be one. A static IP **must** be present before you can enable the DHCP server. ---
**Author:** ![cmarq](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@cmarq](https://discuss.bluerobotics.com/u/cmarq)\ **Post date:** [October 10, 2024, 8:38pm UTC](https://discuss.bluerobotics.com/t/waterlinked-dvl-only-found-when-tether-attached/18225/7 "2024-10-10T20:38:47Z")
I can’t even express how awesome it is that that worked. Even proxy setup works now to be able to see the DVL status and turn it on/off without the tether Thanks so much