eralde

Thank you for explaining why do you want it 🙂 We will keep that scenario in mind for the future. I would be happy to give you a timeline, but at this point, it's difficult to do so. We definitely have 10G models in our roadmap.

I think that in your case the easiest way would be to exclude the Buddy 6 that is placed in the garage from the Wi-Fi system. You can remove the Buddy 6 from the Wi-Fi system using the controller Web UI. After that you can set up that Buddy device again as a separate "Access Point" device (there is an option for that in the Initial Setup Wizard on that Buddy). You will still be able to configure that Buddy using it's own web UI, but the controller won't sync it's settings to it. That means that the work schedule on that Buddy can be 24/7 instead of the one you have inside your house. Unfortunately, that also means that you'll have to configure all the relevant settings (e.g., Wi-Fi SSID/password/...) on the Buddy itself. Some of those settings can be configured in the Initial Setup Wizard. For ones that you can't change there you'll have to log in to the Buddy web UI. You will see a link to it on the "Client Lists" page in the controller web UI.

You can configure a configuration that you describe via the command line. It won't be possible to do it in the web UI. The resulting configuration file (startup-config) will contain something like this: ... interface Dsl0 rename DSL ip dhcp client dns-routes ip name-servers ... up ! ... interface Dsl0/Vlan0 security-level public ip address dhcp ip dhcp client dns-routes ip global 306 up ! interface Dsl0/Vlan123 security-level public ip address dhcp ip dhcp client dns-routes ip global 153 up ! ... However, I don't have enough expertise to answer any following questions about the setup you want. I kindly suggest that you contact our technical support: https://support.keenetic.com/ Our support engineers will be able to answer your questions better than I am.

Hello @Giaccaz unfortunately the setup you described is not possible to configure at the moment. Maybe you can consider configuring a separate Wi-Fi network (AccessPoint) interface specifically for the repeater? Then you can assign a separate schedule only for that Wi-Fi network. Could you elaborate a bit more on what issue you're trying to solve with this scheduling?

Yes, this configuration (no VLAN for the Internet, only for IPTV) should work as you expect. I hope that helps 🙂

