eralde

The clients with random MAC addresses should not be registered automatically even if that setting is turned on. If that is not so in your case, please attach a self-test file in a hidden message here and mark which clients were automatically registered by mistake.

@Pars @PriSonerS61 @ru.celebi @Ahmed Ensar, thank you for your help. The issue is confirmed, it will be fixed in one of the future versions.

@Pars ok, so far no visible issues from the browser. Could you create a readonly user account and DM me the login/password so I can log in to your device remotely and check the issue myself?

@Pars, hi! Could you tell us a bit more about the issue: 1. what browser do you use? 2. if you open the developers tools panel in your browser (it is typically opened by pressing F12 on your keyboard) are there any errors on the Console tab there?

Hello @maemelyanov Could you elaborate on this part: ? Was the segments configuration you described saved successfully (i.e. if you reload the web UI, do you see it configured there)? Also, it would be great if you could attach a self-test file from your device to this thread and hide the post with it (moderators will still be able to see it).

Hello, @alasedo. The data that our devices collect is listed here: https://keenetic.com/en/legal#dpn. Even if you have disabled the cloud features and service to communicate with the mobile app, there is still data transmission for the Authenticity Status Verification and the Internet Checker feature as outlined in the document. You can disable the Internet Checker, by executing the following commands: no service internet-checker system configuration save However, it is not possible to disable data transmission that is used for the authenticity verification purposes.

@fritz box, thank you for checking out the simplified policy configuration. After reading your last comment, I don't think I understand how your network is configured. Can you draw a schematic of your network: - how devices (Keenetic routers, computes, smartphones, ...) connected to each other (including connection policies on Keenetic routers) - on which devices the OpenVPN is configured ? And what problem are you trying to solve with a “double tunnel” VPN configuration?

Yes, thank you! This will be fixed in one of the future versions. That is a separate issue (both the KeenDNS name/icon alignment and the spacing in the clients table have the same underlying cause). It also will be fixed

@ru.celebi thank you for the report! It would be better if you don't hide the posts you publish here. If you don't want to include personal information (e.g. device names / IP addresses / MAC addresses) in your screenshots – blur them out before uploading the images. Firstly, this way you won't post two identical posts, and secondly, if your posts are visible, other users will also be able to check if they have the same problem. Thanks again for reporting the problems

Thank you for the self-test file! The configuration looks correct. Can you try something? Will your devices have Internet access if you: - disable multipath in that policy - remove rate-limiting for the OpenVPN interface ? Should look similar to this:

Hello @fritz box Please attach either a couple of screenshots of your browser with Policy Connections/Policy Bindings or a self-test file (you can download it from the Diagnostics page or the System Settings page. If you decide to attach the self-test file, please toggle the "Hide" toggle when adding a new message to this thread, so only the moderators of the forum will see your message.

This is expected behavior. The fail-safe mode is designed to prevent the device from losing remote access to the device when its settings are changed. Each of these operations can result in loss of remote access to the device.

The IntelliQoS feature in Keenetic devices uses a DPI engine called PACE2. The provider of this DPI engine says that it will use some AI techniques to classify traffic. That's why we also say that we have the AI IntelliQoS in our products. Since every Keenetic model uses the same DPI engine, every model will get the AI version with a firmware update at some point.

Hello, Enrico! Yes, it is possible to send and list received SMS via the REST API. The easiest way to do it is to see how the web interface interacts with the router. I wrote an extended explanation for USSD requests here: Commands for reading/sending SMS are quite similar (sms {interface} list, sms {interface} send, sms {interface} delete, sms {inteface} read). A simple example: A few extra notes: - you need to be authorized on the Keenetic to send the requests; the auth process is described here (in Russian): https://forum.keenetic.ru/topic/5461-не-работает-digest-авторизация-для-rci/#findComment-62946 preserve session cookies while sending follow-up GET requests - don't forget to set the Content-Type HTTP header for your requests (Content-Type: application/json)

Thank you for the report! Looks like the MWS controller send incomplete data to the web UI. If that situation repeats itself, it would be helpful to: - download a self-test file from the controller - open <keenetic address>/rci/show/mws/member (e.g. http://my.keenetic.net/rci/show/mws/member), save the displayed JSON as a text file and upload it here along with the self-test file