Hello! I have configured a netwatch test block to call a script which gets lte interface stats. It was working fine on ROS 7.7 stable, but after upgrade to ROS 7.8rc1 it fails when is called by netwatch. Similarly, it doesn't work when called by scheduler. If i call it manually, then script complete...

All my suggestions, apart from the error you fixed, are based on the fact that if you ask someone for help, if the script is unreadable, they resign... Any excess additional signs, which can be omitted, better not put, rather sometimes it is better to write more instead of less. For example: better...

@rextended thank you, for a such descriptive answer. I appreciate your assistance, however i can't agree with all mentioned, so i hope you wouldn't mind that i'll comment some quotes. Of course, I'm taking into account your previous note, too. It is also a mistake to blindly rely on what I write. I'...

It's time to stop programming with feet. I tried to fix the script on OP, but this is so buggy that I gave up. Also on your post :global gwLoss [:pick $trc 5] must be writed :global gwLoss ($trc->"loss") Using positional syntax with fixed index, on fields that have names, do not work and ...

Probably you're comparing (if) with nothing. Can i see the results of up & down LTE state from: :put [/tool traceroute address=1.0.0.1 max-hops=1 count=5 as-value] Thanks for a tip, but when running checks directly i get sane results: [colt@uTik] > :put $test [colt@uTik] > :put ($test > 0) fals...

Hello! I've configured Netwatch to additionally ping host in On Down event, which works flawlessly. Additionally, i've configured a script nwatch-ltegateway that checks first n hops to provided host. It works when called from Test or On Up events, but if called from On Down, then On Down event fails...

It could very well be the signal you're getting, but normally the problem is the interface stays up with no data - but if your signal was very low, perhaps it would disconnect. To be clear: if the modem isn't actually disconnecting, and its only ping failures, that expected if congestions/low signa...

Well, this is Linux only... But perhaps anybody else stumbles on this and finds it useful.) Another interesting option is to use rsyslog with https://github.com/rsyslog/loganalyzer . Rsyslog allows to easily tweak its default templates to properly parse Mikrotik logs and to store them in any format...

For sure you'd want to make sure everything is upgraded to at least stable. And likely worth trying "testing" 7.7rcX too. But Mikrotik support is actually pretty good at looking at these LTE issue. Perhaps not quick. But they'd want similar to logging and supout.rif files (and that were r...

@Amm0 thank you for a tip. The Chateau (or really any of the "modern LTE" devices) shouldn't need a script to recover. Now some builds to have bugs that would cause this. Well, i believe you are true and like i've previously mentioned it automatically recovers. But delay when it happens is...

Still troubleshooting this. I have implemented a script to ping 1.1.1.1 and cycle the LTE interface when the ping fails. My cell provider assigns my STX a private IP from there CGNAT pool. I extended my ping script to also ping that CGNAT private IP when 1.1.1.1 fails. When the 1.1.1.1 ping fails, ...

Hi,
Can you confirm country and mobile network provider?

Hi,
It's Latvia - Bite.

Hello, On Chateau LTE12 router I have an issue with lte Band 20. Router is located in 1 storey house close to a tower (~1-2km), and have external antenna attached. I have no troubles to connect to band 1 and 3 using any interface configuration (with default settings or enabling only specified bands)...

:put [/interface get ether1 link-downs]; how to send this command via api? Hello. I know that this post is old, yet i've searched everywhere to find an answer to this question with no luck. So, i'll post it here, in case it saves someone time. $ curl -u api:pass https://mikrotik.lan/rest/interface?...