Setting up AX68U with Mikrotik ATL LTE18 ...

[Aziron5]

Hello

I don't expect or think anything major might happen, it's already working in my test case here. The ATL LTE18 is a Cellular client antenna and modem that converts the 3G/LTE signal to a wired Ethernet connection.

However it's the first time I'm dealing with anything Mikrotik or Router OS in general.

I remember loosely reading on this forum something about "router.lan" being a problem, but I can't find the post now. I think one of the addon or FW developers mentioned it.
Now several days into setting up the Mirkotik ATL antenna, I came across a default configuration that mentions "router.lan" and I'm wondering if that could cause problems down the line with the Asus router and DNS, eventually Diversion?

Exporting the entire config mentions this:

/ip dns static
add address=192.168.188.1 comment=defconf name=router.lan

BTW: It's a long story tho, don't get me started hehe, I had no idea the ATL LTE18 was a full blown router as well, but oh well, you can't run diversion and other stuff on it ofcourse, it may just have it's own way of doing just that, it's for a remote location and due to FTTH being setup with all new modems at the primary location, the router was upgraded too, leaving this spare, so it's all fine.

 

[Aziron5]

So I tried logging into the router over WAN and with default authentication/cert settings it's an insecure connection. I also think I had to set Port Mapping on the ATL LTE18 to get it working but surprisingly enough I didn't had to allow the 8443 port through the firewall for some reason, perhaps a thing with the way firewall rules work there, it's not perhaps enforcing the WinBox ports by mistake or by misconfig, letting all ports through for that source IP.

1. With Brave it's quite slow and some web menus are broken, slow and loading in chunks, it's better with Waterfox, almost perfect. (Windows 10)
2. There's completely zero logging in syslog of any WAN login attempts taking place, failed or successful, or the fact that it's an unsafe connection while a https one was requested, that doesn't seem right does it?
3. Logging in from WAN will throw other WAN logins out, unlike on LAN where it tells you that it can't login until the other one logs out themselfs first. Not sure yet if both LAN and WAN can be logged in at the same time.

Haven't worked with certificates on any Asus router yet, nor WAN Administration, so I'll get up to speed on that later ...