I am using a TRB500 for WAN on a UDM and it passes through the IP from the carrier.
A major and four minor differences in my setup.
The major difference is that I have a VLAN for management.
UDM: The TRB500 is connected to a switch port (not the UDM WAN port) and then a switch port is connected to the UDM WAN port. With the correct port settings the UDM WAN behaves as it is directly connected to the TRB500 on the default LAN. I then have access through the VLAN to the TRB500 (and in my case other devices) for management.
There may be a more elegant way to get access to the TRB500 VLAN do this with routing rules, or using the RMS service (neither of which I tried).
TRB500 WAN: I have PDP type set to IPv4, lease time to 2 minutes, MAC address set for the UDM WAN port.
TRB500 LAN: PDP type set to IPv4 and Enable DHCPv4 turned on.
Thank you! I changed some settings on the TRB500 like you said and with the Teltonika TRB500 connected to the wan2 port, i now get an IP address and carrier name.
Even if i enter my wan2 ip address in my browser i can connect to my server so i think it works. Thanks a lot!
Either the TRB500 is not getting an IP from the carrier, or it is and is not passing it through. Unfortunately, I don’t know how to debug this. Someone else might be able to help. I presume you have restarted everything.
My other TRB500 LAN settings are:
Advanced: Fore link on
Physical settings: Bridge Interfaces on.
Physical settings: Interface eth0, ecm0.
I get notifications and can see it in the UDM logs (partially). The “Critical” tab of the System Log (bottom left clipboard icon) shows some of the events. Clicking on the ISP name on the dashboard shows others. My guess is that it is something to do with the DHCP lease times set on the TRB500. I’ve changed those to 1hr to see if that makes a difference.
In my case the TRB500 is the primary WAN, so its a little more obvious when it fails and goes to the secondary WAN. The secondary is also wireless (Mikrotik 4G) but does not seem drom the connection as frequently.