Dear Ladies and Gents!

Since years we do have the RB912R-2nD with several hundret units in the field.
We mainly use them for LTE backup for DSL connected sites.

What else we have:
own APN
own Radius Server

Provider: T-Mobile Austria

The HUGE problem:
Since the launch of the NEW EC200A Modems it is not possibe to have routed networks behind a interface assigned IP.

e.g.: Framed IP on interface: lte1 172.16.1.1
Framed route on lo0: 172.16.5.1


/interface lte
set [ find default-name=lte1 ] allow-roaming=yes band="" network-mode=lte
/interface lte apn
set [ find default=yes ] apn=myapn authentication=chap ip-type=ipv4 password=password use-network-apn=no user=myuser
/interface lte settings
set sim-slot=down
/ip address
add address=172.16.5.1/32 interface=lo0 network=172.16.5.1


Before the EC200 i saw packets arriving, when pulling a pcap, fpr 172.16.5.1, since the EC200 they do NOT show up at all.

I've tried it as well with the actual 7.16.2, as with 7.17rc3
Firmware @R11E: MikroTik_CP_2.160.000_v021
FW @Quectel EC200A: EC200AEUHAR01A19M16

Behavior is reproduceable.

Does any face the same situation or habe a solution for us?

Greetings from Vienna,

roland

Already checked with support ?

Yes, and unfortunately this is a known issue.

Will be solved in the release of the EC200A firmware, but without a date.

So beware of currently using the RB912 version 2004 with routed networks.
luckily I have some old ones, but lets look, how long they last.

The "hAP ax lite LTE6" are within the same price category, and they work. But I don't wanna have to widen my portfolio...

greetings from rainy Vienna,
roland

Any news on this, I have literally been debugging this same issue for like 3 hours now, and finally found this post!

My LTE Tik is deployed in a rural field, 7 hours round trip for a tech, where we replaced a LHGGM
with dodgy PoE with a shiny new wAPGR-5HacD2HnD that has the Quectel EC200A Revision EC200AEUHAR01A19M16 card thinking this would solve our issues, and was the prudent thing to do given the cost of the truck roll vs the cost of the new wAPGR being cheap.

We have a routed network on a private APN into a MPLS WAN, where I can see routed packets leaving the wAPGR LTE interface fine, and I can see them arriving at the other end of the MPLS WAN, but the reply packets never make it back....

When I Torch the LTE interface I can see the reply entries show up for all the routed inbound traffic, but no routed reply traffic shows up in a PCAP... I thought I was going mad...

I had tried 7.16.2, 7.17.2 7.18.2, 7.19beta6 etc with no luck. My Quectel EC200A firmware is EC200AEUHAR01A19M16, which I believe is the latest.

If there is no resolution, I probably need to build some hacky EoIP tunnel now, and re-engineer the WAN access for this remote site

Hi!

I've tried it some 14 days ago, but unfortunately no progress on this topic. Firmware offered is still the buggy one.

greetings from Vienna,
roland

Thanks for the reply!

I have an old Quectel EC25-AU card kicking round, that was used many years ago in an older WAP for a solar LTE gateway, I shall try and get someone to do a road trip and swap the card, hopefully the EC25-AU doesn't have the same bug

Otherwise I guess I am putting in another Starlink, which is way overkill for some telemetry data from a remote field :/

Check with support again.
They should be able to tell you when the corrected version will be available or they can put it themselves on your device (you may have to give them remote access to that device).
Or they should provide a workaround for your setup circumventing this problem.

Crazy this is already lingering for 3 months without solution ?

I emailed support yesterday, not reply yet, maybe I will hear something in the coming weeks.

In the meantime I needed to get the site back online, and managed to convince someone to make a Saturday trek to site with a replacement Quectel EC25-AU card, which solved the issue for me, we're now passing routed traffic again from the WAN / private APN, so at least that's something