[me@myTik] > system/health/print
Columns: NAME, VALUE, TYPE
# NAME VALUE TYPE
0 cpu-temperature 56 C
On my side, it is not a reluctance to reboot the router, it is an experience that a software-initiated reboot of the router was in too many cases not sufficient to resolve an issue with an LTE modem that itself needed a power cycle.Whhy is there such a reluctance to reboot the router?
Please review and maybe reword this sentence, I am not sure what actually happens under what circumstances.if my Kubernetes nodes announce svc addresses (via BGP) and I can connect to them from an IoT network, it loses the connection?
@sjoram has been around for a while, so I figure he enjoys the journey as much as the goal, so I play along.Actually mostly asking cause it pains me to see Sindy guessing.
That's a proper approach but I'm not sure how is that related to what I wrote.first, I just want to make sure that everything is properly configured on the ether2 interface on the server.
If they cannot even connect to the WiFi, I don't think it is a Mikrotik issue any more. So before starting from scratch, I'd suggest to save a backup and an export of the current configuration so that you have something known good to return to.Tomorrow try to reset and start again from scratch...
Please provide the output ofPlease note the firewall filter rule was located in the first line in the table.
@yhfung, please create a dedicated topic in forum general for further discussion.PPTP is no longer in v7.x
...
Please place PPTP client caller in Internet, and try to connect to RouterOS v7, find out what is WRONG.
Yup, but a default route in main is sufficient to meet this requirement.the main routing table should be able to resolve the destination too.
Have you tried the procedure I have suggested in my previous post?I would appreciate any help or workaround.