Why isnt this fixed in a firmware?! We used 4.5 hours today for diagnostics… And then we found this ticket?!
Only thing that worked for our RUTX50 (bridgemode to get public WAN address) → Cisco ASA FP1010 was to use these commands from another user ( roberttz
The script didnt work, so our script is like this:
sed -i ‘s/bridge_mask=255.255.255.254/bridge_mask=255.255.255.254/g’ /lib/functions/mobile.sh
iptables -I forwarding_wan_rule -m comment --comment “!fw3: Mobile bridge” -j zone_lan_dest_ACCEPT
iptables -t nat -I postrouting_rule -o wwan0 -j SNAT --to 46.77.101.129
ifup mob1s1a1
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh del 46.77.101.129 dev br-lan
ip neigh add 46.77.101.129 dev br-lan lladdr e4:fc:82:dc:98:88
This fix should be already implemented I guess in the newest 7.5 series of RutOS’es but somehow Teltonika didn’t make it to include, so I guess next 7.6 RutOS should have fixed ARP problem as they know about it for at least 3-4 months. I hope I helped you with fixing issue.
We would like to investigate your case. Would it be possible for you to contact us through your assigned sales manager or the reseller from whom you purchased the device? If this is not feasible, kindly fill out the ‘contact us’ form here. Please, mention this forum topic and provide some details about the current situation within the form. Thank you!
Hello AndzejJ,
I have tested right now newest RutOS 7.06 with Passthrough issue, despite I see in Changelog some fixes about “Fixed Mobile interface bridge and passthrough mode connectivity loss”,
I see that after configuring Passthrough and rebooting RUT240 it starts to operate OK only for about 10 seconds (10 pings) and then it breaks/crashes due to not patched problem with ARP Incomplete which RUT240 holds invalid entry (my Juniper router gets about 10 responses from pinging Google 8.8.8.8 and then it stops to receive responses), although I see now a little progress, because since 7.05 local virtual point-to-point subnet /30 is now pingable, by default, so I don’t need to add post-NAT routing script anymore. This at least makes me happy (I guess it’s possible right now due to reconstruction of firewall, itself). Problem is now norrowed down to fixing pending ARP Incomplete issue.
Anyway, I still need to appy Script in the GUI at atostart to clear ARP entry (Incomplete):
ip neigh del 46.77.101.129 dev br-lan
ip neigh add 46.77.101.129 dev br-lan lladdr e4:fc:82:dc:98:88
which forces RUT device at startup to clear entry by itself - I tried to login via SSH and clear it manually but its problematic (sometimes you need to do it several times because command via CLI are not applyable).
Yes, go ahead, RnD can contact with me directly via e-mail: [redacted]
u can find my e-mail at user profile at forum
(then we can establish remote session for checkings etc.).
Unfortunately, we cannot do that this way. Could you please either fill out the ‘contact us’ form or, even better, ask your manager to create a ticket for us again (and mention this issue)?
Hi @roberttz,
Has there been any progress on this? I’m new to Teltonika products and recently bought a RUTX50. I’m trying to put it into Bridge mode and connect to my existing TP-Link Mesh router. Whilst the TP-Link receives and IP address, it cannot connect to the internet when the RUTX50 is in bridge mode or passthrough mode. I wondering if it’s related to the issues outlined in this thread.
Hi, Yes there is progress with the topic. I co-operated with AndzejJ outside forum and tested newest developers fixes - with upcoming new firmware they should be implemented, so expect with RutOS 7.7 resolution of the bugs. I don’t know when new Rut 7.7 will be released but I think within 1-2 months it should be available for mass production.
Looking at this topic i have the exact same isue, my Unifi udm pro se have the exact same problems. I get an ip adress from the RUT but there is no internet connection. And i stil dont know what to do then wait for a fix.
Teltonika lately released newest firmware update to RutOS 7.07, finally it includes patches for Passthrough feature we were expecting, you can see in changelog:
Mobile: updated bridge/passthrough mode logic to flush ARP and add static ARP entry if MAC is specified
Mobile: added metric to default gateway when using passthrough mode
If you have at least RUT241 and other series devices, go to WikiPage where you can download new firmware release with correct fixes and forget about the issue.
For those who have older RUT240 (and other outdated legacy) devices in EoL support process, Teltonika will not prepare upgrade to RutOS 7.07 they abandon and discontinue preparing new extensive releases
due to R&D time required for older chipset development etc.
You can read in side topic: RUT240 - will it receive upgrade to RutOS 7.07?
AndzejJ mentioned that for RUT240 fixes for Passthrough feature will be included in latest package fixes
in nextcoming version RutOS v7.06.12 firmware. So I think you should wait about 1-2 months for corrections.
To summarize things up for Passthrough fixes:
RUT241 and newer devices > download at least newest RutOS 7.07
RUT240 - wait and download latest nextcoming and available fixes in RutOS v7.06.12 or newer.
(right now, by the time writing this topic currently available is only: RUT2_R_00.07.06.11)
Dear All,
Teltonika has released patch for RUT240 in OS RUT2_R_00.07.06.12 in 2024.06.20,
it includes same bug fixes as in new line firmware starting RutOS 7.07 and later.
Passthrough stability is resolved starting this firmware anything below should use autoscript in this topic or upgrade OS to this version, itself.
For other newer devices use at least RutOS 7.07 or later and for discontinuated devices at least RutOS 7.6.12.
@AndzejJ Please close this ticked as the case is resolved by R&D.
Any issues reported by other users should be continuated in different thread.
Thank you.