I have the same issue as several posts of both this model and other where the WAN IP address is not passed through to the router in pass-through mode. I am using a Ubiquiti UDM Pro which picks a local class C IP address from the TRB. I have tried all the workarounds of setting the lease time to 2 mins in both DHCP scope and WAN DHCP. I have tried setting DHCP off for Modem connection and hard setting MAC address of downstream router - nothing passed through. Others have the same issue and I would be tempted to roll back firmware to 7.3 as in this post - but that a long time of having been broken without a fix and what else will I then discover broken going back that far.
https://community.teltonika.lt/t/trb500-upgrade-from-07-3-to-07-08-local-ip-leased-instaed-of-wan/7371
Any other ideas anyone? I suspect this issue exists on other TRB’s too.
Thanks.
Hi,
Which firmware version you’re running on your TRB500? It should’ve been fixed with R_00.07.09.2
Did you try to disconnect/reconnect the LAN cable after setting the DHCP lease time to 2mins?
If not, the router may still have the long duration lease from before you changed that.
I do not know the UDM routers, there may be some “renew lease” button that you need to click once.
Unplugged, replugged, rebooted both TRB and Unifi (last).
Firmware latest version 00.07.10.
Teltonika support confirmed it works and advised setting up from a TRB factory reset - tried that too.
And now I have managed to brick it, can’t get access anymore - and it’s on the roof. I’ve retrieved another which is on the bench until I get this working - then will swap it.
Teltonika had said to put int he MAC address of the WAN port on my Unifi (UDM-Pro) which I did. I even confirmed this was the actual MAC with a network scan on the WAN side. I noticed the new firmware has a ‘WAN to LAN’ button in the LAN page which seems to set up another interface in the WAN menu - this is what had bricked it.
If only Teltonika had a reset option via the Ethernet cable like the Ubiquiti products (button on PoE adaptor).
Ok for me with a MikroTik router the passthrough mode worked when 2min DHCP lease time was configured (in two places).
However, I went back to NAT mode because the passthrough mode has considerably lower performance.
Hopefully that will be rectified at some time.
Remote reset via the cable like Ubiquiti offers has the disadvantage that with slight moisture ingress it will falsely detect a reset attempt. So I normally disable that in the config. It may be useful during initial setup but not in the long run.
Thank you all for your input. I do now have this solved and made a few observations along the way which may help others. Firstly, having lost connection to the TRB500 in antenna enclosure on the roof I thought it was time for the ladder to come out then remembered the SMS options and sure enough, sending a factory reset worked and allowed me to gain access again.
Setting up for passthrough works but it took at least 10 mins before the Ubiquiti (UDM Pro) would show the WAN IP. Initially I only noticed IPv6 show up together with the local class C address which was confusing. I now suspect the IPv6 was the WAN IP. Going through the setup again I changed the setting to TCPv4 only for the Cell connection because I previously had issues with RMS connections until IPv6 was disabled. This time, after many refreshes of the Ubiquiti dashboard IPv6 disappeared and IPv4 updated to show WAN IP (at least 10 mins after the change.
I have found the performance to be a significant improvement on NAT. Roughly 25% better on speed but its a continuous throughput, in NAT mode it seemed traffic was sent in bursts which meant voice calls were impossible with double NAT.
Thanks.
Of course when your 5G IP is dynamic it is even more important to set a short lease time, but for us that worked with 2min (the minimum) and as our connection always closes 24h after it is established (provider policy) and the new connection has a new IP, you need to have a short lease time so the router notices that. Maybe there are issues in the UDM when a DHCP server refuses to renew the lease and the router should do a new discover request.
Anyway, my (and other people) experience is that a passthrough connection has a ceiling of around 220-250 Mbit/s when the TRB500 CPU is 100% loaded, while a NAT connection apparently is hardware-accelerated and can go higher. I observed up to 650 Mbit/s with NAT. Still too slow of course, our provider offers well over 1 Gbit/s, but acceptable for now. I bought the TRB500 only as a quick stopgap until better equipment, with 2.5 Gbit/s ethernet and PoE, becomes available.
That is interesting. The UK 5G position at the moment is woeful. EE seems to be vastly superior in most regions I visit but locally it’s no more than 200MB so well inside your findings. O2 seems very poor. I don’t think we have any standalone 5G either so it’s mostly piggybacking on 4G pretending to be 5G.
I recently setup the same TRB500 with Quwireless antenna (4x4) in the West of France and was able to get 860MB/s throughput to a laptop even after going through a basic Ubiquiti compact router so I’m keen to check what setup I used - fairly certain it was NAT.
We have O2 5G SA at our UK location … O2 are starting to roll out.SA in UK and certainly Spain, targeting large conurbations first.
Some interesting observations in this thread, which seems to vaidate that Bridge and Passthrough is still not functioning well, despite some references being made to it in release notes.
There is a woeful silence from Teltonika, when prompted to explain all … maybe their Marketing department have taken over running the Community 
I have not yet tested passthrough with the 7.10 firmware, although I have that running on the TRB500.
Is there any indication that the bandwidth cap for passthrough has been resolved in that version?
(i.e. that it is just as fast as NAT now)
I won’t have access to my ‘lab’ environment for another 6 weeks, so until then, I cannot give bridge/passthrough a good thrashing to see if 07.10 made anything better.
I assume your two lease time changes on the Teltonika were …
a) lease time for WAN interface mob1s?a1
b) lease time on DHCPv4 servers
Cheers,
Mike
Yes, these two DHCP settings need to be set as low as possible or at least as required for how long you want the connection to be down when the WAN IP changes or the connection is down/up.
I have suggested a feature where the TRB500 would bring the ethernet link down and back up when that happens, which would usually trigger the connected device to repeat the DHCP request, but as far as I know that has not been implemented yet.
Now THAT is something I would use, and a lot of others, judging from the support requests on here.
Many thanks … Mike
This topic was automatically closed after 15 days. New replies are no longer allowed.