tool fetch - LTE

RouterOS Scripting
1

Hi All

I have the below at the end of a script on my scheduler, it runs awesome sending all the data [not shown here] to the API endpoint to be handled

Perform the HTTP POST request using the fetch tool

/tool fetch url="https:/MYENDPOINT"
http-method=post
http-header-field="Content-Type: application/json"
http-data=$jsonData
output=none

my question is a simple one why dose this not work when the Device is running on LTE?
As soon as I hardwire, DCHP to ISP router or direct PPPoE its fine, but as soon as its on LTE, it just fails every time.

Any help would be awesome

Thanks

2

Look at how routing table changes as LTE goes up and down.

3

Whats odd is that the the route table is nothing special - See Below

Also if I get a terminal up (on a router on LTE) and I run this

/tool fetch url=“https://MYENDPOINT” http-method=post \

I get
status: finished
downloaded: 0KiBC-z pause]
duration: 1s

This shows connection to the End point (there is nothing to download but the JSON from the Router should be handed over)

however the log message looks like this
memory, Script, Error - executing script script1 from winbox failed, please check it manually

/ip route add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=192.168.150.1 routing-table=rtab-4 scope=30 suppress-hw-offload=no target-scope=30
This is the only rule I have in the route table that I have made

there is then only the Default routes made for the Bridge Interfaces and the LTE1 itself - with a route that has 0.0.0.0/0 → lte1 at distance 2 (which is also default added)

If I connect this router to the broadband I just works

4

Make sure firewall allows required traffic despite routing changes DHCP client makes as connections go up and down.