Help for UDM-PRO and VDSL technology
Help for UDM-PRO and VDSL technology
Hey there! I noticed you're working on upgrading your home network to the Ubiquiti Unifi setup and owning a UDM-PRO. Since you're in Australia, your area is currently limited to FTTN via Aussie Broadband. You mentioned using a NetComm modem set up in bridge mode with an EdgeRouter, but it took hours to get it working and you're still unsure what caused the issue. Now you're facing problems with your UDM setup. It sounds like VDSL might be the culprit, but none of your attempts so far have resolved it. Any tips or alternatives could really help!
It has been a long time since I've worked with ADSL/VDSL connections, but I've consistently achieved great results using DrayTek xDSL modems and enabling 'Half Bridge Mode'. Back then, they were the top choice for ADSL, though they now support VDSL as well. The Half Bridge feature allows the modem to handle authentication and negotiation for DSL, then transfers full control of Ethernet and higher layers to your UDM-PRO device. You simply need to set up an Ethernet WAN port with DHCP (or a static IP if you don’t use DHCP) and that’s it.
You can find more details here:
- https://www.draytek.co.uk/support/guides...-dsl-modem
- https://www.draytek.com/support/knowledge-base/5367
P.S. The term 'Half Bridge Mode' isn’t an official name—they just used that description at the time. Different bridge configurations and setups work in various ways.
Only if you truly can't get it to function on that NetComm device, I suppose you've set up your router in a way similar to this one? Check your ISP's VPI/VCI and VLAN configurations. Also, look at the router's EdgeRouter WAN port setup.
This document provides a detailed Aus-focused reference for Half Bridge Mode setup. It aligns with the style of the referenced PDF guide.
The screen indicates no internet connection is present, and the interface typically displays only the modem's IP address from the WAN port without additional details.
Thanks for your assistance. It seems the problem was with the ISP side. They took some time to pinpoint it, but everything is now working properly!