@moij258 if I understand you correctly, your goal is to configure something like this (in my example I configure the IPTV VLAN on the port #4):

In order for IntelliQoS to properly prioritize traffic it needs to know the total amount of bandwidth available, that's why you see different results after manually specifying the download and upload speed. You said before that without any IntelliQoS configuration you typically get bandwidth values around 92 Mbps (download) / 22Mbps (upload). How do you measure those values? I am asking, because you said that you see different bufferbloat results after entering lower values manually (85/20). Could it be that the lower numbers are closer to the actual bandwidth of your connection?

Hi, @reshuffle812 What problem are you trying to solve with IntelliQoS? I see that you check the configuration by running a bufferbloat test, but if you could elaborate on what you're trying to achieve with getting certain values there, maybe we can provide a better advice about how to configure the Keenetic.

If you press Tab after entering part of the command it will show you the available autocomplete options. For example, if you press Tab after entering ip dhcp pool<space>, you will see the names of existing DHCP pool objects. After that you can check which options are available after you enter ip dhcp pool __POOL_NAME__ option<space> or ip dhcp pool __POOL_NAME__ option 66<space>. Maybe that will help you.

Hi @emresensoy, it looks like you need to change string to ascii in your command: (config)> ip dhcp pool _WEBADMIN option 66 ascii 192.168.2.1 Dhcp::Pool: "_WEBADMIN": set option 66.

I hope this will help you a bit with the REST API: https://github.com/Eralde/rci-tools It is a small side project I am working on. Feedback is appreciated 🙂

The Web UI relies on the values in the startup-config. You should check if your automation changes the value there. If it is not so try adding the system configuration save command after you switch the Wi-Fi with Home Assistant. It should resolve the issue.

Hi @em286 There is a way to do that using Entware nginx-ssl package. While it is not a very straightforward one, it should work. Install Entware Run opkg update && opkg upgrade && opkg-install nginx-ssl in the Entware shell Adjust /opt/etc/nginx/nginx.conf to proxy /auth and /rci/ requests to the firmware web server (see configuration below; replace "Home" segment address in it with 192.168.1.1) Configure xxx.yyy.keenetic.name to proxy requests to "This Keenetic Device" + nginx-ssl port This way X-NDM-Challenge and X-NDM-Realm headers will be preserved: $ curl -i https://rci.dev-3811.keenetic.link/auth HTTP/2 401 server: Web server date: Mon, 29 Dec 2025 07:51:34 GMT set-cookie: ... Path=/; SameSite=Strict; Max-Age=300 www-authenticate: x-ndw2-interactive ... x-ndm-realm: Keenetic Hopper x-ndm-challenge: BJ**** x-ndm-product: Hopper

The controller update channel is not propagated to the extender devices, this is the expected behavior.

You can change the update channel for a member device like this: 1. Check the checkbox for the relevant member device in the nodes table. 2. Press the "Edit" button on top of the table. 3. Change the "KeeneticOS" dropdown value to the desired update channel (Dev in my example) in the device settings dialog. 4. Press the "Save" button at the bottom of the device settings dialog.

If for some reason the MAC address does not work you also can use candidate's cid as the candidate identifier. Device's cid can be found in the show identification command output. If you press Tab after entering mws acquire, there should be some autocomplete options available.

Thank you for the explanation @David CHEVALIER 🙂 So far, I can't really remember any similar requests. Scheduling port shutdowns is a smart solution for your setup 💪 Generally speaking, in a similar setup it would be easier to just use a few Keenetic APs + the central Keenetic router. If you unite them into a Mesh Wi-Fi system, the central router (“controller”) will be able to distribute its settings to access points, including the Wi-Fi schedule. We get requests to add that feature from time to time. It may be implemented in one of the future releases. On a related note, our router provides a REST API that you can use to control it with a bit of scripting. This way you can create your custom small UI containing all the features you want. If you are interested in that, I can provide more details.

@David CHEVALIER Hi, could you elaborate on why do you want to assign schedules to the network ports?

Yes, it should be possible: you need to go to the "Ethernet Cable Connections to Internet" page and delete the existing Ethernet WAN connection. Then the blue Ethernet port will become just another LAN port. I am using an older DSL device, but the process is the same.

If you save the configuration (system configuration save) after assigning the policy that should not happen. If that indeed happens, then please do the following: configure the policy and assign it to the Transmission download a self-test file add or remove a firmware component (and update the firmware) check if the policy assignment for the Transmission is missing (it if is missing) download another self-test file after the device boots again attach both self-test files to this thread in a hidden message Generally speaking, if you configured the policy and saved the configuration, then if you download the startup-config file, there should be a torrent policy ... line in it.

Hello @spetr You can create a dedicated connection policy where the VPN interface is the primary one and then assign it to the Transmission client using the torrent policy command: Don't forget to save the device configuration (system configuration save) after you configure the Transmission policy.

Yes, once you reset the Titan to the factory settings, the Initial Setup Wizard should start automatically (once you connect your computer back to the Titan).

@TarkanTevetoglu so far we don't see any obvious issues with your configuration. Could you try the following to see if it resolves the issue: download the startup-config file from your device (to roll back to it if necessary) delete all Firewall/Port forwarding rules that you created check if you can access your router via KeenDNS after you've deleted the rules ? If this does not help, you can upload the startup-config to restore all the rules you have now.

I can understand your frustration, but this forum is not technical support. I will forward your self-test data to people who will be able to look into this issue during working hours next week. In the meantime you can contact technical support here: https://support.keenetic.com/eu/?lang=en https://support.keenetic.com/tr/?lang=en

Please check out this KB article: https://help.keenetic.com/hc/en-us/articles/360021214160-Installing-the-Entware-repository-package-system-on-a-USB-drive You don't need an SSH connection to actually install the Entware. You should be able to connect to the Entware shell via SSH once it is installed on your new drive.